Skip to main content
Glama

Server Configuration

Describes the environment variables required to run the server.

NameRequiredDescriptionDefault
GARMIN_MCP_HOMENoWhere the tokens live; use one per account~/.garmin-mcp
GARMIN_MCP_HTTPNo`curl_cffi` forces the Windows workaround, `requests` disables itauto
GARMIN_MCP_IS_CNNo`1` for garmin.cn accounts (untested)off
GARMIN_MCP_TIMEZONENoIANA time zone for "today" and timestampsthe account's
GARMIN_MCP_MAX_CHARSNoCap on answer length40000
GARMIN_MCP_READ_ONLYNo`1` removes every tool that changes the accountoff
GARMIN_MCP_CALL_TIMEOUTNoSeconds per call; `0` disables90
GARMIN_MCP_DOWNLOAD_DIRNoWhere downloads go~/Downloads/garmin-mcp
GARMIN_MCP_ENABLED_TOOLSNoComma-separated allow list of toolsall
GARMIN_MCP_DISABLED_TOOLSNoComma-separated deny list of toolsall

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

CapabilityDetails
tools
{
  "listChanged": false
}
prompts
{
  "listChanged": false
}
resources
{
  "subscribe": false,
  "listChanged": false
}

Tools

Functions exposed to the LLM to take actions

NameDescription
garmin_statusA

Login and connection check: who is logged in, how long the saved login lasts, when the watch last synced, and the last error. Call this first when another Garmin call fails, or to see how current the data is.

garmin_profileB

The account owner. profile: body measurements, VO2max, lactate threshold, usual sleep window. settings: Garmin's raw user settings. hr_zones: heart-rate zones in bpm per sport. power_zones: power zones.

garmin_activitiesA

List activities, newest first: id, type, start time, distance, time, pace or speed, heart rate, training load and effect. Pass an id to garmin_activity for detail.

garmin_activityC

One activity in as much depth as needed, one or more sections per call.

garmin_wellnessA

One day of wellness data. summary: steps, calories, intensity minutes, resting/min/max HR, stress, body battery, SpO2, respiration, active and sedentary time. sleep: the night that ENDED on date (date=today is last night): times, stages, score, HRV, resting HR, SpO2. hrv: the same night's HRV, baseline and status. body_battery: charged/drained, high/low and the events that moved it. stress, heart_rate, steps: day totals plus an hour-by-hour profile. Also resting_hr, spo2, respiration, floors, hydration, intensity_minutes, events (auto-detected movement), lifestyle (lifestyle logging).

garmin_trainingA

Training state on a day (default today). readiness: every training-readiness reading that day, with its factors; morning_readiness: the one after waking. recovery_time: hours still needed. status: training status, weekly load, acute/chronic load, ACWR, form, VO2max. load_balance: four-week aerobic low/high and anaerobic load against targets. Also fitness_age, vo2max, acclimation (heat/altitude), running_tolerance, race_predictions (5k to marathon), lactate_threshold, cycling_ftp.

garmin_trendA

A metric across a date range, one row per day (or week). stats (steps + calories), steps, calories, stress, intensity_minutes, sleep (per night), hrv (per night), respiration, resting_hr, body_battery, weight, training_load (acute, chronic, ACWR, form per day), vo2max (the dates it changed), running_tolerance, endurance_score, hill_score, lactate_threshold, progress (activity totals by type). Most allow up to a year; respiration and daily stress/intensity minutes 31 days, training_load 90 days.

garmin_bodyA

Body measurements over a period (default today): weigh_ins (each one, with body composition when a smart scale sent it), body_composition (entries plus averages), blood_pressure. Ids in the answer are what garmin_delete needs.

garmin_devicesB

Watches and other devices: list, last_used (and when it last synced), settings, primary (training device), solar (charging intake on a date), alarms.

garmin_gearC

Shoes, bikes and other gear: status, default activity types, total distance.

garmin_achievementsC

Goals, personal records, badges (earned, available, in progress) and challenges (adhoc, badge, available, unfinished, virtual).

garmin_referenceA

