Garmin Health MCP Server
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| SUPABASE_URL | Yes | The Supabase URL for your Garmin health data | |
| SUPABASE_ANON_KEY | Yes | Your Supabase anonymous key |
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
Server capabilities have not been inspected yet.
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| get_health_summaryB | Get an overview of all health data including VO2 max, activities, sleep, and race predictions |
| get_vo2maxC | Get VO2 max history and trends. VO2 max measures cardiovascular fitness in ml/kg/min. |
| get_activitiesC | Get activity breakdown by type, including counts, distances, and durations |
| get_sleepC | Get sleep statistics including average duration and total nights tracked. Optionally filter by date range. |
| get_race_predictionsB | Get predicted race times for 5K, 10K, half marathon, and marathon based on current fitness |
| get_heart_rate_zonesB | Get personalized heart rate training zones based on max HR and lactate threshold |
| get_training_loadB | Get training load data including acute/chronic workload ratio to assess overtraining risk |
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 7 tools
Each tool has a clearly distinct purpose targeting specific health and fitness data domains, such as activities, health summary, heart rate zones, race predictions, sleep, training load, and VO2 max. There is no overlap in functionality, and an agent can easily differentiate between them based on their descriptive names and scopes.
All tool names follow a consistent 'get_' prefix pattern with descriptive nouns, such as get_activities, get_health_summary, and get_heart_rate_zones. This uniformity makes the tool set predictable and easy to navigate, adhering to a clear verb_noun convention throughout.
With 7 tools, the server is well-scoped for a health and fitness data domain, covering key aspects like activities, sleep, training metrics, and predictions. Each tool serves a distinct purpose without redundancy, making the count appropriate and manageable for the server's intended use.
The tool set provides comprehensive read-only coverage for retrieving health and fitness data, including summaries, detailed metrics, and predictions. A minor gap exists in the lack of write or update operations, but for a data retrieval-focused server, this is reasonable and agents can work effectively with the available tools.