mcpField
G
Garmin Connect Personal API

Garmin Connect Personal API

Local
github.comHealth0Updated 5d ago

About Garmin Connect Personal API

Garmin Connect Personal API is an unofficial, read-only MCP server for AI assistants that need to query Garmin Connect health and activity data. It exposes personal metrics through Garmin's Personal API without allowing account changes.

Key features

  1. 01Sleep, HRV, and heart-rate data
  2. 02Steps, stress, and Body Battery
  3. 03Activity details and search
  4. 04Weight, nutrition, and cycle data

Use cases

  1. 01Compare sleep across date ranges
  2. 02Review monthly HRV trends
  3. 03Summarize recent runs
  4. 04Relate sleep duration to stress

MCP support

It exposes Garmin Connect Personal API data as tools for MCP clients. The server is read-only and authenticates with a Garmin Personal API key.

Configuration

Local server config is the same for every client. Copy it into your client’s MCP config file.

mcp.json · Universal config
{
"mcpServers": {
"dynamicsninja-garmin-connect-personal-api": {
"command": "npx",
"args": [
"-y",
"garmin-connect-personal-api-mcp"
],
"env": {
"GARMIN_PERSONAL_API_KEY": "<GARMIN_PERSONAL_API_KEY>"
}
}
}
}
Run commandnpx -y garmin-connect-personal-api-mcp
Environment variables to set
GARMIN_PERSONAL_API_KEYSecretGarmin Connect Personal API key from connect.garmin.com/app/settings/personalApiToken. Optional if the key is saved in ~/.config/garmin/connect-personal-api-key.

Local servers need a runtime on your machine (e.g. Node.js 18+). Config file locations differ by client; see your client’s docs.

Packages
npmgarmin-connect-personal-api-mcp1.0.0

Tools

24

Saved tool list · updated 5d ago

ParameterTypeRequiredDescription
limitintegerNoMaximum number of activities. Defaults to 20.
startintegerNoZero-based result offset. Defaults to 0.
endDatestringNoOnly activities on or before this date, YYYY-MM-DD.
startDatestringNoOnly activities on or after this date, YYYY-MM-DD.
activityTypestringNoActivity type filter, such as running, cycling, or hiking.

Details

From the project README

Garmin Connect Personal API MCP Server

npm License

Unofficial. This is a community project. It isn't affiliated with or endorsed by Garmin.

An MCP server that lets Claude and other AI assistants read your Garmin Connect data through Garmin's official Personal API. Ask questions such as:

  • "How has my sleep been this week compared with last week?"
  • "Is my HRV trending up or down this month?"
  • "Summarize my last five runs."
  • "On days I slept less than 6 hours, what was my stress like?"

It's built on garmin-connect-personal-api-js and is read-only: it can't change anything in your account.

Setup

  1. Create a Personal API key on Garmin Connect.
  2. Add the server to your AI client, as shown below, with the key in GARMIN_PERSONAL_API_KEY. You need Node.js 20.4 or newer.
Claude Desktop

Open Settings → Developer → Edit Config and add:

{
  "mcpServers": {
    "garmin": {
      "command": "npx",
      "args": ["-y", "garmin-connect-personal-api-mcp"],
      "env": {
        "GARMIN_PERSONAL_API_KEY": "your-personal-api-key"
      }
    }
  }
}

Restart Claude Desktop afterward.

Claude Code
claude mcp add garmin --env GARMIN_PERSONAL_API_KEY=your-personal-api-key -- npx -y garmin-connect-personal-api-mcp
Other MCP clients

Run npx -y garmin-connect-personal-api-mcp as a stdio server with GARMIN_PERSONAL_API_KEY set.

Keeping the key out of client config

Instead of the environment variable, you can save the key in ~/.config/garmin/connect-personal-api-key (on Windows, %USERPROFILE%\.config\garmin\connect-personal-api-key) and leave env out of the configuration. This is the same key file the gc-personal CLI uses.

Tools

ToolData
get_daily_sleep_summariesOne summary per night: duration, stages, sleep score
get_daily_sleepDetailed sleep for one night
get_daily_summariesDaily steps, calories, heart rate, stress, Body Battery, intensity minutes
get_daily_hrv, get_daily_hrv_summariesHeart rate variability for a night, or per night over a range
get_daily_heart_rate, get_heart_rate_zonesHeart rate samples for a day, and heart rate zones
get_daily_stress, get_daily_steps, get_daily_hydrationDaily statistics over a date range
get_daily_body_battery, get_daily_spo2Body Battery and SpO2
search_activities, get_activity, get_activity_workoutsActivities and their details
get_weight_measurements, get_effective_weight_goals, get_daily_food_logsWeight, goals, and nutrition
get_fitness_age, get_user_profile_settingsFitness age and profile settings
get_menstrual_cycle_summary, get_menstrual_cycle_day_viewMenstrual cycle data
get_wellness_activity_summariesWellness activity summaries
api_getAny other Personal API GET endpoint

Dates use YYYY-MM-DD and default to today. Date ranges are inclusive.

How it works

The server exchanges your API key for a bearer token and caches it in ~/.config/garmin/connect-personal-api-bearer-token.json, shared with the gc-personal CLI. Tokens are renewed before they expire, and a rejected token is replaced automatically.

Your data goes from Garmin to the AI client you connect, so it's subject to that client's privacy terms.

License

Apache 2.0. See LICENSE.

Comments

Markdown supported

New to MCP?

From what the protocol is to installing your first server, these answers cover most first questions.

An open protocol that defines how AI applications connect to external tools and data in a uniform way. Clients talk to the model; MCP servers provide tools, resources and prompt templates. They exchange standard messages, so one server can be reused by many clients.