Garmin Mcp Unofficial

Name: Garmin Mcp Unofficial
Author: davidmosiah

@davidmosiah

Repository

About Garmin Mcp Unofficial

No overview available yet

Basic information

Config

Add this server to your MCP-compatible client using the configuration below.

{
  "mcpServers": {
    "garmin": {
      "command": "npx",
      "args": [
        "-y",
        "garmin-mcp-unofficial"
      ]
    }
  }
}

Tools

verify local setup before calling Garmin Connect

inventory supported data domains, scopes, privacy modes and recommended first calls without calling Garmin APIs.

daily readiness, sleep, load, action candidates

scorecard, bottlenecks, next-week plan

Overview

What is Garmin Mcp Unofficial?

A local-first MCP server that connects AI agents to your Garmin sleep, HRV, Body Battery, stress, training readiness, and activities via the unofficial Garmin Connect personal-token mode. It is an independent, unofficial project built for individuals who want their AI to work with Garmin data without sharing credentials or tokens with any agent.

How to use Garmin Mcp Unofficial?

Install via npm, then run setup, auth, and doctor commands. After authentication, add the MCP server configuration to your client (e.g., Claude Desktop, Cursor, Hermes). Example: npx -y garmin-mcp-unofficial setup --auth then add the JSON config to mcpServers.

Key features of Garmin Mcp Unofficial

Local-first: tokens never leave your machine.
Pure Node login – no Python required by default.
Provides daily and weekly summaries, plus intraday investigation prompts.
Covers sleep, HRV, Body Battery, stress, training readiness, activities, heart rate, and more.
Optional SQLite cache and privacy mode settings.
Garmin password is never stored – only short-lived tokens persist locally.

Use cases of Garmin Mcp Unofficial

Daily health and training check-in with a single agent query.
Weekly trend review across activity, sleep, stress, and body battery.
Investigate one day's signals (heart, stress, Body Battery, activity).
Verify setup and data availability before calling Garmin APIs.

FAQ from Garmin Mcp Unofficial

What data is available?

Sleep duration and stages, HRV status, Body Battery, stress, training readiness, training status, daily movement (steps, calories, distance, floors, intensity minutes), heart rate, activities, body composition, and hydration when supported by the device/account. Continuous device telemetry is not exposed.

How are credentials handled?

Your Garmin password is never stored. The auth command prompts locally for credentials and MFA, then saves only short-lived Garmin Connect tokens to ~/.garmin-mcp/garmin_tokens.json with user-only permissions. The MCP client never sees your credentials.

Is this an official Garmin product?

No. This is an unofficial project, not affiliated with, endorsed by, or supported by Garmin. It uses the unofficial Garmin Connect personal-token mode and can break if Garmin changes private auth or endpoints.

What are the runtime requirements?

Node.js 20+ and a Garmin Connect account with active devices. Python 3 is only needed if you opt into the legacy auth --use-python flow; the default login is pure Node.

Can I configure privacy or caching?

Yes. Set GARMIN_PRIVACY_MODE to summary, structured, or raw (default summary). Local read-through cache is opt-in via GARMIN_CACHE=sqlite. The token path and domain are also configurable via environment variables.