Garmin Workouts MCP
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| GARTH_HOME | No | Local convenience path pointing to saved Garmin tokens. | |
| GARMIN_EMAIL | No | Garmin Connect email address for the hosted/default authentication path. | |
| GARMIN_PASSWORD | No | Garmin Connect password for the hosted/default authentication path. |
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 | {
"listChanged": true
} |
| logging | {} |
| prompts | {
"listChanged": false
} |
| resources | {
"subscribe": false,
"listChanged": false
} |
| extensions | {
"io.modelcontextprotocol/ui": {}
} |
| experimental | {} |
Tools
Functions exposed to the LLM to take actions
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 15 tools
Most tools target distinct actions (list, get, delete, upload, validate) but there is some overlap in workout-related operations like generate_workout_data_prompt, preview_workout_payload, and get_workout_input_schema which may confuse an agent. Also, list_workouts and list_activities are distinct but could be ambiguous without descriptions.
The majority of tools follow a consistent verb_noun pattern (list_workouts, delete_workout, validate_workout, get_activity). However, 'resolve_supported_strength_exercise' and 'generate_workout_data_prompt' deviate slightly from the simpler pattern of other tools, introducing minor inconsistency.
Fifteen tools is within a reasonable range for a workout management server, covering CRUD, validation, preview, and activity retrieval. The count feels slightly heavy but each tool seems to serve a purpose, and it is not excessive for the apparent feature set.
The server covers core workout lifecycle operations (list, get, upload, delete) plus validation, preview, and schema retrieval. Missing update functionality for workouts is a notable gap, but the domain appears covered for typical workout management workflows.