Garmin Mcp Unofficial
About
<!-- delx-wellness header v2 --> <h1 align="center">Garmin MCP</h1> <div align="center"> <img src="assets/banner.png" alt="Garmin MCP — Garmin MCP for AI agents" width="85%" /> </div> <h3 align="center"> Give your AI agent your Garmin Body Battery, training readiness, sleep, HRV and activities.<br> Local-first MCP…
Explore
- Local-first: tokens never leave your machine.
- Pure Node login – no Python required by default.
- Provides daily and weekly summaries, plus intraday investigation prompts.
- Covers sleep, HRV, Body Battery, stress, training readiness, activities, heart rate, and more.
- Optional SQLite cache and privacy mode settings.
- Garmin password is never stored – only short-lived tokens persist locally.
Setting up with Highlight
This MCP is not yet compatible with Highlight’s one-click setup. However, you can still use it with Highlight by following these steps:
- Download and install Highlight from highlightai.com/download
- Navigate to the plugins tab and select "Add Custom Plugin"
-
Configure the plugin with the settings below
Plugin Name
Garmin Mcp UnofficialCommand (node, npx, python, etc.)Please refer to the README for specific instructions on how to obtain API keys or other required environment variables.
- Enable "Start Automatically" if you want the plugin to start when Highlight launches
From the repository
GARMIN_TOKEN_PATH=~/.garmin-mcp/garmin_tokens.json
GARMIN_PRIVACY_MODE=summary # summary | structured | raw
GARMIN_CACHE=sqlite # optional read-through cache
GARMIN_CACHE_PATH=~/.garmin-mcp/cache.sqlite
GARMIN_DOMAIN=garmin.com # or garmin.cn for China accounts
No Garmin developer app is required. setup only writes local MCP configuration; it does not ask for your Garmin password.
npx -y garmin-mcp-unofficial setup # writes local config
npx -y garmin-mcp-unofficial auth # built-in login, prompts for credentials locally (no Python needed)
npx -y garmin-mcp-unofficial doctor # verifies you're ready
Or one shot:
npx -y garmin-mcp-unofficial setup --auth
auth runs a self-contained Node login and prompts locally for Garmin email, password and MFA when needed. The MCP does not store your Garmin password — only Garmin Connect tokens, saved at ~/.garmin-mcp/garmin_tokens.json with user-only permissions.
> 📺 Want to see exactly what each command prints? The auth quickstart walkthrough shows real --help, auth, auth --json and doctor output for the full first-call journey.
Prefer the old Python flow? auth --use-python (or auth --install-helper to install the garminconnect package, with an isolated virtualenv fallback under ~/.garmin-mcp/venv) still works.
Then add this to your MCP client config:
{
"mcpServers": {
"garmin": {
"command": "npx",
"args": ["-y", "garmin-mcp-unofficial"]
}
}
}
npx -y garmin-mcp-unofficial setup --client hermes
npx -y garmin-mcp-unofficial auth
npx -y garmin-mcp-unofficial doctor --client hermes
hermes mcp test garmin
After Hermes config changes, use /reload-mcp or hermes mcp test garmin. Don't restart the gateway for normal data access.
garmin_data_inventory
Inventory supported Garmin data domains, auth scope requirements, privacy boundary and recommended first calls. Does not call Garmin APIs or expose user data.
garmin_agent_manifest
Machine-readable install, runtime and client guidance for AI agents. Does not call Garmin or expose secrets.
garmin_capabilities
Explain supported Garmin data, privacy boundaries, recommended agent workflow and project links.
garmin_quickstart
Personalized 3-step setup walkthrough for the human user. Adapts to current state (env vars set? token present? what's next?). Call this first when the user asks 'how do I connect Garmin?'
garmin_demo
Returns realistic example payloads of garmin_daily_summary, garmin_wellness_context, and garmin_get_body_battery_day so agents see the contract before any real Garmin Connect call.
garmin_profile_get
Read the shared Delx wellness profile (~/.delx-wellness/profile.json). Returns the user's preferred name, body basics, goals, devices, training context, nutrition context, agent preferences, and missing critical fields. Cross-connector — the same profile is also available from other Delx Wellness MCPs (WHOOP, Oura, Nourish, Fitbit, etc). Read-only.
garmin_profile_update
Persist a partial patch to the shared Delx wellness profile (~/.delx-wellness/profile.json). REQUIRES explicit_user_intent=true. Top-level fields stored: profile (preferred_name, language, timezone, units, age_or_birth_year, height, weight, sex_or_gender_context), goals, devices, training, nutrition, preferences, safety, notes. NEVER stores OAuth tokens, API keys, refresh tokens, cookies, or any secret-shaped field — writes will be rejected at validation time. Cross-connector — the same profile is read by other Delx Wellness MCPs.
garmin_onboarding
Return the 11-question Delx wellness onboarding flow (in English or pt-BR) plus the current shared profile state and missing critical fields. Read-only. The agent should ask these questions one-by-one, then call garmin_profile_update with explicit_user_intent=true to save. The same profile is reused by every Delx Wellness connector (WHOOP, Oura, Nourish, etc.) — agents can call the equivalent {connector}_onboarding tools to cover their respective domains, or rely on this one since all connectors share the same questions.
garmin_auth_instructions
Explain the local Garmin Connect authentication flow without asking the user to paste secrets into an agent.
garmin_get_profile
Get the authenticated Garmin profile using the configured privacy mode.
garmin_get_user_settings
Get Garmin account user settings such as units and display preferences.
garmin_list_devices
List devices registered to the Garmin account.
garmin_get_primary_training_device
Get the primary Garmin training device when available.
garmin_get_daily_summary
Get Garmin daily movement and wellness summary for a date.
garmin_get_steps_day
Get Garmin daily steps and summary chart for a date.
garmin_get_heart_day
Get Garmin daily heart-rate samples and resting heart-rate context for a date. Not medical advice.
garmin_get_sleep_day
Get Garmin sleep summary, stages and sleep window for a date. Not medical advice.
garmin_get_stress_day
Get Garmin stress summary and samples for a date. Not medical advice.
garmin_get_body_battery_day
Get Garmin Body Battery daily report for a date. Not medical advice.
garmin_get_body_battery_events
Get Garmin Body Battery charge/drain events for a date. Not medical advice.
garmin_get_hrv_day
Get Garmin HRV status and overnight HRV metrics for a date when available. Not medical advice.
garmin_get_training_readiness_day
Get Garmin training readiness for a date when supported by the device/account. Not medical advice.
garmin_get_training_status_day
Get Garmin aggregated training status for a date when supported by the device/account. Not medical advice.
garmin_get_respiration_day
Get Garmin respiration data for a date when available. Not medical advice.
garmin_get_spo2_day
Get Garmin Pulse Ox / SpO2 data for a date when available. Not medical advice.
garmin_get_intensity_minutes_day
Get Garmin intensity minutes for a date.
garmin_get_hydration_day
Get Garmin hydration summary for a date when available.
garmin_get_weight_range
Get Garmin weight/body-composition logs for a date range. Not medical advice.
garmin_list_activities
List recent Garmin activities. Supports pagination, optional date filters and privacy modes.
garmin_get_activity
Get a Garmin activity summary by activity id.
garmin_get_activity_details
Get detailed Garmin activity samples when available.
garmin_activity_series
Bounded time-series for one activity metric. Returns exact stats computed on full-resolution samples plus a downsampled series capped at 500 points, so a 3-hour ride at 1 Hz never blows the context window. Prefer garmin_get_activity / splits / hr_zones first; reach for this when you actually need the shape of the effort over time. GPS is never returned here.
garmin_get_activity_splits
Get Garmin activity splits/laps by activity id.
garmin_get_activity_weather
Get Garmin activity weather by activity id when available.
garmin_get_activity_hr_zones
Get Garmin activity heart-rate zone time by activity id when available.
garmin_connection_status
Check local Garmin config, token file, Node version, privacy mode, cache readiness and optional MCP client readiness without calling Garmin or exposing secrets.
garmin_cache_status
Show optional local SQLite cache status. Enable with GARMIN_CACHE=sqlite or GARMIN_CACHE=true.
garmin_privacy_audit
Return local privacy, cache, token-path and env-presence posture without revealing secret values.
garmin_disconnect_local
Delete the local Garmin token file. This does not change the Garmin account; use only when the user explicitly wants to disconnect this MCP. Gated by explicit_user_intent: true (requires explicit user intent).
garmin_daily_summary
Build a practical daily summary from Garmin activity, sleep, heart-rate, HRV, stress and Body Battery when available. Read-only and non-medical.
garmin_weekly_summary
Build a weekly Garmin scorecard with movement, sleep, HRV, stress, Body Battery, bottlenecks and actions. Read-only and non-medical.
garmin_wellness_context
Normalize Garmin readiness, sleep score, Body Battery and recent movement load into the shared wellness_context shape for recommendation engines.
Start with these:
- garmin_connection_status — verify local setup before calling Garmin Connect
- garmin_data_inventory — inventory supported data domains, scopes, privacy modes and recommended first calls without calling Garmin APIs.
- garmin_daily_summary — daily readiness, sleep, load, action candidates
- garmin_weekly_summary — scorecard, bottlenecks, next-week plan
Auth & diagnostics
- garmin_capabilities, garmin_agent_manifest, garmin_auth_instructions, garmin_privacy_audit
Profile & devices
- garmin_get_profile, garmin_get_user_settings
- garmin_list_devices, garmin_get_primary_training_device
Daily wellness signals (each takes a date)
- garmin_get_daily_summary, garmin_get_steps_day
- garmin_get_sleep_day, garmin_get_heart_day, garmin_get_hrv_day
- garmin_get_stress_day, garmin_get_body_battery_day, garmin_get_body_battery_events
- garmin_get_training_readiness_day, garmin_get_training_status_day
- garmin_get_respiration_day, garmin_get_spo2_day
- garmin_get_intensity_minutes_day, garmin_get_hydration_day
Activities
- garmin_list_activities, garmin_get_activity_details
Body & weight
- garmin_get_weight_range
Claude Desktop / Cursor
Paste into your MCP client config file to install this server.
{
"mcpServers": {
"garmin mcp unofficial": {
"garmin": {
"command": "npx",
"args": [
"-y",
"garmin-mcp-unofficial"
]
}
}
}
}
McpServers
{
"garmin": {
"command": "npx",
"args": [
"-y",
"garmin-mcp-unofficial"
]
}
}
<!-- delx-wellness header v2 -->
<h1 align="center">Garmin MCP</h1>
<div align="center">

</div>
<h3 align="center">
Give your AI agent your Garmin Body Battery, training readiness, sleep, HRV and activities.<br>
Local-first MCP server — <strong>tokens never leave your machine</strong>.
</h3>
<p align="center">
<a href="https://www.npmjs.com/package/garmin-mcp-unofficial"></a>
<a href="https://www.npmjs.com/package/garmin-mcp-unofficial"></a>
<a href="LICENSE"></a>
<a href="https://wellness.delx.ai/connectors/garmin"></a>
</p>
<p align="center">
<a href="https://github.com/davidmosiah/garmin-mcp/stargazers"></a>
<a href="https://modelcontextprotocol.io"></a>
<a href="https://github.com/davidmosiah/delx-wellness-hermes"></a>
<a href="https://github.com/davidmosiah/delx-wellness"></a>
</p>
> ⚡ One-command install with Delx Wellness for Hermes:
> npx -y delx-wellness-hermes setup — preconfigures this connector and the full Delx Wellness stack in a dedicated Hermes profile.
>
> Or wire it standalone into Claude Desktop / Cursor / ChatGPT Desktop — see the install section below. Runnable examples live in the Delx Agent Workbench.
---
<!-- /delx-wellness header v2 -->
Local-first MCP server that connects AI agents to your Garmin sleep, HRV, Body Battery, stress, training readiness and activities.
> Unofficial project. Not affiliated with, endorsed by or supported by Garmin. This is not official Garmin Health API partnership access — it uses the unofficial Garmin Connect personal-token mode.
Built by David Mosiah for people who use Claude, Cursor, Hermes, OpenClaw or other MCP-compatible agents to think about training, sleep and recovery — without copy-pasting numbers from the Garmin Connect app.
Part of Delx Wellness, a registry of local-first wellness MCP connectors.
> If this connector helps your agent workflow, please star the repo. Stars make the project easier for other AI builders to discover and help Delx keep shipping local-first wellness infrastructure.
<p align="center">
</p>
Why this exists
Garmin produces some of the best processed wellness signals — sleep stages, HRV status, Body Battery, stress, training readiness, training status, intensity minutes — but its official Garmin Health API is partner-licensed and not self-serve for individuals.
This package gives individual Garmin users a practical bridge: it logs into Garmin Connect with your own credentials locally (never sent to any agent), keeps tokens on your machine, and exposes Garmin signals through the Model Context Protocol. Your password never reaches the MCP — only short-lived Garmin Connect tokens are stored.
Setup in 60 seconds
No Garmin developer app is required. setup only writes local MCP configuration; it does not ask for your Garmin password.
npx -y garmin-mcp-unofficial setup # writes local config
npx -y garmin-mcp-unofficial auth # built-in login, prompts for credentials locally (no Python needed)
npx -y garmin-mcp-unofficial doctor # verifies you're ready
Or one shot:
npx -y garmin-mcp-unofficial setup --auth
auth runs a self-contained Node login and prompts locally for Garmin email, password and MFA when needed. The MCP does not store your Garmin password — only Garmin Connect tokens, saved at ~/.garmin-mcp/garmin_tokens.json with user-only permissions.
> 📺 Want to see exactly what each command prints? The auth quickstart walkthrough shows real --help, auth, auth --json and doctor output for the full first-call journey.
Prefer the old Python flow? auth --use-python (or auth --install-helper to install the garminconnect package, with an isolated virtualenv fallback under ~/.garmin-mcp/venv) still works.
Then add this to your MCP client config:
{
"mcpServers": {
"garmin": {
"command": "npx",
"args": ["-y", "garmin-mcp-unofficial"]
}
}
}
Try it with your agent
Three things to ask first:
Use garmin_connection_status to check setup, then run garmin_daily_summary.
Give me a 5-line operating brief for today.
Call garmin_weekly_summary with response_format=json. Identify my biggest
recovery/sleep/stress bottleneck and give me a next-week plan.
Use the garmin_intraday_investigation prompt for date=today, focus=stress.
Don't claim Garmin can prove anything it can't.
Data availability
This package reads processed Garmin Connect data via the unofficial personal-token mode. When this README says raw, it means upstream Garmin Connect JSON — not raw accelerometer / gyroscope / continuous device telemetry.
| Data | Available | Notes |
|---|:---:|---|
| Sleep duration + stages + score | ✓ | When the device/account supports it |
| HRV status + overnight HRV | ✓ | When supported by device/account |
| Body Battery (daily + events) | ✓ | Charge/drain reports |
| Stress samples + daily summary | ✓ | Per-day stress context |
| Training readiness + training status | ✓ | When supported by device/account |
| Daily movement (steps, calories, distance, floors, intensity minutes) | ✓ | Standard wellness signals |
| Heart rate (resting + daily samples) | ✓ | Per-day samples and resting HR |
| Activities + details + splits + zones | ✓ | Recent activities and detail payloads |
| Body composition / weight + hydration | ✓ | When logged |
| Continuous device telemetry / accelerometer / gyroscope | — | Not exposed by Garmin Connect web endpoints |
> Garmin can change private auth or endpoints at any time. Failures should be treated as integration drift, not user error.
Tools
Start with these:
- garmin_connection_status — verify local setup before calling Garmin Connect
- garmin_data_inventory — inventory supported data domains, scopes, privacy modes and recommended first calls without calling Garmin APIs.
- garmin_daily_summary — daily readiness, sleep, load, action candidates
- garmin_weekly_summary — scorecard, bottlenecks, next-week plan
Auth & diagnostics
- garmin_capabilities, garmin_agent_manifest, garmin_auth_instructions, garmin_privacy_audit
Profile & devices
- garmin_get_profile, garmin_get_user_settings
- garmin_list_devices, garmin_get_primary_training_device
Daily wellness signals (each takes a date)
…
Sign in to leave a review
Use Google, GitHub, or an email account so ratings stay tied to real people.
No reviews posted yet.



