How do I install Garmin?

Garmin is a local plugin. Install it using npm package: garmin-mcp-unofficial and add the generated configuration snippet to your AI app's MCP config file. Then restart your AI app.

What credentials does Garmin need?

Garmin requires the following credentials or environment variables: GARMIN_TOKEN_PATH, GARMIN_PRIVACY_MODE, GARMIN_CACHE, GARMIN_CACHE_PATH, GARMIN_DOMAIN. You can find setup instructions on the server detail page.

What AI apps work with Garmin?

Garmin uses the Model Context Protocol (MCP) and works with any MCP-compatible AI app, including Claude, ChatGPT / Codex, Gemini, Copilot, Cursor, and more.

Back to Browse

Garmin MCP Server

by davidmosiah

Developer ToolsUse Caution4.6LocalNew

Free

Privacy-first MCP server for Garmin Connect health, sleep, recovery and activities.

About

Privacy-first MCP server for Garmin Connect health, sleep, recovery and activities.

Security Report

4.6

Use Caution4.6High Risk

This is a well-structured MCP server for accessing personal Garmin health data with appropriate authentication and privacy controls. The code demonstrates good security practices including local token storage, privacy modes, proper input validation via Zod schemas, and read-only data access patterns. Minor code quality observations exist around error handling breadth and logging, but these do not represent security vulnerabilities. Permissions align well with the server's purpose of reading Garmin Connect data. Supply chain analysis found 3 known vulnerabilities in dependencies (0 critical, 3 high severity). Package verification found 1 issue.

4 files analyzed · 8 issues found

Security scores are indicators to help you make informed decisions, not guarantees. Always review permissions before connecting any MCP server.

Permissions Required

This plugin requests these system permissions. Most are normal for its category.

HTTP Network Access

Connects to external APIs or services over the internet.

env_vars

Check that this permission is expected for this type of plugin.

File System Read

Reads files on your machine. Normal for tools that analyze or process local data.

File System Write

Writes or modifies files on your machine. Check that this is expected for the tool.

What You'll Need

Set these up before or after installing:

Optional local path for Garmin Connect tokens. Defaults to ~/.garmin-mcp/garmin_tokens.json. Create it with garmin-mcp-server auth --install-helper.Optional

Environment variable: GARMIN_TOKEN_PATH

Optional payload mode: summary, structured, or raw. Defaults to structured. raw means full supported Garmin Connect payloads, not unrestricted raw sensor telemetry.Optional

Environment variable: GARMIN_PRIVACY_MODE

Optional SQLite cache toggle. Set to true or sqlite to enable.Optional

Environment variable: GARMIN_CACHE

Optional local SQLite cache path. Defaults to ~/.garmin-mcp/cache.sqlite.Optional

Environment variable: GARMIN_CACHE_PATH

Optional Garmin domain override. Use garmin.cn only for China accounts; default is garmin.com.Optional

Environment variable: GARMIN_DOMAIN

How to Install

Add this to your MCP configuration file:

{
  "mcpServers": {
    "io-github-davidmosiah-garminmcp": {
      "env": {
        "GARMIN_CACHE": "your-garmin-cache-here",
        "GARMIN_DOMAIN": "your-garmin-domain-here",
        "GARMIN_CACHE_PATH": "your-garmin-cache-path-here",
        "GARMIN_TOKEN_PATH": "your-garmin-token-path-here",
        "GARMIN_PRIVACY_MODE": "your-garmin-privacy-mode-here"
      },
      "args": [
        "-y",
        "garmin-mcp-unofficial"
      ],
      "command": "npx"
    }
  }
}

Documentation

View on GitHub

From the project's GitHub README.

Garmin MCP Unofficial

Unofficial, local-first Garmin Connect MCP server for AI agents. It lets Claude, Cursor, Windsurf, Hermes, OpenClaw and any MCP-compatible client read processed Garmin signals such as sleep, HRV, Body Battery, stress, training readiness, daily movement and activities.

Not affiliated with Garmin. Not medical advice. Garmin Connect personal mode is unofficial and can break if Garmin changes private auth or endpoints.

Why this exists

Garmin has excellent health and training signals, but the official Garmin Health API is primarily partner-approved. This project gives individual Garmin users a practical open-source bridge for personal AI agents while keeping credentials and tokens local.

What it supports

Profile, user settings and registered devices.
Daily movement: steps, calories, distance, floors and intensity minutes.
Sleep: duration, stages and score when available.
Recovery context: HRV, Body Battery, stress, training readiness/status, respiration and SpO2 when supported by the device/account.
Activities: recent activities, activity details, splits, weather and heart-rate zones.
Body logs: weight range and hydration when available.
Agent summaries: daily and weekly diagnostics with confidence, bottlenecks and practical actions.

Install

No Garmin developer app is required. setup only writes local MCP configuration; it does not ask for your Garmin password.

npx -y garmin-mcp-unofficial setup
npx -y garmin-mcp-unofficial auth --install-helper
npx -y garmin-mcp-unofficial doctor

For Hermes:

npx -y garmin-mcp-unofficial setup --client hermes
npx -y garmin-mcp-unofficial auth --install-helper
npx -y garmin-mcp-unofficial doctor --client hermes

The auth helper prompts locally for Garmin email, password and MFA if needed. This MCP does not store your Garmin password. Tokens are saved under ~/.garmin-mcp/garmin_tokens.json with user-only permissions.

If macOS/Homebrew Python blocks helper installs, auth --install-helper falls back to an isolated virtualenv under ~/.garmin-mcp/venv instead of asking users to debug Python packaging.

If you want one command to write config and immediately start Garmin login, use:

npx -y garmin-mcp-unofficial setup --auth

MCP client config

Generic MCP config:

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

Useful optional env/config values:

GARMIN_TOKEN_PATH=~/.garmin-mcp/garmin_tokens.json
GARMIN_PRIVACY_MODE=summary   # summary | structured | raw
GARMIN_CACHE=sqlite
GARMIN_CACHE_PATH=~/.garmin-mcp/cache.sqlite
GARMIN_DOMAIN=garmin.com      # or garmin.cn

Tool highlights

Start with:

garmin_agent_manifest
garmin_auth_instructions
garmin_connection_status
garmin_daily_summary
garmin_weekly_summary

Low-level tools include:

garmin_get_profile
garmin_get_user_settings
garmin_list_devices
garmin_get_daily_summary
garmin_get_sleep_day
garmin_get_heart_day
garmin_get_hrv_day
garmin_get_stress_day
garmin_get_body_battery_day
garmin_get_training_readiness_day
garmin_list_activities
garmin_get_activity_details
garmin_get_weight_range
garmin_privacy_audit

Privacy modes

summary: minimized identifiers and sensitive fields.
structured: normalized useful data for agents.
raw: upstream Garmin Connect payloads. Use only when explicitly needed.

Raw data boundary

This MCP reads processed Garmin Connect data and supported activity detail payloads. It does not provide unrestricted raw accelerometer, gyroscope or continuous device telemetry.

Human to agent handoff

Paste this into your agent when you want it to install the bridge for you:

Install the unofficial Garmin MCP server for me.
Repository: https://github.com/davidmosiah/garminmcp
Run setup, then auth --install-helper, then doctor.
If this is Hermes, use setup --client hermes and reload MCP with /reload-mcp or hermes mcp test garmin.
Never ask me to paste Garmin passwords, tokens or raw private payloads into chat.
Start with garmin_connection_status, then garmin_daily_summary.
This is not medical advice.