Garmin MCP
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| HOST | No | Web server bind address. Defaults to 127.0.0.1. Containers may explicitly set 0.0.0.0 for access through a trusted entry point. | 127.0.0.1 |
| PUBLIC_URL | No | Public HTTPS URL used when running behind a trusted reverse proxy. | |
| GARMIN_REGION | Yes | Garmin region to use, for example cn. | |
| ADMIN_PASSWORD | No | Independent admin password for the web interface. Required when exposing the web setup publicly through a trusted HTTPS proxy. Must be at least 12 characters and must not be an example placeholder password. | |
| ALLOW_URL_SECRET | No | Set to 1 only to re-enable the legacy /k/<secret>/mcp URL authentication method. Disabled by default. | 0 |
| GARMIN_PERSONAL_API_KEY | Yes | Your Garmin personal API key. This is sensitive and should be provided through a dedicated configuration entry, not ordinary chat. |
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
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| get_daily_stressC | 每日压力。与官方客户端 get_daily_stress 一一对应。参数和日期限制沿用官方接口。Return daily stress statistics for an inclusive calendar date range. |
| get_daily_stepsC | 每日步数。与官方客户端 get_daily_steps 一一对应。参数和日期限制沿用官方接口。Return daily step statistics for an inclusive calendar date range. |
| get_daily_hydrationC | 每日饮水。与官方客户端 get_daily_hydration 一一对应。参数和日期限制沿用官方接口。Return daily hydration statistics for an inclusive calendar date range. |
| get_effective_weight_goalsC | 体重目标。与官方客户端 get_effective_weight_goals 一一对应。参数和日期限制沿用官方接口。Return effective weight goals for an inclusive calendar date range. |
| get_weight_measurementsC | 体重测量。与官方客户端 get_weight_measurements 一一对应。参数和日期限制沿用官方接口。Return all weight data for an inclusive calendar date range. |
| get_daily_food_logsC | 饮食记录。与官方客户端 get_daily_food_logs 一一对应。参数和日期限制沿用官方接口。Return nutrition food logs for a calendar date. |
| get_user_profile_settingsC | 个人资料设置。与官方客户端 get_user_profile_settings 一一对应。参数和日期限制沿用官方接口。Return the current user's profile settings. |
| get_daily_sleepC | 单晚睡眠。与官方客户端 get_daily_sleep 一一对应。参数和日期限制沿用官方接口。Return daily sleep data for a calendar date. |
| get_daily_sleep_summariesB | 多日睡眠汇总。与官方客户端 get_daily_sleep_summaries 一一对应。参数和日期限制沿用官方接口。Return daily sleep summaries for an inclusive calendar date range. |
| get_daily_body_batteryC | 身体电量。与官方客户端 get_daily_body_battery 一一对应。参数和日期限制沿用官方接口。Return daily Body Battery data for an inclusive calendar date range. |
| get_daily_summariesC | 每日健康汇总。与官方客户端 get_daily_summaries 一一对应。参数和日期限制沿用官方接口。Return user daily summaries for an inclusive calendar date range. Use the same start and end date for a single day. The response preserves the endpoint's object containing a data array, even for one day. |
| get_daily_hrvC | 单日 HRV。与官方客户端 get_daily_hrv 一一对应。参数和日期限制沿用官方接口。Return heart rate variability (HRV) summary and readings for a calendar date. |
| get_daily_hrv_summariesC | 多日 HRV 汇总。与官方客户端 get_daily_hrv_summaries 一一对应。参数和日期限制沿用官方接口。Return daily heart rate variability (HRV) summaries for an inclusive date range. |
| get_heart_rate_zonesB | 心率区间。与官方客户端 get_heart_rate_zones 一一对应。参数和日期限制沿用官方接口。Return the current user's heart rate zones. |
| get_fitness_ageC | 体能年龄。与官方客户端 get_fitness_age 一一对应。参数和日期限制沿用官方接口。Return fitness age data for a calendar date. |
| get_daily_heart_rateC | 每日心率。与官方客户端 get_daily_heart_rate 一一对应。参数和日期限制沿用官方接口。Return daily heart rate data for a calendar date. |
| get_menstrual_cycle_summaryC | 生理周期汇总。与官方客户端 get_menstrual_cycle_summary 一一对应。参数和日期限制沿用官方接口。Return menstrual-cycle summary data for a calendar date. |
| get_menstrual_cycle_day_viewC | 生理周期日视图。与官方客户端 get_menstrual_cycle_day_view 一一对应。参数和日期限制沿用官方接口。Return the menstrual-cycle day view for a calendar date. |
| get_daily_spo2C | 每日血氧。与官方客户端 get_daily_spo2 一一对应。参数和日期限制沿用官方接口。Return daily SpO2 and acclimation data for a calendar date. |
| get_wellness_activity_summariesC | 日常活动汇总。与官方客户端 get_wellness_activity_summaries 一一对应。参数和日期限制沿用官方接口。Return wellness activity summaries for an inclusive calendar date range. |
| search_activitiesC | 搜索运动记录。与官方客户端 search_activities 一一对应。参数和日期限制沿用官方接口。Return summarized activities matching the supplied search filters. |
| get_activityC | 单次运动详情。与官方客户端 get_activity 一一对应。参数和日期限制沿用官方接口。Return the activity summary/details for an activity ID. |
| get_activity_workoutsC | 运动关联训练。与官方客户端 get_activity_workouts 一一对应。参数和日期限制沿用官方接口。Return workouts associated with an activity ID. |
| download_activityB | 下载原始运动文件。与官方客户端 download_activity 一一对应。参数和日期限制沿用官方接口。Return the original activity file as ZIP bytes, without extracting it. |
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 24 tools
Each tool maps to a distinct Garmin metric endpoint (stress, steps, hydration, sleep, HRV, SpO2, etc.), so most selection is obvious. The main risk is the single-day vs. multi-day summary pairs like get_daily_sleep/get_daily_sleep_summaries and get_daily_hrv/get_daily_hrv_summaries, plus get_daily_summaries vs get_wellness_activity_summaries, which require reading descriptions to distinguish.
All names are snake_case verb_noun following the get_<resource> pattern that mirrors the official API endpoints. The two non-get verbs (search_activities, download_activity) are semantically appropriate for their actions and still fit the convention.
24 tools is at the heavy edge of the ideal range, but each corresponds to a distinct Garmin wellness/activity endpoint, so most earn their place. The single/summary duplication pairs push the count slightly higher than strictly necessary.
The surface covers a broad read-only slice of Garmin data (wellness metrics, sleep, HRV, activities, downloads, profile) with no dead ends for querying. Gaps exist for write operations, device lists, and broader activity/workout library browsing, but the read-oriented domain is largely handled.