All servers / Health / Garmin Connect MCP server
Garmin Connect MCP server
MCP server for the official Garmin Connect Personal API
Tested by ConnectATDScore 90 out of 100. Tested 2026-11-19 on package version 0.14.0. Package: @indaco/garmin-personal-mcp · source
Score breakdown
| Runs | 18 / 20 | |
|---|---|---|
| Tool descriptions | 20 / 20 | |
| Package safety | 20 / 20 | |
| Maintenance | 20 / 20 | |
| Adoption | 12 / 20 |
What we saw
- Starts and answers the MCP handshake: yes (1.3 seconds including download)
- Tools offered: 20
- Last published: 2026-11-17
- Weekly downloads (npm): 1,400
- License: MIT · Direct dependencies: 0
Want this server set up for your team?
ConnectATD builds AI automation and wires up MCP servers like this one. Tell us what you are trying to do.
Talk to ConnectATDTools and how they are described
Agents choose tools from these descriptions. Under each name you can see how many of its parameters are explained.
listActivities6 of 6 parameters describedList the user's Garmin activities (most recent first) as a compact summary: id, name, type, local start time, distance (km), moving duration, average pace, average/max heart rate, cadence, ascent; when Garmin has them: elapsed time (if longer than moving time), race flag, Garmin training load, aerobic/anaerobic training effect and label, seconds in HR zones 1-5, calories, moderate/vigorous intensity minutes, body battery change, steps, swim SWOLF, pool length, lengths and strokes, power, mountain-bike grit and flow, a ride's km/h, ascent per hour and easy (zones 1-2) and hard (zones 4-5) share of the zone time, running form (stride, ground contact, vertical oscillation and ratio), grade-adjusted pace, best efforts (1k, mile, 5k, 10k, half, marathon) and run/walk segments. Dates are yyyy-MM-dd. Set raw=true for Garmin's full JSON. limit is at most 200; names filters the last 200 activities of the date window. Use it to find activity ids and to compare many activities. For the laps, sets or plan of one activity, give its id to getActivityLaps, getActivitySets or getActivityWorkouts.
getActivity1 of 1 parameter describedGarmin's full JSON for one activity: summaryDTO (start time, distance in metres, duration and movingDuration in seconds, averageSpeed in m/s, HR, calories, training effect and load, intensity minutes, Body Battery change, sets and reps of a strength session), splitSummaries (one total per split type, such as the run and walk segments), the activity type and metadataDTO (device maker, lap count, personal record flag). Private ids are left out. Use it for a field that listActivities does not give: listActivities gives the common fields in km and min/km, for many activities in one call. It has no laps, sets or samples: use getActivityLaps, getActivitySets or downloadActivityFit for them.
getActivityWorkouts1 of 1 parameter describedThe planned workout that an activity followed, as created in Garmin Connect: its steps in order, each with its intensity (warmup/active/rest/recovery/cooldown), its duration (time in seconds, reps, or open), its target (cadence, heart rate, pace, or open, with low and high values), the exercise for strength steps, and the coach's notes. A step with durationType REPEAT_UNTIL_STEPS_CMPLT repeats the steps from stepIndex durationValue up to it, targetValue times in all. Use it for the whole plan and its notes. For plan against done (hit or miss), read the plan field of getActivitySets (strength) or getActivityLaps (runs) instead; a ride or a swim has no plan field. An empty list means the activity followed no planned workout. Null fields are left out.
downloadActivityFit1 of 1 parameter describedDownload the ORIGINAL .FIT file of an activity and save it on the user's computer. Returns the absolute path of the saved .fit file (second-by-second HR, cadence, speed, laps). The file is saved once in the fit folder of the data dir; a later call does not download it again. Use it only when the user wants the file itself: getActivityLaps and getActivitySets already read it.
getActivityLaps1 of 1 parameter describedLaps of an activity as recorded by the watch (manual laps, auto-lap every km, or workout steps), read from the original .FIT file. One row per lap: distance (km), timer time, pace (min/km, foot sports) or speed (km/h), average/max HR, cadence (spm for running), ascent/descent, average power, running form (gctMs, vertRatioPct, vertOscCm, strideCm), intensity (active, interval, rest, recovery, warmup, cooldown; the auto laps of a free run can be interval), lap trigger, and the step of the planned workout (step: the reps of one drill share it). A swim lap also has metres, swimPace (per 100 m), stroke, lengths, swolf and strokes. Use it for intervals and per-km splits; getActivity does not have them. For a run: split (pace of the first and second half, kind, hrDriftPct) and, for a structured workout, work (reps, pace, avgHR, and the fade of each step with more than one rep, pct). For a swim: sets, the laps in a row of one distance, stroke and intensity (reps, firstPace, lastPace, pct: above 0 is slower, firstSwolf, lastSwolf). null is n/a. For a run, plan is the planned workout that the watch ran (null without one): its name and, per lap with a step in lap order, the step's target (type, low, high, unit; or zone), done (the lap in that unit), verdict (hit inside the target, ends included, or miss) and off (how far outside, in the unit: s/km for pace, above 0 is slower). An open or zone target, a target in %max or %ftp, a target outside a plausible range, a lap under 15 m or 8 s or a lap without the value has verdict null.
getActivitySets1 of 1 parameter describedStrength training sets of an activity, read from the original .FIT file. One entry per exercise, in the order first done, with its movement category, its primary and secondary muscles (from Garmin's exercise catalogue) and its active sets: reps, weight (kg, absent when none was recorded), set time in seconds and the rest after the set (restSec). Each exercise with weight also has top (the heaviest set of 1 to 12 reps, then the most reps; without one, the heaviest set) and e1rmKg (the best estimated 1RM, Epley, of its sets of 1 to 12 reps; null when it has none). Exercise names are stable across sessions, so they can be used for per-exercise trends. Edits made later in Garmin Connect (renamed exercises, corrected reps or weights) are not in the .FIT file. Use it for strength sessions; for runs, rides and swims use getActivityLaps. plan is the planned workout that the watch ran (null without one): its name and, per planned exercise and rep plan (a pyramid gives a row per rep plan) in plan order, plannedSets, plannedReps (low to high; high null is at least low), doneSets, reps, and verdict (hit or miss, why: sets or reps; extra and over count the done sets above the plan and above the high end); a warm-up or cool-down row (part) and a notInPlan row have verdict null. In a rest-pause group (a repeat of one exercise with a rest of 20 s or less inside it and a longer rest after it), only the first set of each pass is judged on reps. Such a row has restPause true. Each planned row also has plannedRestSec: the planned rests right after its sets, in seconds and plan order (null: an open rest, ended with the lap button; empty: no rest right after it, such as the first exercise of a superset).
getHrvRange2 of 2 parameters describedOvernight HRV for a date range, yyyy-MM-dd: hrvSummaries, one row per night with HRV data (a night without data has no row), with calendarDate, lastNightAvg (ms, the average of the night), lastNight5MinHigh, weeklyAvg (the 7-night average), status (BALANCED, UNBALANCED or LOW) and baseline (balancedLow to balancedUpper: the normal range). Ask at most 28 days in one call: Garmin may refuse a longer range. Use it for the HRV trend; for the sleep of a night use getSleep, and for resting HR use getDailyHeartRate or getDailySummary.
getDailyHeartRate1 of 1 parameter describedHeart rate of one day, yyyy-MM-dd: restingHeartRate, minHeartRate and maxHeartRate (bpm), lastSevenDaysAvgRestingHeartRate, and heartRateValues, the samples of the day as [timestamp, bpm] pairs (several hundred, so the answer is about 13 KB). Use it for the HR curve of a day. For resting HR over several days use getDailySummary with fromDate and toDate; for the zone limits use getHeartRateZones.
getSleep4 of 4 parameters describedSleep for one night (date: the morning you woke up), or for up to 14 nights (fromDate and toDate), yyyy-MM-dd, as one compact row per night: bedtime and wake (local HH:mm), hours of sleep, deep, light, REM and awake, the sleep score and its quality, the sleep need (hours), average heart rate, average and lowest SpO2, average respiration, awake count, average sleep stress and Garmin's feedback. Missing values are left out, and a night without sleep data has only its date. Set raw=true for Garmin's JSON.
getWeight3 of 3 parameters describedWeight for a date range, yyyy-MM-dd: the latest weight of each day (with body fat, muscle and bone mass, BMI and body water when a scale records them), the average of the range, and the last weight before and the first after the range. Set includeAll=true for every entry of each day. Weight, muscle mass and bone mass are in grams. The range has no day cap: ask a trend of months in one call.
getBodyBattery2 of 2 parameters describedBody Battery for up to 14 days, yyyy-MM-dd: for each day how much it charged and drained, its readings through the day as [timestamp, level] pairs, and the events that changed it (sleep, activities, stress, naps) with their start, duration and impact, and Garmin's feedback. Use it to see why Body Battery went up or down. For one number per day with steps and stress use getDailySummary; for the change of one activity, listActivities.
getHeartRateZonesno parametersThe heart rate zones set in Garmin Connect: a list with one entry per sport that has its own zones (sport DEFAULT for the others), each with trainingMethod (how Garmin sets the zones), zone1Floor to zone5Floor (the lowest bpm of each zone; a zone ends where the next one starts, zone 5 at maxHeartRateUsed), maxHeartRateUsed, restingHeartRateUsed and lactateThresholdHeartRateUsed. It takes no parameters. It gives the limits only: the time in each zone of an activity is hrZonesSec in listActivities.
getFitnessAge1 of 1 parameter describedGarmin fitness age for a date, yyyy-MM-dd: fitnessAge, chronologicalAge, achievableFitnessAge and previousFitnessAge, and components: bodyFat, vigorousDaysAvg and vigorousMinutesAvg (per week) and rhr (resting HR), each with its value and, when Garmin suggests one, targetValue and potentialAge (the fitness age at the target). stale is Garmin's flag for an old value. Use it for fitness age; for the body fat trend use getWeight.
getDailySummary3 of 3 parameters describedDaily user summary (steps, calories, stress, body battery, resting HR) for one date, or for up to 14 days (fromDate and toDate; the range answer has Garmin's v2 field names), yyyy-MM-dd. Use it for the totals of each day; for sleep use getSleep, for the Body Battery events getBodyBattery, and for the HR samples getDailyHeartRate.
garminGet2 of 2 parameters describedGeneric read-only GET on the Garmin Connect Personal API, for endpoints not covered by the other tools or when a query parameter name has to be adjusted. 'path' is relative and starts with '/', e.g. /fitnessage-service/fitnessage/v2/2026-10-25 . 'query' is an optional URL query string without '?', e.g. date=2026-10-25&foo=bar .
getDashboardData3 of 3 parameters describedAll the data of the training dashboard in one call: HR zones, fitness age, the activities of the last `weeks` weeks (compact summaries, with strength sets and laps where they apply; a strength session with sets also has `planVerdicts`: hit or miss for each exercise of the plan that the watch ran, null without a plan; a run whose laps are read, or whose .FIT file is saved, has `planVerdicts` too: hit or miss for each lap with a planned target), the activities of the weeks before for the period comparison, daily HRV, the last 14 days of sleep and daily summaries (with `recoveryHistory`, also short rows of the older days: date, sleep hours, sleep score and resting HR), and `units`: the measurement system of the Garmin profile (metric, statute_us or statute_uk) that the page shows; the data itself is always metric; `locale`: the language of the Garmin profile, e.g. it or pt-BR. Keeps a local cache and fetches from Garmin only what is new since the last call, so a rebuild or an update needs few calls. `sync` in the result says what was fetched: Garmin calls, .FIT files downloaded (fitDownloads) and new activities. `digest`, first in the result: the server's totals for the whole period and for each Monday-Sunday week (sessions, km, hours, load), the training load of the last 7 and 28 days, best efforts, races and strength top sets, the plan verdicts of the strength sessions done (`strengthPlan`), the long runs with their half split and HR drift, the longest run and the race predictions (Riegel), the page's readiness verdict for today with its inputs (`readiness`), and today's fitness, fatigue and form (`fitnessFatigue`); quote them instead of your own sums. For another date range, use the activities: each one is on its own line. A load is null (n/a) when the sessions have none; estimatedLoads counts the loads that are estimates from heart rate. A week with partial: true starts before the period. Without HRV and sleep data the digest has no `readiness`: give the verdict as n/a. The full result is large: 12 weeks can be about 180 KB, which can be over the tool output limit of the assistant. `writeDashboard` with `preview: true` gives only the digest, the activities of each board and the settings.
writeDashboard7 of 7 parameters describedWrites the training dashboard page (default <data-dir>/garmin-dashboard.html) with the data of the last `weeks` weeks (or, with `settings.since`, from the week of that day: one week more at each update, up to 52), and returns its path and a short digest of the data (totals, weekly sums, load, best efforts, races, long runs, race predictions, strength top sets, readiness, fitness and form, HRV, recovery, fitness age, sync) for the coach notes. Without HRV and sleep data the digest has no readiness: give the verdict as n/a. An existing page keeps all its code, layout and widgets: its data is replaced. A page with different page code gets the page code of the server and keeps its layout and widgets; the result then has `page: "upgraded"`, `previousServer` (the server version that wrote the page, n/a when unknown) and `server`. Every page from the template also gets the custom widgets of the widget library (<data-dir>/widgets.json), not placed on a board. On a page from the template, an edited board also gets the widgets that a release adds to its preset, one time; the result lists the ones that the page shows in `addedWidgets` (board -> widget ids). `layout` writes a new page from the template: `preset` (the default widgets) or `blank` (empty boards). It keeps the languages added with editDashboard `languages`. `page` writes your own page code instead; it must contain /* garmin-data:start */null/* garmin-data:end */. A replaced page is kept as <file>.bak. The .bak keeps the page from before the build: a write that follows within 15 minutes (the notes, a new title) does not replace it. `notes`: at most 5 plain-text coach notes; the server escapes them. `settings` replace the page's settings (title, headline, sports, data to leave out, languages, themes); without them the page keeps its own. The page holds only the data, languages and themes they keep. `pageLanguages` in the result lists the languages of the page's Language menu, and `settings` the settings that the page keeps. `missingProfileLanguage` is the language of the Garmin profile when the page has no texts in it (it shows English); editDashboard `languages` adds it. `missingWidgetTexts` lists the custom widgets that miss texts in a language of the page, with those languages; editDashboard `widgetTexts` adds them. `preview: true` writes no page file (it updates the data cache, as getDashboardData does): it returns the digest, the activities of each board and the `settings` of the page.
editDashboard8 of 10 parameters describedChanges the layout, the custom widgets or the languages of the dashboard page (a page from the template; call writeDashboard first). Without arguments it only reads: the reply has the layout, the custom widgets, the missing texts of each language, the catalogue of built-in widgets and `widgetApi`, the guide to writing a custom widget. `layout` replaces the whole layout (the text of the page's 'Copy layout'); `place` adds widgets at the end of a board; `widgets` adds or replaces custom widgets by id and saves them in the widget library (<data-dir>/widgets.json), which every page from the template gets; `removeWidgets` removes them from this page and its boards, `forgetWidgets` also from the library. `widgetTexts` adds texts to custom widgets by id, language and key, e.g. {"longest-ride": {"de": {"title": "Längste Fahrt"}}}. `languages` adds page texts by key, e.g. {"de": {"title": "Training + Erholung"}}: keys and {placeholders} as in `englishTexts: true`; a text with "|" has a singular and a plural form. Missing texts show in English. `removeLanguages` removes languages that `languages` added.
showDashboard2 of 2 parameters describedShows the training dashboard in the chat, in assistants that show MCP Apps: the page of `path` (default <data-dir>/garmin-dashboard.html) with its layout, custom widgets, languages and settings, or the preset page when there is none, with new data of the last `weeks` weeks. Writes no page file, but updates the data cache and the saved .FIT files as getDashboardData does, and has no coach notes. Returns the page path, the digest of the data and the page settings. Other assistants show only this reply: there, writeDashboard writes the page as a file.
scheduleDashboardRefresh3 of 3 parameters describedTurns on, changes or stops the automatic refresh of a dashboard page. Use it only when the user asks for it or says yes to the question of a dashboard prompt. A job in the scheduler of the computer (launchd, cron or Task Scheduler) replaces the data of the page at the given times, also with no assistant open. The refresh removes the coach notes, because old notes do not agree with new data. The computer must be on at that time. The page must exist (writeDashboard first). `last` is the last automatic run: its time, the pages that it could not update, with the error, and in `partial` the pages that it updated with gaps. A page shows a note when its update is more than 1 hour late: `last` tells why. `cron`: convert what the user says, in any language, into a 5-field cron expression in local time: minute hour day-of-month month weekday, numbers only (0 = Sunday), e.g. "0 7 * * 1-5" for weekdays at 7. Two runs must be at least 1 hour apart. The cron is for all scheduled pages; `path` adds that page (default the main page); `off` stops the refresh of `path`, or of every page when no `path` is given. Without arguments it only reads. The reply has `next`, the next runs in local time: tell them to the user in their language, so they can check the schedule.
Tested in a sandbox with an empty environment: no API keys, a throwaway folder, nothing from a real account. A passing test shows the server runs and responds. It is not a security audit.