Lookup lists: activity_types (type keys, grouped), event_types (for activities), strength_exercises (Garmin's exercise catalog; search with query), food_serving_units (for custom foods).

garmin_api_getA

Read-only escape hatch: GET any Garmin Connect API path and return the raw JSON. Use only when no other garmin_ tool covers what is needed.

garmin_workoutsA

Saved workouts: the list, or one workout's steps (duration or distance, targets, repeats, strength exercises).

garmin_calendarB

The training calendar, looking forward by default. Scheduled entries carry the scheduled_id that garmin_delete kind=scheduled_workouts needs.

garmin_nutritionA

Garmin Connect's food log. food_log, meals and settings (calorie and macro goals) for one date; summary (per-day totals) and energy_balance (intake against burn, and what the weight trend implies) over up to 61 days.

garmin_food_searchB

Search foods, with each serving's id and macros (what garmin_log_food needs).

garmin_coursesA

Saved courses (routes): the list, or one course with its waypoints.

garmin_womens_healthA

Pregnancy summary, menstrual data for one date, or the menstrual calendar for a range.

garmin_activity_analysisA

Deeper analysis from the activity's original FIT file, beyond what Garmin Connect shows. Manual activities have no FIT file.

garmin_fit_messagesB

Every field of the activity's FIT file, decoded with Garmin's FIT SDK, paged. For questions no other tool answers.

garmin_power_curveA

Best power for 5 s to 60 min across recent activities, with an FTP estimate (95 % of the best 20 minutes). Downloads one file per activity, so it is slow.

garmin_downloadB

Save an activity, workout or course as a file on this computer.

garmin_update_activityA

Edit an activity: rename, retype, describe, set event type, RPE, feel, or gear. Only the fields given change. Confirm with the user first.

garmin_create_activityB

Add a manual activity (one the watch didn't record), in the account's time zone.

garmin_add_weigh_inC

Record a weigh-in in Garmin Connect.

garmin_add_body_compositionC

Record a full body-composition measurement (as a smart scale would).

garmin_add_blood_pressureC

Record a blood-pressure reading (mmHg).

garmin_add_hydrationC

Log water intake in Garmin Connect's hydration tracker.

garmin_set_hr_zonesA

Change heart-rate zone settings for a sport. With method max_hr and a new max_hr the floors are recalculated at 50/60/70/80/90 %. Confirm with the user first.

garmin_request_reloadA

Ask Garmin to reprocess a day's data (when a day's numbers look stuck or wrong).

garmin_create_workoutA

Build a structured workout and save it to Garmin Connect (it syncs to the watch). Each step ends one way (duration, distance_km, reps or lap_button) and has at most one target (hr_zone, hr_bpm, pace_min_km, speed_kmh, power_w, power_zone, cadence). Strength steps name a catalog exercise. See the workout://templates resources. Confirm the plan with the user first.

garmin_upload_workoutsA

Upload workouts written directly in Garmin's JSON. All are checked before any is uploaded (ids vs keys, nested targets, power targets, repeat groups). Prefer garmin_create_workout unless the exact JSON matters.

garmin_schedule_workoutsA

Put saved workouts on the calendar (a week plan at once if needed). A workout already on that day is not added twice.

garmin_set_nutrition_goalsC

Set Garmin Connect's daily calorie and macro goals from a date.

garmin_save_custom_foodC

Create or update a custom food (grams per serving, sodium in mg).

garmin_log_foodB

Log food to Garmin Connect's food log: a saved food by id and serving, or a quick add by name and calories, to Garmin Connect's food log.

garmin_upload_courseC

Create a private course in Garmin Connect from a GPX file.

garmin_deleteA

Permanently delete from Garmin Connect: weigh_ins (all on the date, or the ids given), blood_pressure, workouts, scheduled_workouts (unschedule), custom_food, food_log, course. Without confirm it only previews. With confirm=true it deletes only what was previewed in the last 15 minutes. There is no undo.

Prompts

Interactive templates invoked by user choice

NameDescription

No prompts

Resources

Contextual data attached and managed by the client

NameDescription
workout-template-simple-runWorkout template: Easy run 40 min (garmin_create_workout format)
workout-template-interval-runningWorkout template: 6 x 400 m (garmin_create_workout format)
workout-template-tempo-runWorkout template: Tempo 3 x 8 min (garmin_create_workout format)
workout-template-strength-circuitWorkout template: Full body circuit (garmin_create_workout format)
workout-structureHow workout steps, targets and Garmin's workout ids fit together

TDQS

B3.3/5.0

Scored across 39 tools

Disambiguation4/5

Tools are organized around distinct Garmin domains (activities, wellness, training, nutrition, body, devices), and paired tools like garmin_activities/garmin_activity are clearly list-vs-detail. A few boundaries blur: garmin_add_weigh_in vs garmin_add_body_composition, garmin_create_workout vs garmin_upload_workouts, and the three 'escape hatch' tools (garmin_api_get, garmin_fit_messages, garmin_activity_analysis) all claim to be for cases no other tool covers.

Naming Consistency4/5

All names use a uniform garmin_ prefix and snake_case, with predictable verb_noun forms for mutations (add_, create_, set_, log_, delete_) and noun forms for readers. The mix of noun-only readers (garmin_profile, garmin_gear) and verb_noun tools (garmin_add_weigh_in) is a minor inconsistency but internally readable.

Tool Count3/5

39 tools exceeds the comfortable 3-15 range and lands in heavy territory. The Garmin Connect domain is genuinely broad enough to justify many of them, but multiple escape-hatch/analysis tools and a few overlapping add_ tools push it past what most agents can navigate efficiently.

Completeness5/5

Coverage spans read, create, update, schedule, upload, download, and delete across activities, wellness, training, nutrition, body, devices, gear, workouts, calendar, courses, achievements, and women's health. Every apparent data domain has a corresponding mutation or lifecycle operation, and the preview-then-confirm delete pattern closes the loop for destructive actions.

Maintenance

ActivitySlowing
ResponsivenessNo recent community issues