Comparison

Hosted Garmin MCP vs self-hosting

If you can run a Python script, you can run a Garmin MCP server yourself for free. Here's an honest look at what that involves, when it's the right call, and what you get for paying us instead.

Updated 2026-10-04

The open-source options

ProjectLanguageNotes
Taxuspt/garmin_mcpPythonBuilt on python-garminconnect. Read-only. The most-starred starting point.
Jack-Abyss/claude-garminPythonClaude Desktop focused; recovery checks and session analysis prompts.
tamcore/garmin-mcpGoStdio and remote Streamable HTTP modes, OAuth 2.1 for multi-user. The most "production" shaped.
zjromani/garmin-mcpTypeScriptReads activities and creates workouts and training plans. Closest to what we do.
Garmin Community MCP coreTypeScript (Cloudflare Workers)The server behind this site. We plan to publish the core under a permissive licence; the hosted layer (accounts, MFA, billing) stays ours.

What self-hosting actually involves

  1. Install Python or Node and the project.
  2. Authenticate. Run a login script with your Garmin email and password. If you have MFA on, paste the code. This produces a long-lived OAuth1 token on disk.
  3. Register the server in Claude Desktop's config (stdio). Works immediately on that computer.
  4. For ChatGPT or your phone, you need a remote server: host it somewhere with HTTPS (a VPS, Cloudflare Worker, Railway…), add authentication so it's not open to the internet, and keep it running.
  5. Maintain. About once a year the Garmin token expires and you re-run login. When Garmin changes an endpoint, you wait for a fix or write one.

For a developer who only uses Claude Desktop on one machine, that's an evening and then almost nothing. For everyone else, step 4 is where it stops being fun.

Side by side

Self-hostedGarmin Community MCP
Cost$0 (plus hosting if remote)$4.99–$19.99/mo; 48-hour trial
Time to first answer30–90 minutesAbout 5 minutes
Claude DesktopYesYes
Claude web / mobileOnly if hosted remotely with HTTPSYes
ChatGPTOnly if hosted remotely with HTTPS + authYes
Garmin MFAHandled in a terminalHandled in the browser
Token expiryYou notice when it breaksWe check nightly and email you
Garmin API changesWait or patchPatched for everyone; status page
Data coverage10–40 tools depending on project50+ endpoints + raw API
WritesSome projects (workouts)Workouts, scheduling, weight, hydration, BP, activity edits, gear
Who holds the tokenYou, on diskUs, AES-GCM encrypted, revocable
SupportGitHub issuesEmail, 24 h (4 h on Coach)

Security trade-off, honestly

Self-hosting means your Garmin token never leaves your machine. That's a real advantage. Using a hosted service means trusting us with an encrypted token. We've tried to make that trust cheap: no passwords stored, tokens encrypted at rest with a key that lives only in our runtime, one-click revoke, deletes off by default, and no health data kept at rest beyond a short-lived access-token cache. Details on the security page. If that's not enough for you, self-host; we'll still link to the projects.

Our recommendation

FAQ

Can I self-host a Garmin MCP server for free?

Yes. Several open-source servers exist on GitHub, including Taxuspt/garmin_mcp, Jack-Abyss/claude-garmin, tamcore/garmin-mcp and zjromani/garmin-mcp. They run locally with your Garmin credentials and work with Claude Desktop; ChatGPT and mobile need you to expose them over HTTPS.

Why pay for a hosted Garmin MCP server?

It works from your phone and ChatGPT without running anything, handles MFA and token expiry, gets patched when Garmin changes its API, and comes with support. Garmin Community MCP starts at $4.99/month.

Will you open-source your server?

That's the plan: the core server under a permissive licence, the hosted account and billing layer private. Follow the GitHub org.

Skip the VPS

48-hour free trial. If you'd rather self-host afterwards, the links above will still be here.

Start free trial