Garminmcp
Wire Claude or Cursor agents to your Garmin Connect sleep, activity, and recovery data without building a custom scraper.
Overview
io.github.davidmosiah/garminmcp is a Build-phase MCP server that connects AI agents to unofficial Garmin Connect health, sleep, activity, and recovery data over stdio.
What is this MCP server?
- Unofficial Garmin Connect MCP over stdio for health, sleep, activity, and recovery tool calls
- Privacy-first payload modes: summary, structured, or raw supported Connect payloads
- Self-contained Node login via garmin-mcp-server auth with tokens defaulting to ~/.garmin-mcp/garmin_tokens.json
- Optional SQLite cache (GARMIN_CACHE) with configurable path for fewer repeat API hits
- Five documented environment variables including GARMIN_DOMAIN and GARMIN_PRIVACY_MODE
- Published server version 0.5.1 on the MCP registry schema 2025-12-11
- npm identifier garmin-mcp-unofficial with stdio transport
- 5 documented environment variables: GARMIN_TOKEN_PATH, GARMIN_PRIVACY_MODE, GARMIN_CACHE, GARMIN_CACHE_PATH, GARMIN_DOMA
Community signal: 3 GitHub stars.
What problem does it solve?
Building agents that reason about your real Garmin metrics usually means fragile scripts, unclear auth, and oversharing full API dumps into the model context.
Who is it for?
Indie builders shipping personal health, coaching, or recovery agents who already wear Garmin devices and want MCP-native access during integration work.
Skip if: Teams needing official Garmin partnership APIs, clinical compliance out of the box, or unmanaged raw sensor telemetry beyond supported Connect payloads.
What do I get? / Deliverables
After install and garmin-mcp-server auth, your agent can call MCP tools with privacy-tuned Garmin payloads and optional SQLite caching.
- Registered stdio MCP server exposing Garmin health, sleep, activity, and recovery tools to your agent
- Local Garmin Connect token file plus optional SQLite cache for repeat queries
- Agent-callable responses scoped by GARMIN_PRIVACY_MODE (summary, structured, or raw supported payloads)
Recommended MCP Servers
Journey fit
Solo builders add this MCP while assembling agent stacks and product backends, before they ship health or coaching features. It is an external-service bridge (Garmin Connect over stdio MCP), which belongs on the integrations shelf rather than generic agent-tooling docs.
How it compares
Garmin Connect MCP integration for agents, not a packaged fitness coaching skill or a hosted analytics SaaS.
Common Questions / FAQ
Who is garminmcp for?
Solo and indie developers who use Claude Code, Cursor, or other MCP clients and want Garmin sleep, activity, and recovery data inside agent workflows while building health or coaching products.
When should I use garminmcp?
Use it during the build phase when you are wiring agent-tooling or backend integrations and need queryable Garmin Connect context without maintaining a separate Python auth stack.
How do I add garminmcp to my agent?
Install the npm package garmin-mcp-unofficial, run garmin-mcp-server auth to create local tokens, set optional env vars like GARMIN_PRIVACY_MODE, then register the stdio MCP server in Claude Code or Cursor using the published server identifier.