garmin-personal-api-mcp
This server lets Claude read your own Garmin Connect data via Garmin's official Personal API, with read-only access to activities, recovery, sleep, wellness and body metrics.
View profile settings, units and heart-rate zones.
List and filter activities by date, type and limit; get activity summaries.
Download original activity files and compute exact splits with pacing analysis.
Get VO2 max, training effect, recovery time and performance condition.
Fetch a day at a glance: summary, sleep, HRV, Body Battery and activities.
Query daily trends for steps, calories, heart rate, stress, intensity minutes and Body Battery.
Read sleep summaries/detail, HRV, stress, steps, hydration and Body Battery.
Access weight, body composition and weight goals.
View wellness activities, all-day heart rate, SpO2, fitness age and nutrition logs.
Save activity FIT/ZIP files locally.
Call any documented Personal API GET endpoint within the allowed service paths for extra data.
Integrates with Garmin Connect via Garmin's official Personal API to read a user's Garmin data, including activities, activity splits, VO2 max and performance metrics, sleep, HRV, Body Battery, stress, steps, hydration, weight, heart rate, SpO2, fitness age, nutrition, profile and heart-rate zones, and to download activity FIT files.
Click on "Deploy Server".
Wait a few minutes for the server to deploy. Once ready, it will show a "Started" state.
In the chat, type
@followed by the MCP server name and your instructions, e.g., "@garmin-personal-api-mcp How was my pacing on yesterday's run? Did I fade?"
That's it! The server will respond to your query, and you can continue using it as needed.
Here is a step-by-step guide with screenshots.
garmin-personal-api-mcp
Ask Claude about your own Garmin data: runs, VO2 max, sleep, HRV, Body Battery, weight. It uses Garmin's official Personal API, so there's no password, no scraping and no reverse-engineered login.

You use | Install with |
Claude Desktop (chat) | The Download button above, then three steps |
Claude Code and Cowork |
|
Any other MCP app (Cursor and others) |
|
All three need a Garmin Personal API key, which you create in Garmin Connect under Settings → Personal API.
Contents: Install · What you can ask · What it can't do · Your data · Garmin's terms · Claude Code, Cursor and other apps · Contributing
Install in Claude Desktop
macOS or Windows. No terminal, no Node install. You need a Garmin Connect account.
Create a key. In Garmin Connect, open Settings → Personal API → Create Key, and copy it.
Download the extension and double-click it, then click Install.
Add the key. Claude Desktop installs the extension switched off until it has a key. Open Settings → Extensions → Personal Data for Garmin Connect, paste the key, click Save and switch it on.
Then start a new chat and ask away. The 90-second walkthrough shows all three steps and two questions:
https://github.com/user-attachments/assets/84078971-fc1b-4f1c-9f02-168e73e9cbef
When your key expires, create a new one in Garmin Connect and paste it in the same place. Claude tells you when this happens.
Updating: download the latest version with the same button and double-click it. The badge at the top shows the current version, and the releases page lists what changed in each one.
Related MCP server: runcoach
What you can ask
"How was my pacing on yesterday's run? Did I fade?" "What's my VO2 max, and how has it moved this month?" "How recovered am I today?" "Compare my HRV and sleep this week with last week." "Has my weight moved since I started the bulk in September?"

