Quick start
-
Install uv, which fetches Python and everything else by itself:
winget install astral-sh.uvon Windows,brew install uvon macOS. -
Run the setup in a new terminal. It opens Garmin's key page, reads the key from your clipboard,
checks it, stores it in your system keychain and configures your MCP clients.
uvx garmin-dynamic-mcp setup - Restart your client and ask: "How many km did I run last week?"
Why this one
It follows Garmin's API
A daily check reads Garmin's published specification. When something changes, a pull request regenerates the endpoint catalog, a human reviews it, and a release ships. You are told in the conversation when to update.
Your key stays safe
The key lives in the OS keychain, never in a JSON file. Only GET requests, only to Garmin, only to reviewed endpoints. Nutrition and cycle data are off by default.
One command
setup opens the key page, verifies the key and configures every client it finds, backing up files and never overwriting what it cannot parse.
What you can ask
Claude composes the requests and does the maths and the charts, so you are not limited to preset questions.
- How many km did I run last week?
- What is my average cadence over my last ten runs?
- Chart the km I ran each day last month.
- How did my sleep and HRV change over the last 90 days?
Works with
| Client | Configured by setup |
|---|---|
| Claude Desktop | Yes |
| Claude Code | Yes |
| Cursor | Yes |
| VS Code | Yes |
| Windsurf / Devin Desktop | Yes, when its config file exists |
| Gemini CLI, Codex CLI | Yes |
| Anything else | Prints the snippet to paste |
Security and privacy
- Runs on your computer with your own key. The key is sent only to Garmin.
- Read-only. No free-form URLs: every request goes to a path in the reviewed catalog.
- Client configurations pin an exact version. The server tells you when a newer one exists; you decide.
- Releases are built by CI and published to PyPI with trusted publishing and attestations.