Skip to main content
Glama
Garmin Health MCP

Garmin Health MCP

by EmilbMadsen

Server Configuration

Describes the environment variables required to run the server.

NameRequiredDescriptionDefault
GARMIN_HEALTH_MCP_TZNoTime zone used for converting GMT timestamps to ISO 8601. Defaults to Europe/Copenhagen.Europe/Copenhagen
GARMIN_PERSONAL_API_KEYNoGarmin Connect Personal API key. Looked up after GARMIN_PERSONAL_API_KEY_FILE and before the system keyring.
GARMIN_HEALTH_MCP_STATE_DIRNoDirectory for cached Garmin bearer token and FIT-file cache. Defaults to ~/.config/garmin-health-mcp/ (mode 0700).~/.config/garmin-health-mcp/
GARMIN_PERSONAL_API_KEY_FILENoPath to a file containing the Garmin Connect Personal API key. Looked up before GARMIN_PERSONAL_API_KEY and the system keyring.
GARMIN_HEALTH_MCP_ENABLE_CYCLENoSet to 1 to enable the optional get_menstrual_cycle tool. Menstrual-cycle data is off by default.0

Instructions

Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.

Read-only access to the user's own Garmin Connect health and activity data through Garmin's official Personal API (unofficial server, not affiliated with Garmin). Times are ISO 8601 in the user's local time zone. Dates are YYYY-MM-DD; a day's sleep belongs to the date the user woke up. Range tools default to the last 7 days and accept up to 1 year. Not available through this API: training readiness, training status, race predictions, VO2 max, calendar and workouts. Activities do include training effect, training load and time in HR zones; laps, splits, zone time and running dynamics come from the activity's FIT file.

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
get_sleepA

Full sleep record for one night (the date the user woke up): sleep and wake time, time in deep/light/REM/awake, sleep score with per-factor ratings and optimal ranges, average heart rate, SpO2, respiration, sleep stress, awake count, and sleep need for today and tomorrow.

get_sleep_summariesA

Compact sleep summary per night over a date range: duration, stages, sleep score, average heart rate, stress, SpO2 and respiration. Use get_sleep for one night in detail.

get_hrvA

Heart rate variability for one night: last-night average, 5-minute high, weekly average, personal baseline band and HRV status (e.g. BALANCED, UNBALANCED, LOW).

get_hrv_summariesA

HRV summary per night over a date range: last-night average, weekly average, baseline band and status. Best for HRV trends.

get_body_batteryB

Body Battery per day: charged and drained, level over the day, and events that changed it (sleep, activities, stress) with their impact and Garmin's feedback.

get_stressB

Daily stress: overall stress level (0-100) and seconds spent at rest and in low, medium and high stress.

get_stepsB

Daily steps, distance (meters) and step goal.

get_daily_summariesA

One overview per day: steps and floors, calories (active, resting, total), heart rate (min, max, resting), intensity minutes vs goal, stress breakdown, Body Battery (min, max, charged, drained), hydration, respiration and pulse ox. The best single call for "how was my day/week". Durations are in milliseconds.

get_heart_rateA

Heart rate for one day: resting heart rate, 7-day average resting heart rate, min and max, and min/avg/max per hour.

get_heart_rate_zonesA

The user's heart rate zones per sport: zone floors 1-5, method (e.g. % of max HR or HR reserve), and the max, resting and lactate threshold heart rate used.

get_spo2B

Blood oxygen (SpO2) for one day: day and sleep averages, lowest, latest, 7-day average, and hourly averages.

get_fitness_ageB

Garmin fitness age vs chronological age, and its components (vigorous days and minutes, resting heart rate, BMI).

get_weightB

Weigh-ins in a date range (weight in grams, BMI and body composition if measured), the range average, and the nearest weigh-in before and after the range.

get_weight_goalsC

Weight goals in effect during a date range.

get_hydrationB

Logged water intake per day. Empty if the user does not log hydration.

get_food_logsA

Foods logged in Garmin Connect for one day, with meals and serving sizes. Empty if the user does not log food in Garmin.

search_activitiesC

Recorded activities, newest first: name, type, start time, distance (m), duration (s), speed (m/s), calories, average/max HR, aerobic and anaerobic training effect, training load, seconds in HR zones 1-5, intensity minutes, Body Battery change and strength sets.

get_activityA

Details of one activity: summary (distance, durations, speed, heart rate, calories, training effect and load, intensity minutes, steps), type, time zone and device.

get_activity_workoutsB

The planned workout (steps and targets) the activity was recorded against, if any.

get_wellness_activity_summariesC

Wellness activity summaries (e.g. breathwork or relaxation sessions) in a date range.

get_activity_lapsA

Laps of one activity from its FIT file: distance, timer time, pace (or speed), grade- adjusted pace, average/max heart rate, cadence, power, ascent/descent, intensity (active, rest, warmup, cooldown) and what ended the lap (manual, distance, time). For structured workouts and intervals, laps are the reps.

get_activity_splitsA

Even distance splits of one activity (per km by default), computed from the recorded data: time, pace, average/max heart rate, cadence, power and elevation gain/loss per split. Paused time is excluded. The last split is usually shorter. Needs distance data.

get_activity_time_in_hr_zonesA

Time in heart rate zones for one activity, computed from the recorded heart rate: seconds and percent below zone 1 and in zones 1-5, with each zone's bpm range. Paused time is excluded. Also returns the watch's own time-in-zone totals for comparison.

get_activity_summary_statsB

Session summary from the activity's FIT file: distance, timer and elapsed time, pace and best pace (or speed), grade-adjusted pace, heart rate, cadence, power (avg, max, normalized), ascent/descent, calories, aerobic and anaerobic training effect, training load, running dynamics (ground contact time and balance, vertical oscillation and ratio, step length), respiration rate, perceived effort and feel, and which data the file contains.

get_profile_settingsC

The user's unit system, locale, time zone, first day of week and date/time formats.

Prompts

Interactive templates invoked by user choice

NameDescription

No prompts

Resources

Contextual data attached and managed by the client

NameDescription

No resources

TDQS

B3.4/5.0

Scored across 25 tools

Disambiguation4/5

Most tools target clearly distinct Garmin data domains, and the descriptions explicitly differentiate summary vs. detail tools such as get_sleep/get_sleep_summaries and get_hrv/get_hrv_summaries. There is still some overlap because get_daily_summaries aggregates many of the same metrics exposed by get_steps, get_heart_rate, get_stress, get_body_battery, get_spo2, and get_hydration.

Naming Consistency5/5

Names are consistently snake_case and almost all use the get_<resource> pattern, with activity sub-resources predictably namespaced under get_activity_*. The single search_activities tool uses a different verb but still follows the same verb_noun convention and is semantically clear.

Tool Count3/5

At 25 tools this is at the heavy end of the scale, and several tools are close summary/detail pairs or activity sub-metric calls that could be consolidated. Each tool covers a real data slice, but the surface feels broad and somewhat fragmented for an agent to navigate.

Completeness4/5

The read-only surface is broad, covering daily wellness, sleep, HRV, body battery, stress, weight, hydration, food, and detailed activity analysis. Minor gaps remain, such as training status/readiness, VO2 max, personal records, and planned-workout listing, but core health workflows are well supported.

Maintenance

ActivityMaintained
ResponsivenessNo recent community issues