Dates can be YYYY-MM-DD, today, yesterday or N days ago.
Tool | What it gives Claude |
| Your activities with distance, time, pace, heart rate, training effect and Garmin's training load. Filter by date and type |
| Downloads the original |
| Your VO2 max as Garmin Connect shows it, every VO2 max reading in a window, and per-activity aerobic/anaerobic training effect, recovery time and performance condition, decoded from the activity files |
| Garmin's own summary for one activity |
| One call for a day: summary, sleep, HRV, Body Battery and activities |
| Steps, calories, resting HR, stress and intensity minutes across a date range |
| Nightly sleep summaries, or one night in full |
| Overnight HRV, baseline and status |
| Daily wellness series |
| Weigh-ins and body composition |
| Breathwork, relaxation and other wellness sessions |
| Single-day detail |
| Units, profile and heart-rate zones |
| Save the original file locally, for Runalyze, Golden Cheetah and so on |
| Escape hatch for any other documented Personal API endpoint |
Tool | Try asking |
| "What are my heart-rate zones?" |
| "What was my training load this week, activity by activity?" |
| "What's my VO2 max, and how has it moved this month?" |
| "What was the training effect of my last ride?" |
| "How was my pacing on yesterday's run? Did I fade?" |
| "Save the FIT file of my last run to ~/Downloads." |
| "How recovered am I today?" |
| "How many intensity minutes did I get each day this week?" |
| "Compare my sleep this week with last week." |
| "Break down last night's sleep stages." |
| "Is my HRV within my baseline this month?" |
| "How did my Body Battery recharge overnight this week?" |
| "Which day this week was most stressful?" |
| "Did I hit my step goal every day this month?" |
| "How much water did I log yesterday?" |
| "Has my weight moved since September?" |
| "What's my current weight goal?" |
| "Show my breathwork sessions this month." |
| "What was my resting heart rate yesterday?" |
| "What was my Pulse Ox last night?" |
| "What's my fitness age?" |
| "What did I log for food yesterday?" |
| "Get my menstrual cycle summary for this month." |
What it can't do
These limits are Garmin's, not this extension's:
Read-only. It can't push workouts, courses or training plans to your watch. Garmin keeps those APIs for business partners.
No training readiness, training status or race predictions. Garmin computes those on its servers and doesn't expose them. VO2 max, training effect and recovery time are available, because your watch writes them into each activity file. VO2 max and training effect match Garmin Connect; recovery time and performance condition are approximate.
Your account only. A key only reads the account that created it.
Your data and your key
Nothing is collected. Everything runs on your computer: data goes from Garmin to your computer to Claude and nowhere else. See PRIVACY.md.
Read-only. Every request is a read. Nothing can change or delete your Garmin data.
Your key stays on your computer. Claude Desktop stores it in its extension settings, and it's only ever sent to Garmin.
To remove access, uninstall the extension in Claude Desktop and delete the key in Garmin Connect under Settings → Personal API.
This is an independent project, not made or endorsed by Garmin. "Garmin" and "Garmin Connect" are trademarks of Garmin Ltd.
Garmin's terms
When you create a Personal API key, you accept Garmin's Personal API Supplemental Terms (Garmin Connect → Settings → Personal API → Review Terms and Conditions), on top of the Garmin Terms of Use. This project is built to keep you within them:
Your key is for your own use only. Garmin's terms allow a key to be used only by you, with tools you develop or operate for your own use, and forbid sharing it with anyone. So this tool runs on your computer, uses only your own key, and never sends the key anywhere except Garmin. Never give your key or your Garmin login to anyone else, including friends, support channels or reviewers. Anyone who wants to try the tool creates their own free Garmin account and key.
Only the official API. Every request goes through the Personal API that Garmin provides for this purpose. There's no scraping and no unofficial login, which Garmin's Terms of Use forbid.
Personal, non-commercial and read-only. The tool is free, never writes to your account, and has no hosted or shared version.
Rate limits. Garmin may limit or block requests that are too frequent. Ask for the data you need rather than very long ranges over and over.
Your responsibility. You're the one bound by Garmin's terms, and breaking them can get your key revoked. Read them when you create the key; Garmin can change them, and the current version is on that page.
Why it isn't in Claude's plugin directory
You won't find this in the directory under Customize → Plugins in Claude, and that's deliberate. Listing there requires agreeing to Anthropic's Software Directory Terms and Policy, and two of the Policy's requirements can't be met without breaking Garmin's terms:
A test account for reviewers. The Policy asks for a working test account with sample data. Garmin's terms say a Personal API key is for its owner's use only and must never be shared, and Garmin's Terms of Use forbid sharing account logins.
Owning every endpoint. The Policy asks developers to own or control every API their software calls. This tool calls Garmin's API, which only Garmin controls.
The Terms also make the developer personally liable to Anthropic for claims about the software, which is a lot to take on for a free side project. So it's distributed directly instead: the Claude Desktop extension, the npm package and the plugin below all install from this repository and work the same way.
Claude Code, Cursor and other apps
Claude Code and Cowork: install the plugin, which adds the server plus a skill that tells Claude how to answer training and recovery questions:
/plugin install garmin-personal-api-mcp --marketplace aaronhaddad/garmin-connect-mcp-claude-connectorClaude Code asks for your key when you install it. Cowork doesn't ask, so run the setup below once and the plugin uses the saved key. See the plugin README for details.
Any other MCP app, or to save the key on your computer: run the setup wizard. You need Node.js 20.3 or later.
npx garmin-personal-api-mcp setupThe setup wizard walks you through creating the key, checks it with Garmin, stores it in your macOS Keychain and connects Claude Desktop, Claude Code or Cursor. Restart those apps afterwards. They run the server with npx, so they pick up new versions automatically.

