Garmin MCP Lite

[For AI Assistants & LLMs] You are interfacing with a Garmin MCP (Model Context Protocol) server.

1. Data Freshness: Always query the data if the user asks about their recent workouts or health metrics.
2. Parameter Tuning: Use the fields parameter in tools like garmin_activity_detail to limit the response payload and save context window (e.g., ["splits", "hrZones"]).
3. Read-Only: This server provides read-only access to Garmin Connect. You cannot modify user data.
4. No Password Request: Never ask the user for their Garmin password. Authentication is handled out-of-band via a local token.
5. Health Tip: garmin_health now supports a metric parameter — use "steps", "sleep", "hrv", "spo2", "body_battery", etc., to query specific data and save context window.
6. Zone Context: garmin_activity_detail returns seconds per heart rate zone but no boundaries. Call garmin_zones first to get the bpm ranges before judging intensity.

Read this in other languages: English, 简体中文.

A lightweight Garmin Model Context Protocol (MCP) server, designed specifically for endurance athletes.

It exposes 15 precisely-curated endpoints for deep analysis of running, cycling, swimming, and health data — replacing bulky 80+ endpoint alternatives with a clean, focused toolset.

Core Tools (15)

🏃 Activity & Training

💚 Health & Wellness

🎯 Goals & Challenges

⌚ Device & Gear

Quickstart

There are two ways to run the server. Installing it as a command is the safer default — it starts in well under a second, needs no network at launch, and GUI clients can find it. uvx works too, but it downloads on first run and is invisible to clients that do not inherit your shell PATH.

1. Install

uv tool install garmin-mcp-lite
which garmin-mcp-lite     # → ~/.local/bin/garmin-mcp-lite

uvx garmin-mcp-lite

2. Authenticate (First Time Only)

Why not just put the password in the AI config? Garmin has strict security measures. Logging in from a new location/MCP server often triggers Cloudflare CAPTCHAs or MFA email codes. If the password sits in a client's background config, the AI assistant silently freezes when challenged, with no way for you to type the code in.

So this project uses a two-step strategy: run the login script in your terminal first. If Garmin challenges you, you can type the MFA code interactively. On success the session token is cached locally and stays valid for roughly a year.

GARMIN_EMAIL="your@email.com" GARMIN_PASSWORD="your_password" garmin-mcp-lite-login

(💡 China Region Users: if your account is registered with Garmin China (garmin.cn), prefix the command with GARMIN_IS_CN=true.)

The token is written to ~/.garmin-mcp-lite/garmin_tokens.json. Set GARMIN_TOKEN_DIR to keep several clients or accounts on separate sessions.

3. Configure Your AI Assistant

Claude Desktop

Add this to ~/Library/Application Support/Claude/claude_desktop_config.json:

{
  "mcpServers": {
    "garmin-lite": {
      "command": "/Users/you/.local/bin/garmin-mcp-lite",
      "args": []
    }
  }
}

Prefer uvx? Use "command": "uvx" with "args": ["garmin-mcp-lite"].

Cursor / Windsurf / Gemini CLI

Use the same command and args as above.

Chatbox / opencode / Other GUI Clients

GUI clients such as Chatbox are launched from Finder and do not inherit your shell PATH, so a bare uvx fails with spawn uvx ENOENT. Point them at the absolute path from step 1.

Chatbox (Settings → MCP → Add custom):

{
  "mcpServers": {
    "garmin": {
      "command": "/Users/you/.local/bin/garmin-mcp-lite",
      "args": []
    }
  }
}

opencode (opencode.json) uses a different schema — the key is mcp, type is required, and command is an array:

{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "garmin": {
      "type": "local",
      "command": ["/Users/you/.local/bin/garmin-mcp-lite"],
      "enabled": true,
      "timeout": 30000
    }
  }
}

opencode's timeout defaults to 5000 ms. Raise it if you insist on uvx instead of an installed command.

Environment Variables

Troubleshooting

Verify the server independently of any client:

