Garmin MCP Server
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| GARMIN_EMAIL | No | Garmin email for authentication. Optional; can also use interactive login. | |
| GARMIN_IS_CN | No | Set to 'true' if using Garmin China (CN). Defaults to 'false'. | false |
| GARMIN_PASSWORD | No | Garmin password for authentication. Optional; can also use interactive login. | |
| GARMIN_TOKEN_DIR | No | Directory to store Garmin tokens. Defaults to .garmin-tokens. | .garmin-tokens |
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
} |
| prompts | {
"listChanged": true
} |
| resources | {
"listChanged": true
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| garmin_wellbeing_snapshotB | Fetch a concise Garmin Connect wellbeing snapshot for a date: sleep, Body Battery, HRV, stress, training readiness, and a workload recommendation. |
| garmin_workload_guardA | Check Garmin recovery metrics before committing to a workload and suggest a safer daily scope when signals are weak. |
| garmin_sleep_summaryB | Fetch Garmin sleep score, duration, overnight HRV, sleep stress, Body Battery change, and resting heart rate. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
| garmin_workload_guardrails | System-style instructions for using Garmin recovery data before agreeing to heavy work. |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
| garmin-today | Today's Garmin wellbeing snapshot for agent context. |
TDQS
Scored across 3 tools
The sleep_summary and wellbeing_snapshot tools overlap significantly, as wellbeing_snapshot includes sleep data and more. An agent may be unsure which to use for sleep metrics alone, though descriptions help differentiate scope.
All tools follow a consistent 'garmin_<area>_<descriptor>' pattern using underscores. While not verb_noun, the naming is predictable and readable.
Three tools is slightly low for a comprehensive health tracking server, but the set covers key recovery and readiness metrics without being trivial.
The tools focus on sleep, wellbeing, and workload recovery but lack common Garmin features like activity logs, steps, or heart rate trends, creating notable gaps.