garmin-mcp
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| GARMIN_EMAIL | Yes | Your Garmin Connect email address | |
| GARMIN_PASSWORD | Yes | Your Garmin Connect password |
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
| Name | Description |
|---|---|
| get_activitiesC | Get recent Garmin activities/workouts. |
| get_resting_heart_rateC | Get heart rate data (including resting HR) for a date. |
| get_sleepB | Get sleep data for a date. |
| get_body_batteryB | Get body battery levels for a date range. |
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 4 tools
Each tool targets a distinct health metric (activities, resting HR, sleep, body battery) with no overlap, making them easily distinguishable.
All tools follow a consistent 'get_' prefix with snake_case noun patterns, e.g., get_activities, get_sleep.
4 tools is slightly minimal for a health data server, but each tool covers a core metric and the set is well-scoped without being cluttered.
The server provides read-only access to a few common metrics, but lacks many standard Garmin data like steps, calories, or stress; notable gaps exist.