garmin-everything-mcp
Integrates with Garmin Connect to expose data and operations across sleep, HRV, stress, body battery, heart rate, activities, training metrics, gear, courses, calendars, reports, golf, menstrual health, and more. Includes reflection-generated tools plus hand-written tools for compact daily ranges, downsampled activity time series, sleep detail, intraday metrics, raw API GET requests, endpoint discovery, export, and coverage inspection.
This server does not currently have a deployable release on Glama. Follow the repository's setup instructions to install and configure it for your MCP client, including any required credentials and local dependencies.
garmin_mcp is excellent, but it hand-wraps 105 calls of the python-garminconnect library, pinned at 0.3.2. The library is now at 0.3.20 with 348 public methods: sleep need and skin temperature, HRV baselines, training load balance, ECG, glucose, health snapshots, jet lag, race predictions, power curves, one-rep max, gear, courses, calendars, reports, golf, menstrual health, and dozens of daily/weekly/monthly range endpoints.
This server does not hand-wrap anything. It introspects garminconnect.Garmin at startup and turns every
public method into an MCP tool: name, typed parameters, defaults and docstring come straight from the library.
When python-garminconnect gains a method, this server gains a tool. A shipped list of what garmin_mcp already
provides keeps the two servers disjoint, and eight hand-written tools do what reflection cannot: compact ranges,
downsampled time series, a raw endpoint escape hatch, and an offline export.
Highlights
Reflection-generated tools: 178 read-only tools in the default
extrasprofile, 265 inall, 338 with writes. See docs/COVERAGE.md for the full 348-row matrix.Zero duplicates with garmin_mcp: the
extrasprofile excludes every method and tool name garmin_mcp registers.8 hand-written power tools:
garmin_daily_range,garmin_activity_timeseries,garmin_sleep_detail,garmin_intraday,garmin_raw_get,garmin_endpoint_catalog,garmin_export,garmin_coverage.Context-safe by default: a 60 KB size budget summarises huge payloads instead of flooding the model; a 1 MB activity detail becomes a 4 KB columnar series.
Privacy by default: email, names, birth date, address and phone fields are redacted recursively.
Write-safe by default: every
add_/create_/delete_/update_/set_/upload_/...method stays hidden unless you opt in twice (profile=fullandGARMIN_EVERYTHING_WRITES=1). Tools carry MCPreadOnlyHintannotations.Same auth as garmin_mcp: authenticate once with
garmin-mcp-auth; both servers read~/.garminconnect.
Related MCP server: Garmin Health MCP Server
Quick start
Requires Python 3.12+ and uv.
# 1. Authenticate once (this is garmin_mcp's auth tool; tokens land in ~/.garminconnect)
uvx --python 3.12 --from git+https://github.com/Taxuspt/garmin_mcp garmin-mcp-auth
# 2. Run the server (stdio)
uvx --python 3.12 --from git+https://github.com/dlekdns08/garmin-everything-mcp garmin-everything-mcpThe server never prompts for credentials and never stores anything but what the library already keeps.
The composition recipe: run both servers
Claude Desktop (~/Library/Application Support/Claude/claude_desktop_config.json) or any MCP client:
{
"mcpServers": {
"garmin": {
"command": "uvx",
"args": ["--python", "3.12", "--from", "git+https://github.com/Taxuspt/garmin_mcp", "garmin-mcp"]
},
"garmin-everything": {
"command": "uvx",
"args": ["--python", "3.12", "--from", "git+https://github.com/dlekdns08/garmin-everything-mcp", "garmin-everything-mcp"],
"env": {
"GARMIN_EVERYTHING_PROFILE": "extras"
}
}
}
}Claude Code:
claude mcp add garmin -- uvx --python 3.12 --from git+https://github.com/Taxuspt/garmin_mcp garmin-mcp
claude mcp add garmin-everything -e GARMIN_EVERYTHING_PROFILE=extras -- \
uvx --python 3.12 --from git+https://github.com/dlekdns08/garmin-everything-mcp garmin-everything-mcpextras is the default, so the env block is optional. With it, no tool name exists in both servers.
Prefer a single server? Use GARMIN_EVERYTHING_PROFILE=all and drop garmin_mcp (you lose its workout builders
and FIT parsing, which are not library methods).
The hand-written tools
Tool | What it does |
| One compact row per day for |
| Maps |
| The sleep sub-objects garmin_mcp drops: sleep need and next-night need, naps, skin-temperature deviation, breathing disruptions, HRV series + status, movement, restless moments, body battery, heart rate, stress, respiration. |
| Downsampled intraday series: |
| GET any Connect API path. |
| 54 paths verified against a real account plus ~270 path templates extracted from the library source by |
| Writes one JSONL file per metric (one line per day) to |
| Live matrix: library version, profile, tools per group, what garmin_mcp covers, what was excluded and why. |
Examples (as the model would call them):
garmin_daily_range(metric="sleep_score", start="2026-11-11", end="2026-11-17")
-> {"metric":"sleep_score","calls":1,"rows":7,"data":[{"date":"2026-11-11","value":65}, ...]}
garmin_activity_timeseries(activity_id="12345678901", metrics="directHeartRate,directPower", points=100)
-> {"totalPoints":1188,"returnedPoints":100,"columns":["directTimestamp","sumDuration","directHeartRate","directPower"],
"units":{"directHeartRate":"bpm","directPower":"watt"},"series":{"directHeartRate":[127,135,...],...}}
garmin_sleep_detail(date="2026-11-16", include="hrv,skin_temp,breathing")
-> {"summary":{"sleepTimeSeconds":24462,"sleepNeed":{"actual":500,"feedback":"INCREASED",...},"sleepScores":{...}},
"hrv":{"hrvData":{"count":86,"returned":120,"values":[[1794746901000,32.0],...]},"avgOvernightHrv":48.0,"hrvStatus":"UNBALANCED"},
"skin_temp":{"avgSkinTempDeviationC":0.3},"breathing":{"breathingDisruptionData":{...}}}
garmin_raw_get(path="/wellness-service/stats/daily/sleep/score/2026-11-11/2026-11-17", jq_path="[*].value")
-> [65,54,48,69,86,73,76]Everything else is auto-generated. A few of the 178 extras: get_sleep_daily, get_sleep_stats_weekly,
get_hrv_data_range, get_daily_body_battery_stats, get_training_four_week_load_balance,
get_training_readiness_range, get_heart_rate_zones_v2, get_power_zones, get_sensors, get_ecg_list,
get_glucose_data, get_health_snapshots, get_jetlag_status, get_personal_record_candidates,
get_fastest_splits, get_activity_laps, get_activity_power_curve, get_gear_list, get_calendar_week,
get_upcoming_events, get_golf_summary, get_menstrual_cycle_summary, search_activities, ...
Profiles and environment
Variable | Default | Effect |
|
|
|
| unset | Must be |
| all | Comma list of groups to keep: |
| unset | Comma allowlist of auto-generated tool names (case-insensitive), same semantics as garmin_mcp. |
| unset | Comma denylist; ignored when the allowlist is set. |
|
| Size budget per result; larger payloads are summarised. |
|
| Recursive redaction of personal keys. Set |
|
| Seconds before a stalled Garmin request is abandoned. |
|
| Default directory for |
|
| Where the |
|
| Also |
|
| Token directory, identical to garmin_mcp. |
|
| Base64 token file fallback, identical to garmin_mcp. |
|
| Use garmin.cn. |
The hand-written garmin_* tools are always registered.
Size budget and redaction
Every tool returns a JSON string. If it exceeds GARMIN_EVERYTHING_MAX_BYTES, you get a structural summary
(keys, list lengths, first items) with "truncated": true, the original size, and a hint pointing at
garmin_raw_get(fields=, jq_path=) or the downsampling tools. Errors come back as
{"error": ..., "type": ..., "hint": ...} with actionable hints (expired tokens, rate limit, 404 for a feature your
device lacks, bad date format). The server never crashes on a tool call.
Redaction masks, recursively and case-insensitively, any key matching email, userName, firstName,
lastName, fullName, displayName, birthDate, address, phone (including prefixed variants such as
ownerFullName) with "[redacted]". The display name is still used internally for URL paths. Numeric ids
(profile, device, activity) are not redacted because tools need them as parameters.
Raw endpoint escape hatch
garmin_endpoint_catalog(search="metrics-service") lists what is known; garmin_raw_get calls it. The catalog
bundles two sources: paths verified on 2026-11-17 against a real account (shapes noted), and every
*-service/ path template the installed library touches, extracted by walking its AST
(scripts/gen_endpoints.py). Fifteen library methods returned 404/400 for the probing account (naps, lifetime
totals, acclimation, running economy, power curve, one-rep max, ECG, health snapshots, ...) and are flagged; they
may work for you if your device records that data.
Write safety
Methods are classified by name prefix: add_ create_ delete_ update_ set_ upload_ schedule_ unschedule_ push_ send_ import_ reschedule_ move_ confirm_ init_ request_ copy_ convert_ remove_ are WRITE, everything else is READ.
Write tools only exist when GARMIN_EVERYTHING_PROFILE=full and GARMIN_EVERYTHING_WRITES=1, are described
with a [WRITE: modifies your Garmin account] prefix, and carry readOnlyHint=false, destructiveHint=true.
login, logout, resume_login, request_reload, the raw connectapi/download helpers and the GraphQL
escape hatch are never auto-generated. Methods that return bytes (download_*) are wrapped by small overrides that
save the file locally and return its path.
Privacy
This repository contains no personal data: the bundled endpoint lists only hold path templates with {dn}
placeholders, tests use a fake Garmin class, and the smoke tests are run locally. Tokens live where garmin_mcp
puts them and are never copied. garmin_export writes to your machine only, with redaction applied, and the
.gitignore refuses token files and exports by default.
Updating when python-garminconnect releases
uv lock --upgrade-package garminconnect
uv run python scripts/gen_endpoints.py # refresh the endpoint catalog from the new source
uv run python scripts/gen_coverage.py # refresh docs/COVERAGE.md and the badge line
uv run pytest # the committed coverage file is checked against the live registryNew methods appear as tools automatically. If one needs special handling (odd signature, bytes return), add it to
OVERRIDES or SKIP in src/garmin_everything_mcp/registry.py.
Development
git clone https://github.com/dlekdns08/garmin-everything-mcp && cd garmin-everything-mcp
uv sync
uv run pytest # 45 tests, no network
uv run garmin-everything-mcp --profile all # stdio
npx @modelcontextprotocol/inspector uv run garmin-everything-mcpLayout: registry.py (introspection, classification, profiles, overrides), results.py (JSON, redaction,
size budget, error hints), pathsel.py (jq-like resolver), client.py (lazy token login with a lock),
tools_extra.py (the eight hand-written tools), server.py (FastMCP wiring and CLI),
data/ (garmin_mcp method and tool name lists, verified and generated endpoint catalogs).
How the garmin_mcp list was derived
data/garmin_mcp_wrapped_methods.txt is the set of garmin_client.<method>( calls grepped from garmin_mcp's
src/garmin_mcp/*.py (105 names, 99 of which are Garmin methods in 0.3.20; the rest are HTTP helpers such as
post/put). data/garmin_mcp_tool_names.txt is every @app.tool-decorated function name in the same tree
(153 names), because a few garmin_mcp tools shadow library method names without calling them
(get_heart_rate_zones, get_courses, get_calendar_events, the get_nutrition_daily_* trio, ...). The
extras profile excludes the union of both lists.
Credits
Taxuspt/garmin_mcp for the server this one is designed to sit next to, and for the token conventions it established.
cyberjunky/python-garminconnect for the library that does all the real work. Every tool here is one of its methods.
MIT licensed. Not affiliated with Garmin.
Tool Schema Changelog
Recent tool additions, removals, and schema changes observed during successful MCP inspections.
Loading tool schema changelog…
This server cannot be deployed
Maintenance
Related MCP Connectors
Garmin watch data for AI assistants: activities, sleep, HRV, recovery. Never writes to Garmin.
Garmin data in Claude: 135 tools — activities, sleep, HRV, training, workouts. Free, open source.
Unofficial Garmin Connect access: sleep, HRV, training, activities, workouts and weight.
Explore Garmin activity and health data with your AI assistant.
Related MCP Servers
- AlicenseNot gradedqualityCmaintenancePersonal MCP server for interacting with your Garmin Connect data. Exposes 62 tools across 11 domains including activities, health, training, and workouts.1MIT
- FlicenseNot gradedqualityDmaintenanceExposes Garmin Connect health data (steps, sleep, HR, HRV, stress, activities, etc.) as tools for MCP-compatible clients like Claude.-
- AlicenseNot gradedqualityCmaintenanceExposes your own Garmin Connect activity, health, and training data as read-only MCP tools, covering activities, workouts, sleep, heart rate, HRV, stress, body battery, weight, and women's health. Most tools use Garmin's official Personal API key, with a clearly labeled unofficial fallback for data the official API doesn't yet cover, such as training readiness and VO2 max.MIT
- AlicenseBqualityBmaintenanceA read-only MCP server that lets AI agents query a user's own Garmin Connect data via Garmin's official Personal API. It exposes activities, daily wellness metrics, sleep and recovery, and body/profile data as tools for natural-language analysis.21Apache 2.0