Garmin MCP Server
Read-only MCP server that lets an AI agent query your own Garmin Connect data through Garmin's Personal API.
Search and inspect activities, including summaries, metadata, measurements, splits, and structured workouts.
Retrieve daily wellness data: summaries, steps, stress, heart rate, Body Battery, SpO2, hydration, and wellness activities.
Retrieve sleep and recovery data: sleep details/summaries, HRV summaries/range, and fitness age.
Retrieve body and profile data: weight/body composition, weight goals, heart rate zones, and profile settings.
Supports date/date-range queries up to 366 days, activity pagination/filtering, and optional intraday samples for large time-series tools.
All tools are read-only; unavailable Garmin Personal API data includes training readiness/status, VO2 max, personal records, and device lists.
Provides read-only tools for querying a user's own Garmin Connect data through Garmin's Personal API, covering activities (search and retrieve activities and their workouts), daily health metrics (daily summaries, steps, stress, heart rate, body battery, SpO2, hydration, wellness activities), sleep and recovery (sleep summaries, HRV, fitness age), and body/profile data (weight, weight goals, heart rate zones, profile settings).
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 MCP Server How did I sleep last night, and what was my body battery this morning?"
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 MCP Server
A read-only MCP server that lets an AI agent query your own Garmin Connect data through Garmin's official Personal API.
1. Create a personal API key
Sign in to Garmin Connect Web and open https://connect.garmin.com/app/settings/personalApiToken.
Create Key, accept the terms, pick an expiry (30 days – 1 year), and copy the key. It is shown only once — treat it like a password.
The server exchanges the key for a 24-hour access token and renews it automatically. When the key itself expires (Garmin emails you a week ahead), create a new one and update your config.
Related MCP server: Garmin MCP Worker
2. Install and verify
Requires uv and Python 3.11+.
cd c:\temp\garmin-mcp-server
uv syncCheck the key works (prints only field counts, no personal data):
$env:GARMIN_PERSONAL_API_KEY = "<your key>"; uv run garmin-mcp check3. Connect an MCP client
Claude Code
claude mcp add garmin --scope user -e GARMIN_PERSONAL_API_KEY=<your key> -- uv --directory c:\temp\garmin-mcp-server run garmin-mcpThen run /mcp in Claude Code to confirm garmin is connected.
Any other MCP client (stdio)
Most clients accept a JSON server entry like this:
{
"mcpServers": {
"garmin": {
"command": "uv",
"args": ["--directory", "c:\\temp\\garmin-mcp-server", "run", "garmin-mcp"],
"env": { "GARMIN_PERSONAL_API_KEY": "<your key>" }
}
}
}Tools
All tools are read-only. Dates are YYYY-MM-DD; a missing date means today.
Ranged tools accept up to 366 days and split requests to fit Garmin's per-call limits (28/31 days).
Tools marked † drop large intraday time series unless called with include_samples=true.
Area | Tools |
Activities |
|
Daily health |
|
Sleep & recovery |
|
Body & profile |
|
Not available in the Personal API (so not offered here): training readiness, training status, VO2 max, personal records, and device lists.
Sample .NET MAUI app (Android)
app/GarminCoach is a Blazor Hybrid MAUI app that embeds this MCP server and coaches you:
it reads the last 7 days of your own Garmin data through the read-only tools, shows every
tool call it made, asks your chosen AI model for one cycling session, and sanity-checks the
answer. Its shared coach core ships as the app/GarminCoach.Core library.
uv sync # Python server + its HTTP extra
dotnet build garmin-mcp-server.slnx # the app, its core and the .NET tests
dotnet test app/GarminCoach.Core.Tests # the .NET unit testsIn the app, open Settings, paste your Garmin personal API key and your OpenAI or
Anthropic key, then tap What should I ride today?. The app talks to the MCP server over
the Streamable HTTP transport (garmin-mcp http); on the Android emulator it reaches this
machine at http://10.0.2.2:8000. Point it at another address in Settings if your server
runs elsewhere.
React Native Android app
app/ReactNativeCoach is a React Native (bare CLI, TypeScript) version of the same coach for
Android. It reads the last 7 days through the read-only tools, shows every tool call, and asks
your chosen AI model for one cycling session. See
app/ReactNativeCoach/README.md for starting the server in HTTP
mode, running the app on an emulator, and pointing it at a server on another host.
cd app/ReactNativeCoach
npm ci
npm run typecheck
npm run test:ci # writes test-results/junit.xml and coverage/cobertura-coverage.xml
npm run android # with an Android emulator runningAndroid deploys with "not enough space"
If deployment to the emulator stops with
ADB0010: Mono.AndroidTools.InstallFailedException: ... Requested internal only, but not enough spacethe emulator's internal data partition is too small for a MAUI debug build, and Android's
default is to install to internal storage only. app/GarminCoach/GarminCoach.csproj sets
AndroidInstallLocation to auto, which lets the system fall back to external storage. If it
still fails, free space in the emulator with adb shell pm uninstall com.garmincoach.sample,
or recreate the AVD with a larger internal storage (Device Manager -> Wipe Data / edit disk size).
Security notes
The key is read only from the
GARMIN_PERSONAL_API_KEYenvironment variable and is never logged or included in error messages.Revoke access at any time by deleting the key on Garmin Connect Web.
The Personal API is licensed for personal use with your own data only.
Development
uv run pytestLicense
Licensed under the Apache License 2.0.
Available Tools
21 toolsget_activityBRead-only
Get one activity's summary, metadata, measurements and split summaries.
Inputs: activity_id (required).
get_activity_workoutsCRead-only
Get the structured workouts performed during an activity.
Inputs: activity_id (required).
get_body_batteryBRead-only
Get daily Body Battery reports (charged, drained, events) for a date range.
Set include_samples=true for the intraday Body Battery values (large).
Inputs: start_date (required), end_date, include_samples.
get_daily_summariesARead-only
Get daily wellness summaries for a date range (up to a year). Best for trends across many days.
Inputs: start_date (required), end_date.
get_daily_summaryBRead-only
Get one day's wellness summary: steps, calories, stress, Body Battery, intensity minutes, resting HR.
Inputs: date.
get_fitness_ageBRead-only
Get the latest Fitness Age as of a date, with the factors that drive it.
Inputs: date.
get_heart_rateARead-only
Get one day's heart rate: resting, min, max, 7-day resting average.
Set include_samples=true for the intraday heart rate time series (large).
Inputs: date, include_samples.
get_heart_rate_zonesBRead-only
Get the user's configured heart rate zones per sport.
Inputs: no named parameters.
get_hrvARead-only
Get one night's heart rate variability (HRV) summary and status.
Set include_samples=true for the individual overnight HRV readings.
Inputs: date, include_samples.
get_hrv_rangeBRead-only
Get daily HRV summaries for a date range. Best for HRV trends.
Inputs: start_date (required), end_date.
get_hydrationBRead-only
Get daily hydration intake and goals for a date range.
Inputs: start_date (required), end_date.
get_profile_settingsARead-only
Get profile settings: units, time zone, height, birth date, activity level, etc.
Inputs: no named parameters.
get_sleepBRead-only
Get one night's sleep: duration, stages, sleep score, SpO2, respiration, sleep stress.
date is the calendar day the sleep ended on (the morning you woke up).
Inputs: date.
get_sleep_summariesARead-only
Get nightly sleep summaries for a date range. Best for sleep trends.
Inputs: start_date (required), end_date.
get_spo2ARead-only
Get one day's blood oxygen (SpO2): average, lowest, sleep average, 7-day average.
Set include_samples=true for individual and hourly readings (large).
Inputs: date, include_samples.
get_stepsCRead-only
Get daily step totals and step goals for a date range.
Inputs: start_date (required), end_date.
get_stressCRead-only
Get daily stress levels for a date range.
Inputs: start_date (required), end_date.
get_weightARead-only
Get weight and body composition for a date range: daily latest weights and range average.
Weights are in grams.
Inputs: start_date (required), end_date.
get_weight_goalsCRead-only
Get the weight goals in effect over a date range.
Inputs: start_date (required), end_date.
get_wellness_activitiesCRead-only
Get wellness activity summaries (e.g. auto-detected moves) for a date range.
Inputs: start_date (required), end_date.
search_activitiesBRead-only
Search recorded activities (runs, rides, swims, strength, ...), newest first.
Args: start_date: Earliest activity date, YYYY-MM-DD. end_date: Latest activity date, YYYY-MM-DD. activity_type: Garmin activity type key, e.g. "running", "cycling", "lap_swimming". search: Free-text match on activity name. limit: Page size (1-100). start: Offset for pagination.
Inputs: limit, start, search, end_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 21 tools
Most tools target clearly distinct Garmin data domains and actions, such as activities, sleep, HRV, weight, and profile settings. The main ambiguity comes from singular/range pairs like get_daily_summary vs. get_daily_summaries and get_sleep vs. get_sleep_summaries, though the descriptions clarify their intended use.
The tool set is overwhelmingly consistent snake_case and mostly follows a get_<resource> pattern, with search_activities as the main verb deviation. Singular/plural naming variants like summary/summaries and range-specific suffixes are readable but slightly inconsistent.
At 21 tools, the surface is somewhat large but reflects the broad Garmin wellness and activity domain. Each metric group is reasonably scoped, though some singular/range pairs could potentially be consolidated.
The server covers a wide range of read-only Garmin data: activities, workouts, daily wellness, sleep, HRV, SpO2, hydration, weight, and profile settings. Some secondary areas such as devices, training status, VO2 max, or personal records are absent, but core health and activity workflows are well covered.
Maintenance
Related MCP Connectors
Garmin watch data for AI assistants: activities, sleep, HRV, recovery. Never writes to Garmin.
Adaptive running coach MCP server — training data, plans, and recovery for AI assistants.
Multi-tenant hosted MCP server for Oura Ring — 21 read-only tools, OAuth per user.
Garmin data in Claude & ChatGPT via the Garmin Health API. OAuth sign-in, no password sharing.
Related MCP Servers
- AlicenseAqualityBmaintenanceEnables MCP-capable AI apps to query a user's own Garmin sleep, HRV, stress, Body Battery, heart-rate, activity, and body-metric data through Garmin's official Personal API in a read-only, locally run setup.1487 PyPI1MIT
- AlicenseNot gradedqualityNot gradedmaintenanceA read-only remote MCP server that lets Claude query your own Garmin Connect wellness and activity data — sleep, HRV, Body Battery, stress, heart rate, daily summaries, and workout details — through Garmin's official Personal API, with OAuth sign-in so it works from mobile and desktop clients.MIT
- AlicenseNot gradedqualityNot gradedmaintenanceThis server provides a read-only remote connection between MCP clients and a Garmin Connect account. It allows users to query extensive personal health and activity data using natural language.MIT
- AlicenseAqualityBmaintenanceA read-only MCP server that lets AI assistants query a user's own training, recovery, sleep, activity, and wellness data through the official Garmin Connect Personal API. It can run locally or be self-hosted on Cloudflare Workers for access from Claude and other MCP clients.27575 npmMIT