Command | What it does |
| Interactive setup: key and connected apps |
| Checks the saved key still works, and when it expires |
| Removes the saved key and cached token |
| Runs the MCP server on stdio (what your MCP app launches) |
For scripts and dotfiles: pbpaste | npx garmin-personal-api-mcp setup --key-stdin --storage keychain.
{
"mcpServers": {
"garmin-connect": {
"command": "npx",
"args": ["-y", "garmin-personal-api-mcp"]
}
}
}Claude Code: claude mcp add --scope user garmin-connect -- npx -y garmin-personal-api-mcp
The server reads the key from $GARMIN_PERSONAL_API_KEY, the macOS Keychain or ~/.config/garmin/connect-personal-api-key, so run setup once to save it even if you write the config yourself.
Contributing
Issues and pull requests are welcome. The server stays read-only and local (one user, their own key); CONTRIBUTING.md has the setup, how it works, how to add a tool and the PR checklist.
Built on the MCP TypeScript SDK v2, Garmin's FIT JavaScript SDK and @clack/prompts. Endpoint paths follow Garmin's Apache-2.0 connect-personal-api-python client.
License
MIT
Available Tools
23 toolsgarmin_api_getRaw Personal API GETARead-onlyIdempotent
Call any documented Personal API endpoint directly, for data the other tools don't cover (e.g. menstrual cycle summaries, activity workouts). Path must start with one of: /activity-service/, /activitylist-service/, /biometric-service/, /fitnessage-service/, /goal-service/, /hrv-service/, /nutrition-service/, /periodichealth-service/, /sleep-service/, /usersummary-service/, /userprofile-service/, /weight-service/, /wellness-service/, /wellnessactivity-service/. Example: path="/activity-service/activity/123456/workouts"
Inputs: path (required), params.
garmin_download_activity_fitSave original activity fileAIdempotent
Saves an activity's original file (Garmin's ZIP containing the .fit) to a folder on this computer, for import into other tools such as Runalyze or Golden Cheetah. Returns the saved path.
Inputs: activity_id (required), directory.
garmin_get_activityActivity detailsARead-onlyIdempotent
Garmin's computed summary for one activity: distance, durations, pace/speed, HR, cadence, elevation, training effect, calories. For per-km splits use garmin_get_activity_splits.
Inputs: activity_id (required), response_format.
garmin_get_activity_splitsSplits & pacing analysisARead-onlyIdempotent
Downloads the original .FIT recording and computes exact distance splits (default 1 km, interpolated at each boundary, pauses excluded), per-split HR, cadence and climb, the device laps, and a pacing verdict (even, negative split, faded).
Use this for "how was my pacing", "did I go out too fast", "compare km 1 to km 5". Works for any GPS or footpod activity recorded on a Garmin device.
Inputs: activity_id (required), split_meters, response_format.
garmin_get_body_batteryBody BatteryARead-onlyIdempotent
Per-day Body Battery: charged, drained, highest and lowest values.
Long ranges are fetched in chunks automatically (up to 366 days).
Inputs: start_date (required), end_date.
garmin_get_daily_summariesDaily summariesARead-onlyIdempotent
Per-day totals: steps, distance, active and total calories, resting/min/max heart rate, average and max stress, intensity minutes, floors, Body Battery high/low. Best tool for trends across weeks.
Long ranges are fetched in chunks automatically (up to 366 days).
Inputs: start_date (required), end_date.
garmin_get_dayOne day at a glanceARead-onlyIdempotent
Everything for one day in one call: daily summary (steps, calories, resting HR, stress, intensity minutes), sleep, overnight HRV, Body Battery and activities. Best first call for 'how recovered am I today' or 'how was yesterday'. Parts Garmin has no data for are omitted.
Inputs: date.
garmin_get_fitness_ageFitness ageBRead-onlyIdempotent
Garmin's fitness age estimate and its inputs for a date.
Inputs: date.
garmin_get_heart_rateHeart rate (all day)BRead-onlyIdempotent
One day's resting HR and the all-day heart-rate samples.
Inputs: date.
garmin_get_hrvHRVARead-onlyIdempotent
Per-night heart-rate variability: last-night average, weekly average, baseline range and status (balanced, unbalanced, low).
Long ranges are fetched in chunks automatically (up to 366 days).
Inputs: start_date (required), end_date.
garmin_get_hydrationHydrationARead-onlyIdempotent
Per-day logged water intake and goal.
Long ranges are fetched in chunks automatically (up to 366 days).
Inputs: start_date (required), end_date.
garmin_get_nutritionFood logARead-onlyIdempotent
Foods and macros logged in Garmin Connect's nutrition log for one day.
Inputs: date.
garmin_get_performance_metricsVO2 max, training effect & recoveryARead-onlyIdempotent
Garmin's own VO2 max, read the way Garmin Connect shows it, plus per-activity aerobic/anaerobic training effect, recovery time and performance condition. Decoded from the original .FIT files, since the Personal API has no VO2 max endpoint.
Returns the current VO2 max (whole number, as Garmin's apps round it, plus the precise value), every new VO2 max reading in the window (Garmin only updates it on qualifying runs and power-meter rides), and a row per activity.
Examples:
"what's my VO2 max?" / "how is my VO2 max trending?" -> last_n=20
"how hard was today's workout, how long to recover?" -> last_n=1 Each activity costs one file download, so keep last_n small unless a trend is asked for.
Inputs: last_n, activity_id, activity_type, response_format.
garmin_get_profileProfile & heart-rate zonesARead-onlyIdempotent
The user's Garmin profile settings (units, weight, height, birth year, lactate threshold where set) plus their heart-rate zones. Call this first when you need zones or units to interpret other data.
Inputs: no named parameters.
garmin_get_sleepSleepARead-onlyIdempotent
Per-night sleep: duration, deep/light/REM/awake time, sleep score, and timing.
Long ranges are fetched in chunks automatically (up to 366 days).
Inputs: start_date (required), end_date.
garmin_get_sleep_detailSleep detailARead-onlyIdempotent
One night's sleep in full: stages timeline, sleep score breakdown, respiration, restless moments, SpO2 and HR during sleep.
Inputs: date.
garmin_get_spo2Pulse OxCRead-onlyIdempotent
One day's SpO2 readings and acclimation.
Inputs: date.
garmin_get_stepsStepsARead-onlyIdempotent
Per-day step totals and goals.
Long ranges are fetched in chunks automatically (up to 366 days).
Inputs: start_date (required), end_date.
garmin_get_stressStressARead-onlyIdempotent
Per-day all-day stress levels.
Long ranges are fetched in chunks automatically (up to 366 days).
Inputs: start_date (required), end_date.
garmin_get_weightWeight & body compositionARead-onlyIdempotent
Every weigh-in in the range (Garmin usually reports weight in grams: divide by 1000 for kg), with BMI, body fat, muscle mass and water where a smart scale recorded them. Use for bulk/cut progress.
Long ranges are fetched in chunks automatically (up to 366 days).
Inputs: start_date (required), end_date.
garmin_get_weight_goalsWeight goalsBRead-onlyIdempotent
Weight goals in effect during the range.
Long ranges are fetched in chunks automatically (up to 366 days).
Inputs: start_date (required), end_date.
garmin_get_wellness_activitiesWellness activitiesARead-onlyIdempotent
Wellness activity summaries (e.g. breathwork and relaxation sessions) for the range.
Long ranges are fetched in chunks automatically (up to 366 days).
Inputs: start_date (required), end_date.
garmin_list_activitiesList activitiesARead-onlyIdempotent
List recorded activities (runs, gym sessions, rides…), newest first, with distance, time, pace, heart rate, training effect and Garmin's training load.
Examples:
"my runs this month" -> start_date="2026-10-01", activity_type="running"
"last 5 activities" -> limit=5 Use garmin_get_activity_splits on an activity_id for per-km splits and pacing.
Inputs: limit, offset, end_date, start_date, +2 more.
Tool Schema Changelog
Recent tool additions, removals, and schema changes observed during successful MCP inspections.
Loading tool schema changelog…
TDQS
Scored across 23 tools
Tools are organized around a clear pattern: one aggregated day tool plus per-metric range getters, which keeps most purposes distinct. A few boundaries could confuse an agent—garmin_get_day vs garmin_get_daily_summaries, and garmin_get_sleep vs garmin_get_sleep_detail—but the descriptions explicitly differentiate the aggregate vs range vs single-night-detail cases.
Nearly all tools follow garmin_get_<resource> or garmin_<verb>_<noun> (garmin_list_activities, garmin_download_activity_fit), which is predictable. The one deviation is garmin_api_get, which uses noun_verb ordering as a generic escape hatch, a minor inconsistency.
At 23 tools the surface is on the heavy side for the domain, though each metric-specific getter earns a reasonable place. The breadth of Garmin data (sleep, HRV, stress, activities, weight, nutrition) justifies most of them, but the aggregate plus per-metric split inflates the count.
Coverage is broad: profile, daily summaries, sleep (summary and detail), HRV, Body Battery, stress, steps, hydration, activities (list/get/splits/FIT download), performance metrics, weight and goals, SpO2, fitness age, and nutrition. The generic garmin_api_get escape hatch fills any remaining gaps, so there are no dead ends.
Maintenance
Related MCP Connectors
Garmin data in Claude & ChatGPT via the Garmin Health API. OAuth sign-in, no password sharing.
Garmin data in Claude: 135 tools — activities, sleep, HRV, training, workouts. Free, open source.
tri-train is a training platform for triathletes that syncs activities from Strava and Garmin and exposes them to Claude through a remote MCP server. Ask Claude how your last block went, why your run pace dropped, or whether you are fresh enough for Sunday's race, and it answers from your real data: activities with laps and grade-adjusted pace, weekly load and the performance management chart (CTL/ATL/TSB), sleep, HRV and resting heart rate, and your race calendar with predictions. Claude can also act: create and adjust planned workouts with structured intervals, push them to your Garmin watch, add races and write notes. Every change is journaled and can be undone. Read and write access are separate OAuth scopes, and the server enforces them on every call. Built and hosted in Switzerland by a triathlete; data stays on our own servers (Swiss revDSG / GDPR).
Connect Claude to your Intervals.icu watch data for fitness, workout review, and plan writing.
Related MCP Servers
- AlicenseBqualityBmaintenanceEnables users to analyze their own Garmin Connect data—activities, sleep, HRV, Body Battery, training readiness—directly inside Claude Desktop.131,323 npm2MIT
- AlicenseAqualityBmaintenanceProvides Claude Code and Claude Desktop with safe, read-only access to your local Garmin training data, readiness decisions, run details, and trends so you can get coaching advice in natural language.1599 PyPI9MIT
- AlicenseAqualityBmaintenanceDaash connects Garmin Connect to ChatGPT and Claude. Your assistant reads your runs, splits, sleep, HRV, Body Battery and recovery, and writes structured workouts and whole training plans to your Garmin calendar, so they're on your watch at the next sync. Free, hosted, open source. Works on free Claude.265MIT
- AlicenseBqualityBmaintenanceEnables Claude to access and query your Garmin Connect data—sleep, training, heart rate, and more—through a suite of read-only tools, with an optional write path for creating strength workouts.63MIT