Garmin Connect MCP server

garmin-connect-api

Read and write Garmin Connect from an MCP client such as Claude, from Python, or over a local HTTP API: activities with per-set strength detail, daily health data, planned workouts, completed strength sessions, and weigh-ins with full body composition.

<!-- mcp-name: io.github.happyc0der/garmin-connect-api -->

Unofficial. Not affiliated with or endorsed by Garmin. It uses the same private endpoints as

the Garmin Connect website, through python-garminconnect,

because Garmin offers no public API for individuals. Those endpoints can change without notice,

and using them is not sanctioned by Garmin's terms. It is meant for your own account and your

own data.

Status

v0.3. Reads activities with per-set strength detail, laps and pool-swim lengths, daily health, trends over up to two years and named personal records; writes strength, run, ride and swim workouts, completed strength sessions, set corrections and weigh-ins with body composition. 38 tools, every one checked against a real account. Bug reports and feature requests go to GitHub Issues.

Quick start

You need uv and Python 3.12 or newer.

1. Log in once, at a terminal:

uvx --from garmin-connect-api garmin login

This is the only place a password is ever typed. It asks for your Garmin email, password and any multi-factor code, then stores tokens in ~/.garmin-api/default, readable by your user only. Nothing else ever prompts for a password; without tokens, every tool says to run this.

2. Add the server to your MCP client.

Claude Code:

claude mcp add --scope user --transport stdio garmin -- uvx garmin-connect-api@latest

Claude Desktop, in claudedesktopconfig.json (in ~/Library/Application Support/Claude/ on macOS, %APPDATA%\Claude\ on Windows):

{
  "mcpServers": {
    "garmin": {
      "command": "uvx",
      "args": ["garmin-connect-api@latest"]
    }
  }
}

@latest makes uvx check for a new release each time the server starts. Without it, uvx keeps running the first version it downloaded.

3. Ask. "How did I sleep this week?", "Did my pace hold up in yesterday's swim?", "How has my resting heart rate moved since summer?", "Show my last strength session's sets, and change sets 3 to 5 to dumbbell rows", "Schedule a swim for Thursday: 200 easy, then 8 x 100 free on 20 seconds rest, in a 25-yard pool".

What it can do

38 tools, each annotated so your client knows which only read (24), which add something (8) and which delete or overwrite (6), and can ask before running those. Every argument, down to a workout step's pace target, carries a description.

Four tools are written for a model rather than mirrored from an endpoint: garminstatus checks the login without calling Garmin, findexercise finds Garmin's name for a lift, and recentstrengthsessions and week_summary answer common questions in one call.

Shortened. The full README is on GitHub.