get_cache_status
Show what data is currently stored in the local SQLite cache.
How to use it
get_cache_status is exposed by the Coros MCP MCP server. Add the server to your MCP client (Claude Desktop, Cursor, Windsurf and others), and the get_cache_status tool becomes available to the model automatically. See the full listing for setup details and every tool this server provides.
Install Coros MCP
claude mcp add coros -- /path/to/coros-mcp/.venv/bin/coros-mcp serveOther tools in Coros MCP (20)
Log in with your Coros credentials. The auth token is stored securely in your system keyring (or an encrypted file as fallback).
Authenticate with the Coros mobile API only. This is mainly useful if you need to restore sleep-data access without redoing full web authentication.
Check whether valid web and mobile tokens are stored and how long the web token remains valid.
Delete a saved workout template from the Coros library.
Fetch full detail for a single activity. Requires the sporttype from listactivities.
Fetch daily metrics for a configurable number of weeks (default: 4).
Fetch nightly sleep stage data for a configurable number of weeks (default: 4).
List activities for a date range.
List the Coros exercise catalogue for a sport type. Default sporttype=4 returns strength exercises.
List planned activities from the Coros training calendar.
List reusable workout templates saved in the Coros library.
Remove a scheduled workout from the Coros training calendar.
Save a reusable strength workout template to the Coros library. Exercises must come from the Coros exercise catalogue.
Save a reusable cycling/intervals workout template to the Coros library. The template appears in the Coros app and can be synced to the watch. Steps can be plain steps or repeat groups for intervals.
Schedule a one-off strength workout for a specific date. Builds the workout inline and posts straight to the calendar — does not create a library entry.
Schedule a one-off cycling/intervals workout for a specific date. Builds the workout inline and posts straight to the calendar — does not create a library entry. This is the common case.
Schedule an existing library template on a calendar day.
2 = Indoor Cycling (default), 200 = Road Bike
Backfill all data into the local SQLite cache for a date range. After the first full sync, getdailymetrics, getsleepdata, and listactivities serve historical data from cache and only fetch the incremental tail from the API.
2 = time in seconds, 3 = reps