io.github.davidmosiah/garminmcp
garmin-mcp-server
Privacy-first unofficial Garmin Connect MCP for AI health, sleep, activity & recovery agents.
alive probed 2026-10-19
41tools
≈ 6.0ktokens, estimate
≈ 3.0 %of Claude's 200k window
4.2×the median server
484 msto initialize
22 msto list tools
- Run it
- npx -y garmin-mcp-unofficial@0.5.3 (stdio, probed in a container with the network off)
- Host
- npmjs.com
- Reports itself as
- garmin-mcp-server 0.5.3
- Capabilities
- prompts, resources, tools
- Instructions
- none
- Of a 1M window
- ≈ 0.6 % of a 1M context window, estimate
- Claude count
- The count_tokens endpoint refused the tool schemas: invalid x-api-key. The estimate stands in.
- Repository
- https://github.com/davidmosiah/garmin-mcp
- Website
- https://wellness.delx.ai/connectors/garmin
- Registry
- active, updated 2026-07-03 · registry entry
- Reachable
- 1 of the last 1 probe
Most expensive tools
Estimates with the o200k_base tokenizer.
| Tool | o200k estimate | Share of this server |
|---|---|---|
| garmin_list_activities | 690 | 11 % |
| garmin_profile_update | 261 | 4 % |
| garmin_wellness_context | 212 | 4 % |
| garmin_onboarding | 202 | 3 % |
| garmin_weekly_summary | 184 | 3 % |
Badge for the README
The result of the latest probe, the tool count and the token cost. The feed has an entry for every probe that changed them.
A mail when this server changes
Stops answering, comes back, tool set or cost changes. One confirmation mail first, a stop link in every mail.
For the publisher
- The Anthropic count_tokens endpoint refused the tool schemas (invalid x-api-key). A client that validates schemas can refuse them too.