printf '%s\n' \
 '{"jsonrpc":"2.0","id":1,"method":"initialize","params":{"protocolVersion":"2024-11-05","capabilities":{},"clientInfo":{"name":"t","version":"1"}}}' \
 '{"jsonrpc":"2.0","method":"notifications/initialized"}' \
 '{"jsonrpc":"2.0","id":2,"method":"tools/list"}' | garmin-mcp-lite

Expect a serverInfo line reporting this package's version, followed by all 15 tools.

Example Queries

Once connected, you can ask your AI assistant natural-language questions like:

Training

• "What's my training load focus this week?"
• "Show me my race goal for June and what my current predicted finish time is."
• "Compare my marathon PB against the current prediction."

Health

• "How many steps have I taken today? Am I on track for my daily goal?"
• "Analyze my sleep quality from last night."
• "What are my heart rate zones for running, and where does my lactate threshold sit?"

Gear & Goals

• "How's my Grossglockner virtual climb challenge going?"
• "Is my Descent G1 firmware up to date?"

Manual Installation (for Developers)

If you want to modify the code:

git clone https://github.com/Golden0Voyager/garmin-mcp-lite.git
cd garmin-mcp-lite
uv sync

# Login
GARMIN_EMAIL="your@email.com" GARMIN_PASSWORD="your_password" python -m garmin_mcp_lite.login

# Run server
python -m garmin_mcp_lite.server

Run the same gates CI runs before opening a PR:

uv run ruff check garmin_mcp_lite/ tests/ scripts/
uv run mypy garmin_mcp_lite/
uv run pytest --cov tests/
python3 scripts/smoke_wheel_install.py

The suite is at 100% statement coverage across every module, including the 15-tool registry in server.py. tests/test_server.py pins the exact tool names, so a rename or a dropped add_tool() call fails a test instead of silently disappearing from a client's tools/list.

There is also a live end-to-end script that walks all 15 tools against your own account (needs a login token):

python test_e2e.py

Comparison with Other Garmin MCPs

Changelog

0.1.6

• Fix: garmin_events crashed with 'NoneType' object has no attribute 'get' on any event without a custom goal — Garmin sends customGoal: null rather than omitting the key, so .get(key, {}) never applied. Affected most real calendars.
• Fix: garmin_zones crashed with 'Garmin' object has no attribute 'get_heart_rate_zones'. That method is absent in garminconnect 0.3.3 (still within the supported range); the tool now reads /biometric-service/heartRateZones directly, which is stable across versions.
• Fix: a missing intermediate zone floor no longer makes the zone below it extend all the way to max HR and overlap every zone above it.
• Fix: nested payloads that Garmin sends as null (summaryDTO, metadataDTO, dailySleepDTO, sleepScores, hrvSummary, userData, workoutSteps, acuteTrainingLoadDTO, training load balance map) are now coerced to empty containers instead of raising.
• Test: statement coverage 90% → 100% (171 tests). server.py is measured now instead of omitted, so the 15 tool registrations are actually asserted.
• Test: tests/test_client.py no longer reloads the client module, which is why CI had to skip it with -k 'not test_get_client'; that filter is gone.
• Test: test_e2e.py covers all 15 tools (was 9) and keeps going after a failure so one broken tool does not hide the rest.
• Repackage: the 0.1.5 sdist accidentally shipped a local notes file.

0.1.5

• New: garmin_race_prediction — predicted 5K/10K/half/marathon times, with 90-day and 1-year trends.
• New: garmin_personal_records — personal bests with the activity that set each one.
• New: garmin_zones — per-sport heart rate zone boundaries, lactate threshold, and FTP.
• Fix: serverInfo.version reported the mcp dependency's version instead of this package's.
• Docs: client setup for Chatbox and opencode, troubleshooting table, environment variables.

0.1.4

• Cap mcp<2.0 so lock-ignoring installers (uvx, pip) stop resolving mcp 2.x.

License

MIT © 2026 Haining Yu

This project is built on top of the excellent garminconnect library. It is not an official Garmin product. Please adhere to Garmin Connect's terms of service when using this tool.