Garmin Health MCP Server
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| GARMIN_EMAIL | Yes | Your Garmin account email address. | |
| GARMIN_PASSWORD | Yes | Your Garmin account 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 | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| get_sleep_dataC | Get sleep data including hours, stages (light/deep/REM), and quality scores |
| get_body_batteryB | Get Body Battery data (Garmin's recovery metric, 0-100) |
| get_hrv_dataC | Get Heart Rate Variability (HRV) data in milliseconds |
| get_heart_rateC | Get resting, max, and min heart rate data |
| get_activitiesC | Get workout/activity data including type, duration, calories, and distance |
| get_stress_levelsB | Get all-day stress level data |
| get_summaryC | Get combined health summary with averages across all metrics |
| get_user_profileB | Get user profile information and connected devices |
| generate_chartC | Generate an interactive HTML chart (sleep, body_battery, hrv, activities, or dashboard) |
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 9 tools
Each tool has a clearly distinct purpose targeting specific health metrics or functions, with no overlap in scope. The tools cover different data types like activities, body battery, heart rate, HRV, sleep, stress, summaries, and profiles, making them easily distinguishable.
All tools follow a consistent verb_noun pattern with 'get_' or 'generate_' prefixes, using snake_case uniformly. This predictable naming scheme enhances readability and reduces confusion for agents.
With 9 tools, the server is well-scoped for a health data domain, covering key metrics without being overwhelming. Each tool serves a specific, necessary function, making the count appropriate for comprehensive health monitoring.
The toolset provides broad coverage for retrieving health metrics, including core data like activities, sleep, and stress, with a summary tool for aggregation. A minor gap exists in update or management tools for user data, but retrieval operations are largely complete for the domain.