New:Introducing Socket Scanning for VS Code Marketplace Extensions.Learn more →
Get Started

garmin-connect-personal-api-mcp

Package Overview
Dependencies
Maintainers
1
Versions
2
Alerts
File Explorer

Advanced tools

Socket logo

Install Socket

Detect and block malicious and high-risk dependencies

Install

garmin-connect-personal-api-mcp

Unofficial MCP server for the Garmin Connect Personal API: let Claude and other AI assistants read your sleep, HRV, steps, stress, Body Battery, and activities

latest
Source
npmnpm
Version
1.0.0
Version published
Weekly downloads
99
-72.58%
Maintainers
1
Weekly downloads
 
Created
Source

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

  • Create a Personal API key on Garmin Connect.
  • 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.

Keywords

mcp

FAQs

Package last updated on 23 Oct 2026

Related posts