garmin-mcp
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| GARMIN_EMAIL | No | Optional Garmin account email, used by login instead of prompting and by the server as a fallback if no tokens exist (accounts without MFA only). | |
| GARMIN_IS_CN | No | Set to true for Garmin China accounts. | |
| GARMIN_PASSWORD | No | Optional Garmin account password, used by login instead of prompting and by the server as a fallback if no tokens exist (accounts without MFA only). | |
| GARMIN_MCP_TOKENSTORE | No | Where Garmin session tokens live. | ~/.garmin-mcp |
| GARMIN_MCP_DOWNLOAD_DIR | No | Where the download_activity tool writes downloaded activity files. | <tokenstore>/downloads |
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_user_profileB | Return the user settings (user data, units, formats, sleep times). (Garmin Connect, read-only. Dates are YYYY-MM-DD.) |
| get_user_summaryC | Return user activity summary for 'cdate' format 'YYYY-MM-DD'. (Garmin Connect, read-only. Dates are YYYY-MM-DD.) |
| get_stats_and_bodyA | Return the daily summary and body composition for a date. (Garmin Connect, read-only. Dates are YYYY-MM-DD.) |
| get_daily_summariesB | Return full daily summaries for a date range in one call. (Garmin Connect, read-only. Dates are YYYY-MM-DD.) |
| get_lifetime_totalsA | Return lifetime totals (distance, steps, calories, active days, ...). (Garmin Connect, read-only. Dates are YYYY-MM-DD.) |
| get_user_statisticsB | Return the profile statistics block (totals per activity type). (Garmin Connect, read-only. Dates are YYYY-MM-DD.) |
| get_activitiesA | Return a page of activities, newest first, optionally filtered by type. :param start: Starting activity offset, where 0 means the most recent activity :param limit: Number of activities to return :param activitytype: (Optional) Filter activities by type :param activitysubtype: (Optional) Filter activities further by sub-type. :return: List of activities from Garmin. (Garmin Connect, read-only. Dates are YYYY-MM-DD.) |
| get_activities_by_dateA | Return activities between two dates, optionally filtered by type. :param startdate: String in the format YYYY-MM-DD :param enddate: (Optional) String in the format YYYY-MM-DD :param activitytype: (Optional) Type of activity you are searching Possible values are [cycling, running, swimming, multi_sport, fitness_equipment, hiking, walking, other] :param sortorder: (Optional) sorting direction. By default, Garmin uses descending order by startLocal field. Use "asc" to get activities from oldest to newest. :return: list of JSON activities. (Garmin Connect, read-only. Dates are YYYY-MM-DD.) |
| get_last_activityB | Return the most recent activity. (Garmin Connect, read-only. Dates are YYYY-MM-DD.) |
| count_activitiesB | Return total number of activities for the current user account. (Garmin Connect, read-only. Dates are YYYY-MM-DD.) |
| get_activityB | Return activity summary, including basic splits. (Garmin Connect, read-only. Dates are YYYY-MM-DD.) |
| get_activity_detailsC | Return activity details. (Garmin Connect, read-only. Dates are YYYY-MM-DD.) |
| get_activity_splitsC | Return activity splits. (Garmin Connect, read-only. Dates are YYYY-MM-DD.) |
| get_activity_typed_splitsB | Return typed activity splits. Contains similar info to |
| get_activity_split_summariesC | Return activity split summaries. (Garmin Connect, read-only. Dates are YYYY-MM-DD.) |
| get_activity_hr_in_timezonesC | Return the time spent in each heart rate zone during an activity. (Garmin Connect, read-only. Dates are YYYY-MM-DD.) |
| get_activity_power_in_timezonesC | Return the time spent in each power zone during an activity. (Garmin Connect, read-only. Dates are YYYY-MM-DD.) |
| get_activity_weatherC | Return activity weather. (Garmin Connect, read-only. Dates are YYYY-MM-DD.) |
| get_activity_gearC | Return the gear linked to an activity. (Garmin Connect, read-only. Dates are YYYY-MM-DD.) |
| get_activity_exercise_setsC | Return activity exercise sets. (Garmin Connect, read-only. Dates are YYYY-MM-DD.) |
| get_activity_typesB | Return all activity types and their parent types. (Garmin Connect, read-only. Dates are YYYY-MM-DD.) |
| get_personal_recordC | Return personal records for current user. (Garmin Connect, read-only. Dates are YYYY-MM-DD.) |
| get_progress_summary_between_datesA | Return progress totals (distance, duration, ...) between two dates. :param startdate: String in the format YYYY-MM-DD :param enddate: String in the format YYYY-MM-DD :param metric: metric to be calculated in the summary: "elevationGain", "duration", "distance", "movingDuration" :param groupbyactivities: group the summary by activity type :return: list of JSON activities with their aggregated progress summary. (Garmin Connect, read-only. Dates are YYYY-MM-DD.) |
| get_weekly_activity_statsC | Return weekly activity aggregates (VO2 max, distance, duration, ...). (Garmin Connect, read-only. Dates are YYYY-MM-DD.) |
| get_sleep_dataB | Return sleep data for 'cdate' format 'YYYY-MM-DD'. (Garmin Connect, read-only. Dates are YYYY-MM-DD.) |
| get_heart_ratesC | Fetch available heart rates data 'cDate' format 'YYYY-MM-DD'. (Garmin Connect, read-only. Dates are YYYY-MM-DD.) |
| get_rhr_dayC | Return resting heart rate data for 'cdate' format 'YYYY-MM-DD'. (Garmin Connect, read-only. Dates are YYYY-MM-DD.) |
| get_hrv_dataB | Return HRV (Heart Rate Variability) data for 'cdate' format 'YYYY-MM-DD'. (Garmin Connect, read-only. Dates are YYYY-MM-DD.) |
| get_stress_dataC | Return stress data for 'cdate' format 'YYYY-MM-DD'. (Garmin Connect, read-only. Dates are YYYY-MM-DD.) |
| get_body_batteryC | Return body battery values by day for 'startdate' format 'YYYY-MM-DD' through enddate 'YYYY-MM-DD'. (Garmin Connect, read-only. Dates are YYYY-MM-DD.) |
| get_body_battery_eventsA | Return body battery events for date 'cdate' format 'YYYY-MM-DD'. The return value is a list of dictionaries, where each dictionary contains event data for a specific event. Events can include sleep, recorded activities, auto-detected activities, and naps. (Garmin Connect, read-only. Dates are YYYY-MM-DD.) |
| get_spo2_dataB | Return available SpO2 data 'cdate' format 'YYYY-MM-DD'. (Garmin Connect, read-only. Dates are YYYY-MM-DD.) |
| get_respiration_dataB | Return available respiration data 'cdate' format 'YYYY-MM-DD'. (Garmin Connect, read-only. Dates are YYYY-MM-DD.) |
| get_steps_dataC | Fetch available steps data 'cDate' format 'YYYY-MM-DD'. (Garmin Connect, read-only. Dates are YYYY-MM-DD.) |
| get_floorsB | Fetch available floors data 'cDate' format 'YYYY-MM-DD'. (Garmin Connect, read-only. Dates are YYYY-MM-DD.) |
| get_intensity_minutes_dataB | Return available Intensity Minutes data 'cdate' format 'YYYY-MM-DD'. (Garmin Connect, read-only. Dates are YYYY-MM-DD.) |
| get_hydration_dataA | Return available hydration data 'cdate' format 'YYYY-MM-DD'. (Garmin Connect, read-only. Dates are YYYY-MM-DD.) |
| get_body_compositionB | Return available body composition data for 'startdate' format 'YYYY-MM-DD' through enddate 'YYYY-MM-DD'. (Garmin Connect, read-only. Dates are YYYY-MM-DD.) |
| get_weigh_insB | Get weigh-ins between startdate and enddate using format 'YYYY-MM-DD'. (Garmin Connect, read-only. Dates are YYYY-MM-DD.) |
| get_blood_pressureC | Return blood pressure by day for 'startdate' format 'YYYY-MM-DD' through enddate 'YYYY-MM-DD'. (Garmin Connect, read-only. Dates are YYYY-MM-DD.) |
| get_daily_stepsC | Fetch available steps data 'start' and 'end' format 'YYYY-MM-DD'. (Garmin Connect, read-only. Dates are YYYY-MM-DD.) |
| get_daily_heart_rate_statsB | Return resting / min / max heart rate per day. (Garmin Connect, read-only. Dates are YYYY-MM-DD.) |
| get_daily_stress_statsB | Return overall stress level and stress durations per day. (Garmin Connect, read-only. Dates are YYYY-MM-DD.) |
| get_sleep_stats_weeklyB | Return weekly sleep statistics ( |
| get_training_readinessC | Return training readiness data for 'cdate' format 'YYYY-MM-DD'. (Garmin Connect, read-only. Dates are YYYY-MM-DD.) |
| get_training_statusB | Return training status data for current user. (Garmin Connect, read-only. Dates are YYYY-MM-DD.) |
| get_max_metricsC | Return available max metric data for 'cdate' format 'YYYY-MM-DD'. (Garmin Connect, read-only. Dates are YYYY-MM-DD.) |
| get_race_predictionsB | Return race predictions for the 5k, 10k, half marathon and marathon. Accepts either 0 parameters or all three: If all parameters are empty, returns the race predictions for the current date Or returns the race predictions for each day or month in the range provided. (Garmin Connect, read-only. Dates are YYYY-MM-DD.) |
| get_endurance_scoreA | Return endurance score by day for 'startdate' format 'YYYY-MM-DD' through enddate 'YYYY-MM-DD'. Using a single day returns the precise values for that day. Using a range returns values aggregated per |
| get_hill_scoreC | Return hill score by day from 'startdate' format 'YYYY-MM-DD' to enddate 'YYYY-MM-DD'. (Garmin Connect, read-only. Dates are YYYY-MM-DD.) |
| get_fitnessage_dataB | Return Fitness Age data for current user. (Garmin Connect, read-only. Dates are YYYY-MM-DD.) |
| get_lactate_thresholdB | Return running lactate threshold information, including heart rate, power, and speed. (Garmin Connect, read-only. Dates are YYYY-MM-DD.) |
| get_cycling_ftpB | Return cycling Functional Threshold Power (FTP) information. (Garmin Connect, read-only. Dates are YYYY-MM-DD.) |
| get_devicesB | Return available devices for the current user account. (Garmin Connect, read-only. Dates are YYYY-MM-DD.) |
| get_device_last_usedA | Return the device that synced last. (Garmin Connect, read-only. Dates are YYYY-MM-DD.) |
| get_goalsA | Return goals by status (active, future or past). :param status: Status of goals (valid options are "active", "future", or "past") :type status: str :param start: 1-based index of the first goal to retrieve :type start: int :param limit: Pagination limit when retrieving goals :type limit: int :return: list of goals in JSON format. (Garmin Connect, read-only. Dates are YYYY-MM-DD.) |
| get_earned_badgesA | Return all earned badges for the current user. (Garmin Connect, read-only. Dates are YYYY-MM-DD.) |
| get_todayA | Today's date (YYYY-MM-DD) in the Garmin account's timezone. Use it to resolve relative dates such as "yesterday" or "last week" before querying other tools. |
| garmin_api_getA | Raw GET against the Garmin Connect API for endpoints that have no dedicated tool.
Read-only; the path must not contain a query string (use |
| download_activityA | Download an activity's raw file (GPS track, sensor data) to the local download directory and return its path. Reads from Garmin; only writes a local file. |
| garmin_list_methodsA | List every read-only Garmin Connect data method runnable with |
| garmin_callA | Run any read-only Garmin Connect data method by name (see |
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 62 tools
Many tools overlap heavily: get_daily_heart_rate_stats vs get_heart_rates vs get_rhr_day; get_daily_stress_stats vs get_stress_data; get_steps_data vs get_daily_steps; and several activity-detail variants (get_activity, get_activity_details, get_activity_splits, get_activity_typed_splits, get_activity_split_summaries). Descriptions help in places, but an agent can easily choose the wrong endpoint for the same underlying data.
Most tools follow a get_<noun> snake_case pattern, but there are noticeable deviations: garmin_api_get, garmin_list_methods, garmin_call, download_activity, and get_today break the dominant convention. Minor inconsistencies like get_fitnessage_data and get_weigh_ins also reduce predictability.
62 tools is excessive for a read-only data server, especially because many endpoints are near-duplicates and generic escape hatches (garmin_api_get, garmin_call, garmin_list_methods) already cover undocumented data. Consolidation would make the surface far easier to navigate.
For a read-only Garmin Connect surface, coverage is broad: daily metrics, activities, sleep, body composition, training status, devices, goals, badges, raw API access, and downloads are all present. Some niche domains rely on the generic fallback rather than dedicated tools, but there are few obvious hard dead ends.