Garmin Open MCP
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 | {
"listChanged": false
} |
| prompts | {
"listChanged": false
} |
| resources | {
"subscribe": false,
"listChanged": false
} |
| experimental | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| garmin_connection_statusA | Check whether a Garmin session exists and when data was last synchronized. |
| garmin_syncA | Synchronize recent Garmin daily summaries and activities into the local cache. Use sparingly because Garmin's unofficial API can rate-limit frequent requests. |
| garmin_get_dayA | Get a consolidated health summary for one YYYY-MM-DD date. |
| garmin_get_sleepA | Get sleep stages and available sleep metrics for one YYYY-MM-DD date. |
| garmin_list_activitiesA | List activities in an inclusive date range using YYYY-MM-DD dates. |
| garmin_get_activityA | Get one activity. Samples are capped and omitted unless explicitly requested. |
| garmin_get_training_statusA | Get Garmin training status and readiness for one YYYY-MM-DD date. |
| garmin_get_body_metricsB | Get body composition and blood-pressure data for a date range. |
| garmin_get_trendsA | Calculate trends from locally cached daily summaries. |
| garmin_compare_periodsA | Compare daily averages for two locally cached date ranges. |
| garmin_recent_overviewB | Return cached trends and activities for the most recent number of days. |
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 11 tools
Each tool targets a distinct resource or operation: connection status, sync, day summary, sleep, activities list/get, training status, body metrics, trends, period comparison, and recent overview. Even the cached-data tools are clearly separated by their analytical purpose.
All tools follow a consistent garmin_ prefix with a verb_noun structure (check, sync, get, list). The naming pattern is uniform and predictable, making it easy to infer what each tool does.
At 11 tools, the server is well-scoped for a health-data integration. It covers core data access, activity management, analytics, and connection handling without unnecessary bloat or gaps.
The surface covers major Garmin data domains: daily summary, sleep, activities, body metrics, training status, and cached data analysis. Minor gaps exist (e.g., no explicit hydration or intraday detail endpoints), but the core workflows are complete.