Coros MCP Server
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| loginA | Start the authentication process by opening a web browser. The user will complete login in the browser and then confirm when done. |
| get_recent_activitiesB | Get recent Coros activities. Returns a list of workouts with basic information like date, name, and sport type. |
| get_activity_file_urlB | Get the download URL for a specific activity file (FIT, TCX, or GPX format) |
| get_profileA | Get user profile including personal metrics and training zones (heart rate zones, pace zones) |
| get_evolab_metricsB | Get EvoLab metrics including running fitness scores, training status, recovery data, and efficiency trends |
| get_training_calendarB | Get training schedule and calendar for a date range |
| get_sport_typesA | Get a mapping of all supported sport types and their IDs |
| get_activity_detailsB | Get comprehensive activity data including summary metrics, laps, time-series data, zones, and weather |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 8 tools
All tools have clearly distinct purposes: login, listing activities, downloading files, profile, metrics, calendar, sport types, and activity details. No overlaps.
Most tools follow 'get_' prefix pattern. One exception is 'login', which is a different action. Overall consistent and predictable.
8 tools is well-scoped for a fitness server, covering authentication, data retrieval, and analytics without being excessive or too few.
Covers profile, activities list/details, metrics, calendar, file downloads. Missing create/update/delete, but likely acceptable for a read-focused API. Minor gap.