garmin

MCP serverAI & models

Once added, your AI can work with your Garmin health and fitness data, answering questions about your activities, sleep, heart rate variability (HRV), training, and workouts. It is community-built, includes 135 tools covering these areas, and is free and open source.

Use garmin in Claude, ChatGPT or Ahel Desktop

Free. Sign in, add garmin and connect your AI. About a minute.

Also: Claude Code · Cursor · Codex

Then ask your AI: use garmin

Details

Available today. Use it from your connected AI after setup.

After adding it, ask your AI about your recent activities or how you have been sleeping to see your Garmin data in action. It is free and open source, so you can also browse the code on GitHub.

What your AI can do with it

  • Pull up your recent activities
  • Summarize your sleep data
  • Explain your heart rate variability (HRV) readings
  • Review training and workout details
  • Answer questions about your fitness history

Install garmin

The server’s own address, for the clients that take one directly. Or connect Ahel once and every client you use reads it from one address, with the account kept on Ahel rather than in each client’s config.

  • Claude Code

    claude mcp add --transport http --scope user garmin 'https://missingmcp.com/garmin/mcp'

    Run it once in your project, then open /mcp to approve any sign-in the server asks for.

  • Claude Desktop

    https://missingmcp.com/garmin/mcp

    Add a custom connector in Settings, paste this address, and approve the sign-in.

  • Cursor

    cursor://anysphere.cursor-deeplink/mcp/install?name=garmin&config=eyJ1cmwiOiJodHRwczovL21pc3NpbmdtY3AuY29tL2dhcm1pbi9tY3AifQ==

    Open the link and Cursor adds the server at that address.

  • ChatGPT

    https://missingmcp.com/garmin/mcp

    In Settings, enable Developer mode, create an MCP app, and paste this address. Your plan and workspace must allow custom apps.

  • Codex

    codex mcp add garmin --url 'https://missingmcp.com/garmin/mcp'

    Run it once, then sign in with codex mcp login garmin if the server asks for an account.

From the project's README

As published by velkyvenik/missingmcp in README.md. This repository publishes several servers, so only the opening is shown here.

The MCP servers exist. Connecting them shouldn't be complicated.

A multi-user, OAuth 2.1–protected gateway that hosts the connectors Claude is missing, so a small trusted circle can connect their own accounts from any Claude client (iOS, Android, Web, Desktop). The flagship connector is Garmin Connect: the gateway wraps the unmodified garmin_mcp worker and adds OAuth, per-user token isolation, and a reverse proxy. WHOOP is served the same way but in-process, on WHOOP's own official OAuth v2 API. The core is adapter-based and supports three forward strategies — worker (garmin), local (whoop, in-process, no subprocess), and remote (MCP + header injection, for services with a hosted MCP that lacks its own OAuth) — see Connectors. The reference deployment runs at missingmcp.com.

Claude → POST /garmin/mcp (Bearer) → Gateway → 127.0.0.1:<port>/mcp (per-user garmin_mcp) → connect.garmin.com

Why

Shortened here. Read the whole README on GitHub.

Signals

GitHub stars
10
Forks
13
Last commit
Sep 2026
Advanced
Delivery
garmin MCP server → your Ahel connector (mcp.ahel.ai) → your AI.
Item type
mcp-server
Key
com-missingmcp-garmin
Source
github.com/velkyvenik/missingmcp
Hosted endpoint
https://missingmcp.com/garmin/mcp