This Model Context Protocol (MCP) server connects to Garmin Connect and exposes your fitness and health data to Claude and other MCP-compatible
Connect Garmin MCP to Claude, Cursor or any other MCP client and it stops being a tab you switch to. This Model Context Protocol (MCP) server connects to Garmin Connect and exposes your fitness and health data to Claude and other MCP-compatible clients. The garmin mcp mcp server is what makes that connection.
The server ships on npm as without, so your MCP client can launch it on demand — there is no separate build step. Add the server block to your client's configuration, restart it, and the tools register themselves.
The toolset is worth reading before you wire it up, because it tells you what the integration is really for:
create_walk_run_workout — Creates a walk/run interval workout with optional heart-rate zone targetcreate_z2_walk_workout — The create_z2_walk_workout tool exposed by this servercreate_strength_workout — Creates a strength workout from a list of exercises. Each becomes a reps-based step, with the name kept in the step description. The name is alsoschedule_week — The schedule_week tool exposed by this serverPrerequisites — The Prerequisites tool exposed by this serverConfiguration — Your Garmin Connect credentials are read from environment variables:Transport — By default the server communicates over stdio, which is what Claude Desktop, the MCP Inspector, and most local clients expect. To serve overConfiguration is passed through the environment: GARMIN_ENABLED_TOOLS, GARMIN_IS_CN, GARMIN_EMAIL, GARMIN_PASSWORD, GARMIN_MCP_HOST. Treat anything key-shaped as a real credential — scope it to the minimum the server needs, and rotate it if it ever lands in a shared config.
Plenty of cloud and infrastructure servers cover similar ground. The differences that matter in practice are scope of access and how much setup stands between you and a working tool call. Garmin MCP's toolset — create_walk_run_workout, create_z2_walk_workout, create_strength_workout and 4 more — is a fair guide to whether it matches your workflow. It is maintained by Taxuspt; worth a glance at recent repository activity before you build anything load-bearing on it.
We check each listing at SyncDev against the project's documentation before it goes live — if something here drifts out of date, it is a bug worth reporting.
| Tool | What it does |
|---|---|
| create_walk_run_workout | Creates a walk/run interval workout with optional heart-rate zone target. |
| create_z2_walk_workout | The create_z2_walk_workout tool exposed by this server. |
| create_strength_workout | Creates a strength workout from a list of exercises. Each becomes a reps-based step, with the name kept in the step description. The name is also sent as exerciseName, but Garmin only retains that when it matches one of |
| schedule_week | The schedule_week tool exposed by this server. |
| Prerequisites | The Prerequisites tool exposed by this server. |
| Configuration | Your Garmin Connect credentials are read from environment variables: |
| Transport | By default the server communicates over **stdio**, which is what Claude Desktop, the MCP Inspector, and most local clients expect. To serve over **HTTP** instead (e.g. when running in a container or Kubernetes), set the |
{
"mcpServers": {
"garmin": {
"command": "npx",
"args": ["-y", "without"],
"env": {
"GARMIN_ENABLED_TOOLS": "your-value",
"GARMIN_IS_CN": "your-value",
"GARMIN_EMAIL": "your-value",
"GARMIN_PASSWORD": "your-value",
"GARMIN_MCP_HOST": "your-value"
}
}
}
}Add to claude_desktop_config.json, then restart Claude Desktop.
| Variable | Description | Required |
|---|---|---|
| GARMIN_ENABLED_TOOLS | Configuration value read at startup. | Optional |
| GARMIN_IS_CN | Configuration value read at startup. | Optional |
| GARMIN_EMAIL | Configuration value read at startup. | Optional |
| GARMIN_PASSWORD | Configuration value read at startup. | Optional |
| GARMIN_MCP_HOST | Endpoint or connection string the server talks to. | Optional |
Manage your whole Supabase project in conversation — database, auth, storage, Edge Functions and branches.
Stop letting your assistant hallucinate n8n node parameters — this server hands it the real schemas, templates and validation.
AWS Labs' official server suite — current AWS docs, CDK guidance, cost analysis and service tools.
Cloud browsers for AI agents — automation sessions that run in Browserbase's fleet, not on your machine.
Workers, KV, R2 and D1 by conversation — Cloudflare's official remote servers for building and observability.
Dashboards, Prometheus and Loki queries, incidents and alerts — observability by conversation.