Skip to main content
Glama

Garmin β†’ Claude Β· Self-Hosted MCP Server + Live Dashboard

Put your Garmin Connect data inside Claude β€” and run your own private health & triathlon dashboard β€” on a small server that's entirely yours.

  • πŸ—£οΈ Ask your body data in plain English in Claude (web, desktop, mobile): "How did I sleep?", "Show my last 5 runs", "Am I recovered for a hard session?"

  • πŸ“Š A live dashboard at /dashboard β€” body battery, sleep, heart rate, stress, VOβ‚‚ max, training load, HR zones, weight/hydration, and a Swim / Bike / Run view that fills in as you train.

  • πŸ”’ Private by design β€” runs on your Railway account, locked with your bearer token. Your Garmin password never leaves your own computer.

Built for the community by Sudhakar Reddy Gade Β· πŸ“– Full step-by-step guide (no coding needed): https://www.nirvedha.com/garmin-dashboard/


Quick start

The easy way β€” let Claude Code do it

Install Claude Code, open it in an empty folder, and paste the ready-made prompt from the guide. It clones this repo, mints your Garmin token, deploys to Railway, and hands you your connector + dashboard URLs. You only approve the Railway login and type your Garmin password into your own terminal.

The hands-on way

Fork this repo and follow the guide (8 clicks-and-copy steps, ~20 minutes) or the concise SETUP.md. In short: fork β†’ deploy on Railway β†’ add a volume at /root/.garminconnect β†’ set four variables β†’ generate a domain β†’ add to Claude.


Related MCP server: Garmin MCP Server

What you get

MCP tools

90+ Garmin tools (activities, sleep, HRV, body battery, training, gear, …) usable from Claude

Transport

Streamable HTTP at /mcp, health check at /healthz

Auth

Bearer token on every request (header or ?token= in the URL, for clients like Claude that can't set headers)

Dashboard

Server-rendered, live-on-refresh single page at /dashboard

Persistence

Garmin OAuth tokens on a mounted volume, auto-refreshing

Cost

~$5/month on Railway's Hobby plan

Environment variables

Variable

Required

Purpose

MCP_ACCESS_TOKEN

Yes

Bearer token guarding /mcp and /dashboard (β‰₯16 chars, or the server won't start)

GARMIN_TOKEN_BASE64

Recommended

Pre-minted Garmin OAuth blob β€” avoids logging in from a cloud IP (Garmin blocks those)

GARMIN_MCP_TRANSPORT

Yes

streamable-http

GARMIN_MCP_HOST

Yes

0.0.0.0

GARMIN_EMAIL / GARMIN_PASSWORD

Fallback

Full login if no token blob; may trigger MFA

PORT

Auto

Injected by Railway; the server binds it

DASHBOARD_TZ_OFFSET_HOURS

Optional

Local-day offset for the dashboard (default 5.5 = IST)

See SETUP.md for the full list, token rotation, and re-auth.

Security model

  • Fail-closed: the server refuses to start without a strong MCP_ACCESS_TOKEN, so the endpoint is never exposed unprotected β€” not even briefly.

  • The bearer check runs before the MCP app, so unauthorized callers get 401 and never reach your data.

  • Your Garmin password is only ever used locally to mint a token blob; the deployed server uses the blob (read-scoped OAuth tokens), never the password.

  • .gitignore keeps .env, tokens, and caches out of git.

Architecture

Claude (web / desktop / mobile)  ──HTTPS + bearer token──►  Railway service
                                                                 β”‚
                    BearerAuthMiddleware ──► /healthz (open) Β· /mcp Β· /dashboard
                                                                 β”‚
                                             FastMCP (90+ tools) + dashboard API
                                                                 β”‚
                                             garminconnect + garth ──► Garmin API
                                             (OAuth tokens on a persistent volume)

Local development

uv sync
# stdio (for Claude Desktop config):
GARMIN_MCP_TRANSPORT=stdio uv run garmin-mcp
# streamable HTTP + dashboard:
MCP_ACCESS_TOKEN=$(python3 -c "import secrets;print(secrets.token_urlsafe(32))") \
GARMIN_MCP_TRANSPORT=streamable-http uv run garmin-mcp-http
# mint a Garmin token blob (interactive):
uv run garmin-mcp-mint

Credits

Stands on the shoulders of the open-source garmin_mcp by Taxuspt and the Docker + streamable-HTTP fork by k8sautom8. This repo adds a bearer-token security layer, $PORT/proxy fixes, and the live triathlon dashboard.

License

MIT β€” free to use, change, and share. See LICENSE.


Shared as a community resource by Nirvedha Executive Coaching Solutions, Hyderabad Β· https://nirvedha.com

A
license - permissive license
-
quality - not tested
C
maintenance

Maintenance

–Maintainers
–Response time
–Release cycle
–Releases (12mo)
Commit activity

Resources

Unclaimed servers have limited discoverability.

Looking for Admin?

If you are the server author, to access and configure the admin panel.

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/sumal009/garmin-mcp'

If you have feedback or need assistance with the MCP directory API, please join our Discord server