Server data from the Official MCP Registry
Unofficial read-only Garmin Connect data: sleep, HRV, heart rate, stress, recovery analysis.
About
Unofficial read-only Garmin Connect data: sleep, HRV, heart rate, stress, recovery analysis.
Security Report
Valid MCP server (4 strong, 1 medium validity signals). No known CVEs in dependencies. Imported from the Official MCP Registry.
6 files analyzed · No issues found
Security scores are indicators to help you make informed decisions, not guarantees. Always review permissions before connecting any MCP server.
What You'll Need
Set these up before or after installing:
Environment variable: GARMIN_API_KEY
Environment variable: GARMIN_TZ
How to Install
Install command not verified. See the repository for install instructions.
View repositoryDocumentation
View on GitHubFrom the project's GitHub README.
garmin-mcp
English | Русский
Unofficial. This project is not affiliated with, endorsed by or supported by Garmin Ltd. "Garmin" is a trademark of Garmin Ltd. or its subsidiaries; it is used here only to describe compatibility.
An MCP server that gives Claude (or any other MCP client) read-only access to your own Garmin Connect data: sleep, HRV, heart rate, stress, Body Battery, daily activity, workouts and weight. It uses the official Garmin Connect Personal API.
The main use case is personal advice on sleep and wellbeing. The server computes averages, sleep regularity, sleep shortfall, deviations from your own baseline and links between your day and your sleep; Claude turns that into concrete recommendations.
MCP (Model Context Protocol) is the standard an AI assistant uses to call external tools. Claude Code starts
garmin-mcpas a child process and talks to it over stdin/stdout.
Quick start
-
API key. Open https://connect.garmin.com/app/settings/personalApiToken → Create Key → accept the terms → choose an expiry (30, 90, 180 days or 1 year) → copy the key. The key is shown once. Garmin emails you about a week before it expires.
-
Install — pick the option that fits your client:
Client How Claude Desktop Download garmin-mcp.mcpbfrom the latest release and open it. Claude Desktop asks for the API key (stored securely) and time zone. Bundled for macOS (Intel and Apple Silicon), Windows x64 and Linux x64Claude Code (plugin) /plugin marketplace add sasha-sup/garmin-mcp, then/plugin install garmin-mcp@garmin-mcp; Claude Code asks for the key. On first start the plugin downloads the release binary and verifies its SHA-256. macOS and LinuxClaude Code (binary) Install the binary (row below), then claude mcp add -s user garmin -- garmin-mcp -env-file /path/to/.envBinary Archives for Linux, macOS and Windows on the releases page, or go install github.com/sasha-sup/garmin-mcp/cmd/garmin-mcp@latestDocker docker run -i --rm -e GARMIN_API_KEY -e GARMIN_TZ ghcr.io/sasha-sup/garmin-mcpas the MCP command (images for amd64 and arm64)Any MCP client Listed in the MCP Registry as io.github.sasha-sup/garmin-mcpFrom source make build(Go 1.27.4+; Go 1.21+ downloads it automatically) →bin/garmin-mcp -
Configure (binary and source installs; the plugin and the bundle ask for the values instead):
cp .env.example .env chmod 600 .env # only your user can read the key $EDITOR .env # set GARMIN_API_KEY and GARMIN_TZ -
Check:
garmin-mcp -env-file .env -check # auth ok: access token valid until 2026-11-13 10:33:12 # profile ok: Garmin time zone Europe/Berlin, server time zone Europe/Berlin (CET +01:00) # data ok: 7 of the last 7 days have a daily summaryClaude Desktop, in
claude_desktop_config.json, if you prefer the binary over the bundle:{ "mcpServers": { "garmin": { "command": "/absolute/path/garmin-mcp", "args": ["-env-file", "/absolute/path/.env"] } } } -
Ask Claude, for example:
- "Analyse my sleep over the last month and give me recommendations"
- "How recovered am I today? Is a hard workout a good idea?"
- "How have my resting heart rate and HRV changed over six months?"
- "What hurts my sleep more: stress or late workouts?"
Or run a ready-made prompt. In Claude Code they are
/mcp__garmin__sleep_review,/mcp__garmin__wellbeing_review(both take an optional number of days) and/mcp__garmin__readiness_check.
Tools
| Tool | Returns | Period |
|---|---|---|
garmin_sleep_analysis | Sleep analysis: average duration vs Garmin's baseline sleep need and weekly shortfall, median sleep onset and wake time and their spread, weekday/weekend shift (social jetlag), stage shares, sleep score trend, sleep heart rate/HRV/SpO2/breathing, and factors from the previous day (stress above your usual, late or hard workouts, low step count, late sleep onset → score, HRV and sleep heart rate with and without; differences are shown only with ≥ 5 nights in each group) | up to 366 days, default 28 |
garmin_sleep | Per night: bedtime, wake time, stages, score and sub-scores, heart rate, stress, SpO2, breathing, sleep need, Garmin's feedback | up to 366, 7 |
garmin_recovery_status | One-day readiness snapshot: sleep; HRV, resting HR, sleep HR, breathing rate and yesterday's stress each compared with your own previous 28 days (mean, SD, z-score, days of history); overnight Body Battery charge; training load of the last 7 vs 28 days; plain-language signals and the method used. Baseline-relative signals need ≥ 14 days of history | 1 day |
garmin_trends | Weekly or monthly averages: resting HR, HRV, sleep, steps, stress, Body Battery, intensity minutes, workouts, training load, weight | up to 731 days, 84 |
garmin_daily_summary | Per day: steps, distance, calories, heart rate, intensity minutes, stress, Body Battery, breathing, SpO2 | up to 366, 7 |
garmin_hrv | Overnight HRV, 7-day average, personal baseline band, Garmin status | up to 366, 14 |
garmin_body_battery | Charged/drained, min/max, events (sleep, workouts), Garmin's feedback, optional intraday timeline | up to 31, 3 |
garmin_heart_rate | Heart rate for one day in local-time intervals (5, 10, 15, 20, 30, 60, 120, 180, 240 min) | 1 day |
garmin_activities | Workouts: type, duration, distance, pace/speed, heart rate, time in zones, training load, training effect, VO2max | default 30 days, up to 100 items |
garmin_activity | Full summary of one workout | — |
garmin_profile | Time zone, heart rate zones, Fitness Age, latest weight | — |
garmin_weight | Weigh-ins: weight, BMI, body fat, muscle mass, body water | up to 731, 90 |
garmin_api_get | Raw JSON from an allow-listed endpoint (hourly SpO2, daily stress and steps, hydration, …), truncated at 100 KB. Nutrition and menstrual cycle only with GARMIN_ALLOW_SENSITIVE=1 | — |
All dates are local calendar dates (YYYY-MM-DD). Sleep is filed under the wake-up date:
the night from 10 to 11 November is 2026-11-11.
Not in the API
The Personal API does not expose Training Readiness, Training Status, Acute Load or a VO2max trend.
garmin_recovery_status computes comparable signals itself (HRV, resting HR, sleep, the sum of
activityTrainingLoad over 7 and 28 days) and labels them as computed by this server, not by Garmin.
Configuration
| Variable | Purpose | Default |
|---|---|---|
GARMIN_API_KEY (or GARMIN_API) | Personal API key. Without it the server starts and lists its tools, but every call returns an error explaining how to set it | — (required for data) |
GARMIN_TZ | Your IANA time zone, e.g. Europe/Berlin. Decides what "today" is. garmin_profile warns if it differs from your Garmin profile | system zone |
GARMIN_CACHE_DIR | Cache directory, or off | user cache dir: ~/.cache/garmin-mcp on Linux, ~/Library/Caches/garmin-mcp on macOS |
GARMIN_REGION | global or cn | global |
GARMIN_LOG_LEVEL | debug, info, warn, error (logs go to stderr) | info |
GARMIN_ALLOW_SENSITIVE | 1 enables the nutrition and menstrual-cycle endpoints in garmin_api_get | off |
Flags: -env-file PATH (the environment wins over the file; the file may only set GARMIN_*), -check, -clear-cache, -version.
How it works
- Authentication. The key is exchanged for an access token (a JWT valid for 24 hours; there is
no refresh token):
POST /personalapitoken-service/personal-api/personal-api-key/tokenwithAuthorization: ApiKey <key>. Every other request carriesAuthorization: Bearer <token>. The token lives only in memory and is renewed 5 minutes before expiry, and once on HTTP 401. One request performs the renewal; concurrent requests wait for it, but never longer than their own timeout. - Range limits. Garmin answers
400when a period is too long: sleep and Body Battery 31 days, stress and steps 28, daily summaries 1 year. The dedicated tools split requests into chunks and run them in parallel (at most 4 at a time).garmin_api_getpasses dates through unchanged, so rawstress_daily/steps_dailyrequests must stay within 28 days. - Cache. Responses are stored per day in
GARMIN_CACHE_DIR. A day with data that was fetched more than 72 hours after it ended is final and never requested again; more recent days are cached for 10 minutes because the watch keeps syncing. A day without data (watch not worn or not synced yet) is re-checked every 6 hours and becomes final only after 30 days. Re-analysing a year costs a handful of requests, not hundreds. If the watch synced very late and past days came in partially, rungarmin-mcp -clear-cache. - Retries. On
429and5xx: up to 3 retries with exponential backoff, honouringRetry-After. Garmin does not document a rate limit.
Privacy and security
- The server only reads: the API has no write methods and every tool is marked
readOnlyHint. - The key and token are sent only to Garmin's host; redirects are not followed, so the key cannot leak to another address. Logs and error messages never contain the key or token.
- The cache holds health data: the
v1directory insideGARMIN_CACHE_DIRgets mode0700, files0600; symlinks and oversized files in the cache are ignored. Clear it withgarmin-mcp -clear-cacheor by deleting the directory. -env-fileaccepts onlyGARMIN_*variables, so a tampered file cannot setHTTPS_PROXYorSSL_CERT_FILEto intercept the key.- Nutrition and menstrual-cycle data never reach the model unless you set
GARMIN_ALLOW_SENSITIVE=1. - Whatever the tools return is sent to the model provider (Anthropic for Claude) as part of the conversation.
.envand*.dbare in.gitignore. If the key leaks, delete it on the Personal API Key page; every token issued for it stops working too.- Recommendations based on this data are not medical advice.
Development
make test # unit tests with -race against a synthetic fake Garmin API (no real data needed)
make lint # golangci-lint v2
make vuln # govulncheck
make live # every tool against the real API (needs .env); prints response sizes only
make all # lint + test + vuln + build
make ci-lint # validate the GitHub Actions workflows (actionlint)
Releases
Push a tag vX.Y.Z from a commit where plugin/.claude-plugin/plugin.json has version X.Y.Z.
.github/workflows/release.yml then builds the archives and garmin-mcp.mcpb (GoReleaser),
pushes ghcr.io/sasha-sup/garmin-mcp:X.Y.Z (amd64 and arm64) and publishes server.json to the
MCP Registry with GitHub OIDC (no stored secrets).
CI
GitHub Actions (.github/workflows/ci.yml) runs on pushes to main, on pull requests, weekly
(new vulnerabilities appear without code changes) and on demand:
| Job | What it does |
|---|---|
| Lint | go mod tidy leaves go.mod/go.sum unchanged; golangci-lint v2.15.0 with .golangci.yml |
| Test | go vet, go test -race with coverage on Ubuntu and macOS, builds the binary |
| Vulnerability scan | govulncheck over the code and its dependencies |
Actions are pinned to commit SHAs, the workflow has only contents: read, and checkout does not
persist the token. Dependabot proposes Go module and action updates weekly. The live test against
the real API does not run in CI: no key is given to CI.
Layout:
cmd/garmin-mcp/ entry point: flags, config, stdio server
internal/config/ environment and .env loading
internal/garmin/ HTTP client (token, retries, limits), response models, cached range-aware service
internal/cache/ file cache with atomic writes
internal/tools/ MCP tools, sleep and recovery analysis, prompts
internal/civil/ calendar date without time
Garmin's official OpenAPI spec is embedded in
https://developer.garmin.com/gc-developer-program/personal/swagger-docs/; the response formats in
internal/garmin/models.go were checked against live API responses (November 2026).
License
Reviews
No reviews yet
Be the first to review this server!
More Developer Tools MCP Servers
Rea
Freeby Morluto · Developer Tools
Reverse engineer anything from your terminal or agent with one CLI and MCP server.
Paperclip
Freeby Paperclipai · Developer Tools
Trending hip-hop artist momentum scores across four cultural dimensions.
Scrapling
Freeby D4Vinci · Developer Tools
Web scraping with stealth HTTP, real browsers, and Cloudflare bypass. CSS selectors supported.
Toleno
Freeby Toleno · Developer Tools
Toleno Network MCP Server — Manage your Toleno mining account with Claude AI using natural language.
MCP Marketplace
Freeby mcp-marketplace · Developer Tools
Search and install MCP servers from inside your AI client.
mcp-creator-python
Freeby mcp-marketplace · Developer Tools
Create, build, and publish Python MCP servers to PyPI — conversationally.
