mcp-garmin

An MCP server that exposes Garmin Connect over Streamable HTTP, authenticated with GitHub OAuth.

It is built for remote use — as a custom connector in claude.ai / Claude Desktop, or over claude mcp add --transport http — rather than as a local stdio server. Two consequences follow from that:

• Clients authenticate with OAuth, handled by FastMCP's GitHubProvider. The server publishes /.well-known/oauth-authorization-server and supports Dynamic Client Registration, which is what claude.ai requires.

• Garmin credentials never reach the client. The interactive sign-in runs once; the resulting OAuth tokens live on a mounted volume and refresh themselves.

Data access is provided by garminconnect.

Why a GitHub OAuth app?

It is reasonable to ask what GitHub has to do with reading your own Garmin data. Nothing — GitHub is only the login screen. The chain that puts it there:

1. claude.ai will not accept a static token. Its connector dialog can send fixed request headers, but that feature is in limited beta. Without it the only way to add a remote MCP server is OAuth.

2. OAuth needs something that authenticates a human. The server must run an authorization flow, which means a browser sign-in that proves who you are.

3. The server has no user database, and should not have one. FastMCP's OAuthProxy translates between the MCP client and an existing identity provider; it does not store users or passwords itself.

So an identity provider is required, and GitHub is a convenient one. The app requests the user scope only — it reads your profile, not your repositories — and the single field taken from it is your login, which is compared against ALLOWED_GITHUB_LOGINS.

Nothing depends on GitHub specifically. FastMCP ships providers for Google, Azure, Auth0, Keycloak, Discord, WorkOS and others; swapping is a one-line import change in server.py plus the matching credentials. What will not work is FastMCP's InMemoryOAuthProvider — it simulates the flow for tests and authenticates nobody, so on a public URL it would admit anyone.

Related MCP server: health-mcp

Access control

Holding a valid GitHub identity is not enough. ALLOWED_GITHUB_LOGINS lists the accounts permitted to use the server, and every message is checked against it. If the list is empty the server refuses to start — an unset allowlist fails closed rather than exposing health data to any GitHub user.

Tools

Diagnostics — garmin_status

Activities — garmin_get_activities, garmin_get_activities_by_date, garmin_get_last_activity, garmin_get_activity, garmin_get_activity_splits, garmin_get_activity_weather, garmin_get_activity_hr_zones

Analysis — garmin_compare_activities, garmin_get_progress_summary

Health — garmin_get_daily_summary, garmin_get_body_battery, garmin_get_hrv, garmin_get_sleep, garmin_get_heart_rates, garmin_get_resting_heart_rate, garmin_get_stress, garmin_get_steps, garmin_get_spo2, garmin_get_respiration

Training — garmin_get_training_readiness, garmin_get_training_status, garmin_get_max_metrics, garmin_get_hill_score, garmin_get_endurance_score, garmin_get_race_predictions, garmin_get_training_summary

Profile, goals, gear — garmin_get_user_profile, garmin_get_personal_records, garmin_get_goals, garmin_get_earned_badges, garmin_get_badge_challenges, garmin_get_devices, garmin_get_gear, garmin_get_gear_stats

Weight — garmin_get_weigh_ins, garmin_get_body_composition

Workouts — garmin_get_workouts, garmin_get_workout, garmin_get_scheduled_workouts

Writes — garmin_upload_workout, garmin_schedule_workout, garmin_create_manual_activity, garmin_add_weigh_in, garmin_delete_activity

Every write tool takes confirm and does nothing until it is true. These change a real training record that feeds load and fitness metrics, so an agent should show its intent and get agreement first rather than write speculatively.

Setup

1. GitHub OAuth app

Create one at Settings → Developer settings → OAuth Apps with the callback URL <BASE_URL>/auth/callback. Copy the client id and secret.

2. Build and sign in to Garmin (once)

cp .env.example .env   # then fill it in
docker build -t mcp-garmin .

# Interactive: asks for password and any MFA code.
docker run -it --rm -v /srv/garmin-data:/data mcp-garmin garmin-mcp-auth

Tokens land in /data/garminconnect with mode 0600 and are refreshed automatically from then on.

3. Run

docker run -d --name mcp-garmin --env-file .env \
  -v /srv/garmin-data:/data -p 8000:8000 mcp-garmin

4. Add the connector

• Claude Code — claude mcp add --transport http garmin <BASE_URL>/mcp

• claude.ai / Claude Desktop — Settings → Connectors → Add custom connector → <BASE_URL>/mcp

Both then send you through GitHub to sign in.

Configuration

Notes

Garmin Connect has no public API; garminconnect talks to the endpoints the mobile and web apps use, and Garmin changes them without notice. The dependency is pinned exactly for that reason — upgrade deliberately and re-check the tools afterwards.

Calls are synchronous, so each one runs in a worker thread; a slow Garmin response cannot stall the MCP event loop. Sessions that Garmin expires server-side are re-established once and the call retried.

Licence

MIT