Skip to content
MCP server

durely insights MCP for Garmin

Analyse your full Garmin history locally through the official Personal API

Runs locallyStatus and history
Install
Pricing
Open source
Platforms
CLI, macOS, Linux
Runs
Locally
Version
0.5.2
Listing updated
today

Similar MCP servers

About durely insights MCP for Garmin

durely insights MCP for Garmin is an open-source MCP server for health and science. It runs locally on your machine and is started by your AI client.

This server keeps a local copy of your Garmin Connect history and lets an assistant answer questions about it, from a single run to years of training. It uses Garmin's Personal API with a key you create and can revoke, so no password or scraping is involved. The README calls it early development, so tools and options may change before 1.0, and says it is unofficial and not affiliated with Garmin.

The first question triggers a background sync; recent activities appear within seconds and the rest of the history follows in a few minutes, then data refreshes when it is over an hour old. Second-by-second detail comes from each activity's original FIT file, including laps, swim lengths, heart rate, power and cadence, plus VO2max, recovery time and lactate threshold when the device records them.

Built-in analysis covers time in zones, training load and fitness, fatigue and form, aerobic decoupling, best efforts, recovery trends and comparing similar sessions, and an assistant can run read-only SQL for anything else. It is read-only, and name, account ID and GPS positions stay out of answers unless you ask for a route. It needs Node.js 24 or later, or Docker.

Install

Run in a terminal

claude mcp add garmin-insights-mcp --env GARMIN_PERSONAL_API_KEY='<GARMIN_PERSONAL_API_KEY>' -- npx -y @durely/garmin-insights-mcp

Add to claude_desktop_config.json

{
  "mcpServers": {
    "garmin-insights-mcp": {
      "command": "npx",
      "args": [
        "-y",
        "@durely/garmin-insights-mcp"
      ],
      "env": {
        "GARMIN_PERSONAL_API_KEY": "<GARMIN_PERSONAL_API_KEY>"
      }
    }
  }
}

Add to ~/.cursor/mcp.json

{
  "mcpServers": {
    "garmin-insights-mcp": {
      "command": "npx",
      "args": [
        "-y",
        "@durely/garmin-insights-mcp"
      ],
      "env": {
        "GARMIN_PERSONAL_API_KEY": "<GARMIN_PERSONAL_API_KEY>"
      }
    }
  }
}

Add to .vscode/mcp.json

{
  "servers": {
    "garmin-insights-mcp": {
      "type": "stdio",
      "command": "npx",
      "args": [
        "-y",
        "@durely/garmin-insights-mcp"
      ],
      "env": {
        "GARMIN_PERSONAL_API_KEY": "<GARMIN_PERSONAL_API_KEY>"
      }
    }
  }
}

Add to ~/.codeium/windsurf/mcp_config.json

{
  "mcpServers": {
    "garmin-insights-mcp": {
      "command": "npx",
      "args": [
        "-y",
        "@durely/garmin-insights-mcp"
      ],
      "env": {
        "GARMIN_PERSONAL_API_KEY": "<GARMIN_PERSONAL_API_KEY>"
      }
    }
  }
}

Add to your client's MCP settings (most use this shape)

{
  "mcpServers": {
    "garmin-insights-mcp": {
      "command": "npx",
      "args": [
        "-y",
        "@durely/garmin-insights-mcp"
      ],
      "env": {
        "GARMIN_PERSONAL_API_KEY": "<GARMIN_PERSONAL_API_KEY>"
      }
    }
  }
}

Using several servers? Build one config file with the MCP config generator.

Configuration

  • GARMIN_PERSONAL_API_KEYYour Garmin Personal API key. Leave empty if you saved it with `npx -y @durely/garmin-insights-mcp auth` (recommended): the server then reads it from ~/.config/garmin/connect-personal-api-key.
  • GARMIN_MCP_TIMEZONEYour time zone, e.g. Europe/Brussels. Defaults to your computer's time zone.
  • GARMIN_API_KEY_EXPIRESThe date your key expires, e.g. 2027-10-24, so the server can warn you in time.
  • GARMIN_MCP_TIMEZONEYour time zone, e.g. Europe/Brussels. The container doesn't know your computer's time zone, so set it.Required
  • GARMIN_API_KEY_EXPIRESThe date your key expires, e.g. 2027-10-24, so the server can warn you in time.

What it does

Local history store
Syncs your Garmin data once to a local database so trend questions answer quickly.
FIT-level detail
Reads laps, swim lengths, heart rate, power and cadence from the original activity files.
Training analysis
Time in zones, load, fitness and fatigue, decoupling and best efforts.
Health and recovery
Sleep, HRV, resting heart rate and Body Battery questions.
Read-only SQL
Assistants can run read-only queries over your data.
Privacy defaults
Name, account ID and GPS positions are withheld unless a route is requested.

Good for

  • Review yesterday's run with splits and heart rate
  • Compare the bike legs of two triathlons lap by lap
  • See how sleep and HRV changed over a month
  • Check whether a regular route is getting faster

Pricing

Open source

durely insights MCP for Garmin FAQ

Do I give it my Garmin password?

No. It uses a Personal API key you create in Garmin Connect, valid from 30 days to 1 year.

Where is my data stored?

On your own machine; the README says your data stays local.

Can it change my Garmin account?

No, it is read-only.

How do I run it?

With npx using @durely/garmin-insights-mcp on Node.js 24 or later, or with the ghcr.io/durely/garmin-insights-mcp Docker image.

Is durely insights MCP for Garmin free?

Yes. durely insights MCP for Garmin is open source, so you can use and self-host it for free.

How do I add durely insights MCP for Garmin to Claude Code?

Run this command in your terminal: claude mcp add garmin-insights-mcp --env GARMIN_PERSONAL_API_KEY='<GARMIN_PERSONAL_API_KEY>' -- npx -y @durely/garmin-insights-mcp

What are the best alternatives to durely insights MCP for Garmin?

The closest alternatives to durely insights MCP for Garmin are Tooluniverse, Oya Browser, BasalFit, Ebi Ols and Clinicaltables.

Where this comes from

  • Description: written from the project's README.
  • Install steps: from the official MCP Registry entry.

How AIPoweredBot checks servers