MCP.so
Sign In

Garmin MCP Server

@Taxuspt

Basic information

Category

Other

License

MIT

Transports

stdio

Author

Taxuspt

Submitted by

Alexandre Domingues

About Garmin MCP Server

MCP server to access Garmin data

Before you connect

Documentation reviewed 2026-10-25

When to choose this server

This community server accesses Garmin data through python-garminconnect. Account authentication is a separate first-time step from running the MCP service.

Setup and limitations

Run garmin-mcp-auth interactively to create local credentials, then launch garmin-mcp in the MCP client. Do not use the authentication command as the server command. If data access expires, repeat the upstream authentication procedure rather than placing your password in the shared client configuration.

These notes check the linked documentation, not a live authenticated connection. Suggested checks are steps for you to run.

Garmin MCP Server config

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

{
  "mcpServers": {
    "garmin": {
      "command": "uvx",
      "args": [
        "--python",
        "3.12",
        "--from",
        "git+https://github.com/Taxuspt/garmin_mcp",
        "garmin-mcp"
      ]
    }
  }
}

Garmin MCP Server tools

Tool list not available yet

This listing does not currently have a tool list to display. This does not mean the server has no tools; check its documentation for supported capabilities.

Fetch the live tool list by running this server in a temporary sandbox using the button above.

Overview

What is Garmin MCP?

This Model Context Protocol (MCP) server connects to Garmin Connect and exposes your fitness and health data to Claude and other MCP-compatible clients. It leverages the python-garminconnect library to access Garmin’s API.

How to use Garmin MCP?

Authenticate once by running uvx --python 3.12 --from git+https://github.com/Taxuspt/garmin_mcp garmin-mcp-auth. Then add the server to your MCP client (e.g., Claude Desktop) using the uvx command with the garmin-mcp tool. Optionally filter which of the 110+ tools are exposed via the GARMIN_ENABLED_TOOLS or GARMIN_DISABLED_TOOLS environment variables.

Key features of Garmin MCP

  • List and paginate recent activities
  • Edit activity name, type, description, and more
  • Access health metrics: steps, heart rate, sleep, stress
  • View body composition, training status, and readiness
  • Manage gear, workouts, and training plans
  • Download raw activity files (FIT, GPX, TCX, CSV)

Use cases of Garmin MCP

  • Query your weekly training load and recovery status from Garmin Connect
  • Download a FIT file for detailed power and cadence analysis
  • Create and schedule interval workouts without writing Garmin JSON
  • Monitor HRV trend, VO₂ max, and respiration rate over time
  • Manage gear and equipment mileage directly from an LLM chat

Frequently asked questions

1

How do I authenticate for the first time?

Run `garmin-mcp-auth` in your terminal. It will prompt for your Garmin email, password, and an MFA code if enabled. OAuth tokens are saved to `~/.garminconnect` and are valid for approximately 6 months.

2

Can I limit which tools are available to the LLM?

Yes. Set `GARMIN_ENABLED_TOOLS` (comma‑separated allowlist) or `GARMIN_DISABLED_TOOLS` (denylist) as environment variables. Only matching tools will be registered, reducing context for the LLM.

3

What data is not accessible through this server?

A few endpoints are intentionally skipped: high‑volume activity details (GPS tracks), sport‑specific workout uploads, and destructive operations like deleting activities. These can be requested via GitHub issues.

4

Where are downloaded activity files saved?

Files go to the directory specified in the `download_activity_file` call argument, the `GARMIN_FIT_DOWNLOAD_DIR` environment variable, or a persisted directory set via `set_fit_download_dir`. On first run, no directory is configured and the tool will prompt you to set one.

5

Does the server require my Garmin credentials in the MCP config?

No. After the one‑time authentication step, tokens are stored locally. You can omit `GARMIN_EMAIL` and `GARMIN_PASSWORD` from the MCP client configuration.

Comments

More Other MCP servers