# Garmin Connect (pypi · garmin-personal-mcp)

Garmin Connect on Garmin's official Personal API: sleep, HRV, body battery, activities.

- Trust score: 63/100 (medium)
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-10-23

## Components

- pypi · `garmin-personal-mcp`: 63/100 (this document), [markdown](https://verifymcp.io/servers/mason-levyy-garmin-personal-mcp/garmin-personal-mcp.md), [page](https://verifymcp.io/servers/mason-levyy-garmin-personal-mcp/garmin-personal-mcp)

## Channel facts

- Registry: `pypi`
- Package: `garmin-personal-mcp`
- Version: `0.1.1`
- Transport: `stdio`

## Trust breakdown

How this component scores in each security and reliability category. Every signal is checked automatically from public evidence about the published package, including repeated runs of it in an isolated sandbox, and we only credit what we can confirm. Scores are 0–100 per category. Scoring method: https://verifymcp.io/docs/scoring (what has changed: https://verifymcp.io/docs/scoring/changelog)

Scored 2026-10-23.

- **Supply Chain Security**: 50/100
  - Malware scan not yet available for this package.
  - No known CVEs affecting this package version or its production dependencies.
  - Runs hatchling.build at install time, a recognised build step with no custom scripting around it.
  - 0 of 33 dependencies flagged as unhealthy.
- **Provenance & Transparency**: 100/100
  - Source repository is publicly reachable at the declared URL.
  - Cryptographically verified build provenance (signed, bound to Mason-Levyy/garmin-personal-mcp).
  - Clear OSI-approved license (MIT).
  - Actively maintained (last published 0 days ago).
  - Publishes a security disclosure policy (SECURITY.md).
- **Schema Quality & AI Usability**: 68/100
  - AI-judged instruction clarity (good).
  - Context-footprint check failed: tool/resource definitions use about 2738 tokens (~105/item across 26 items; 26 tools + 0 resources), over budget; trim descriptions and params.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 3/100
  - Stability observed for 1 of 30 days with no destabilising changes; credit accrues until the full window elapses.
- **Tool Coverage**: 67/100
  - 100% of tools have a non-trivial description (not blank, and not just the tool's name).
  - 0% of tool parameters carry a description.
- **Tool Safety**: 100/100
  - No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.
  - We read all 26 captured tool definition(s), and no name or description among them implies an irreversible operation.
  - An AI judge read all 26 captured unit(s) of tool text and found none that tries to manipulate the model reading it.
- **Capabilities**: 100/100
  - Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.

## Install

### How do I install the Garmin Connect MCP server?

Garmin Connect runs locally as a PyPI package, launched with uvx garmin-personal-mcp. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.

### Claude

```bash
claude mcp add mason-levyy-garmin-personal-mcp -- uvx garmin-personal-mcp
```

### Cursor

```json
{
  "mcpServers": {
    "mason-levyy-garmin-personal-mcp": {
      "command": "uvx",
      "args": [
        "garmin-personal-mcp"
      ]
    }
  }
}
```

### VS Code

```json
{
  "servers": {
    "mason-levyy-garmin-personal-mcp": {
      "command": "uvx",
      "args": [
        "garmin-personal-mcp"
      ]
    }
  }
}
```

### Codex

```bash
codex mcp add mason-levyy-garmin-personal-mcp -- uvx garmin-personal-mcp
```

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "mason-levyy-garmin-personal-mcp": {
      "type": "local",
      "command": [
        "uvx",
        "garmin-personal-mcp"
      ],
      "enabled": true
    }
  }
}
```

### OpenClaw

```bash
openclaw mcp add mason-levyy-garmin-personal-mcp --command uvx --arg garmin-personal-mcp
```

### Hermes

```yaml
mcp_servers:
  mason-levyy-garmin-personal-mcp:
    command: "uvx"
    args: ["garmin-personal-mcp"]
```

### Netclaw

```json
{
  "McpServers": {
    "mason-levyy-garmin-personal-mcp": {
      "Transport": "stdio",
      "Command": "uvx",
      "Arguments": [
        "garmin-personal-mcp"
      ]
    }
  }
}
```

### Vellum

```bash
assistant mcp add mason-levyy-garmin-personal-mcp -t stdio -c uvx -a garmin-personal-mcp
```

### Other

```json
{
  "mcpServers": {
    "mason-levyy-garmin-personal-mcp": {
      "command": "uvx",
      "args": [
        "garmin-personal-mcp"
      ]
    }
  }
}
```

## Changelog

Every change recorded for this component, newest first. Days that predate change tracking, or that we cannot explain, say so: "we were watching and nothing happened" and "we were not watching" are different claims.

### 2026-10-23 (score 63, 0)

- [functional improvement] Stability: unverified → 0.03
- [functional] Package version: 0.1.0 → 0.1.1

### 2026-10-22 (score 63)

First indexed and scored.

## MCP tools (26)

### `garmin_get_day` (~90 tokens)

Get day overview

One day at a glance: daily summary (steps, calories, intensity minutes,
resting HR, stress, body battery), last night's sleep, HRV, body battery,
stress, and the day's activities. A section Garmin has no data for yet
comes back as {"error": ...} while the rest still load.

date: YYYY-MM-DD (default: today).

Input parameters:

- `date`

### `garmin_get_daily_summary` (~75 tokens)

Get daily summary

Every all-day wellness total for one date: steps, distance, floors,
total/active/BMR calories, intensity minutes, heart rate, stress, body
battery, SpO2, respiration, and time active/sedentary/asleep.

date: YYYY-MM-DD (default: today).

Input parameters:

- `date`

### `garmin_get_daily_summaries` (~132 tokens)

Get daily summaries

Daily wellness summaries across a date range, grouped per day (movement,
calories, heart rate, intensity minutes, stress, body battery, hydration,
respiration, pulse ox, jet lag). About 1-2 KB per day, so for a long
trend in one metric prefer garmin_get_steps, garmin_get_stress, or
garmin_get_sleep_summaries.

start, end: YYYY-MM-DD inclusive (default: the 7 days ending today). Ranges
over a year are fetched in yearly requests.

Input parameters:

- `end`
- `start`

### `garmin_get_steps` (~66 tokens)

Get steps

Daily total steps, distance (meters), and step goal.

start, end: YYYY-MM-DD inclusive (default: the 7 days ending today). Any
length works; long ranges are fetched 28 days at a time.

Input parameters:

- `end`
- `start`

### `garmin_get_stress` (~78 tokens)

Get stress

Daily overall stress level (0-100) and seconds spent in high, medium,
low, and rest stress.

start, end: YYYY-MM-DD inclusive (default: the 7 days ending today). Any
length works; long ranges are fetched 28 days at a time.

Input parameters:

- `end`
- `start`

### `garmin_get_hydration` (~78 tokens)

Get hydration

Daily water intake, goal, estimated sweat loss, and intake logged during
activities, all in mL.

start, end: YYYY-MM-DD inclusive (default: the 7 days ending today). Any
length works; long ranges are fetched 31 days at a time.

Input parameters:

- `end`
- `start`

### `garmin_get_body_battery` (~139 tokens)

Get body battery

Daily Body Battery: amount charged and drained, plus the events that
moved it (sleep, activities, stress) with Garmin's feedback.

start, end: YYYY-MM-DD inclusive (default: the 7 days ending today). Any
length works; long ranges are fetched 31 days at a time.
chunks: split each day into this many intervals (e.g. 24 for hourly) and
include each interval's lowest and highest level. Omitted, the
every-few-minutes readings are left out to keep the response small.

Input parameters:

- `chunks`
- `end`
- `start`

### `garmin_get_heart_rate` (~78 tokens)

Get heart rate

Resting, minimum, and maximum heart rate for a day, the 7-day resting
average, and any abnormal high/low heart rate alerts.

date: YYYY-MM-DD (default: today).
include_samples: also return the all-day readings (large).

Input parameters:

- `date`
- `include_samples` (boolean)

### `garmin_get_spo2` (~79 tokens)

Get SpO2

Blood oxygen (pulse ox) for a day: average, lowest, latest, sleep
average, 7-day average, hourly averages, and altitude acclimation.

date: YYYY-MM-DD (default: today).
include_samples: also return every individual reading (large).

Input parameters:

- `date`
- `include_samples` (boolean)

### `garmin_get_wellness_activities` (~87 tokens)

Get wellness activities

Wellness activities recorded by the device, each with its type,
start and end time, per-metric summary values, and time in zones. Regular
workouts like runs and rides are in garmin_search_activities instead.

start, end: YYYY-MM-DD inclusive (default: the 7 days ending today).

Input parameters:

- `end`
- `start`

### `garmin_get_sleep` (~89 tokens)

Get sleep

The full sleep record for the night ending on date: sleep score and its
components, deep/light/REM/awake seconds, start and end times, overnight
heart rate, SpO2, respiration, sleep stress, naps, and Garmin's feedback.

date: YYYY-MM-DD, the morning you woke up (default: today, i.e. last night).

Input parameters:

- `date`

### `garmin_get_sleep_summaries` (~81 tokens)

Get sleep summaries

Nightly sleep records across a date range, same fields as
garmin_get_sleep. Use it for sleep trends.

start, end: YYYY-MM-DD inclusive (default: the 7 days ending today). Any
length works; long ranges are fetched 31 days at a time.

Input parameters:

- `end`
- `start`

### `garmin_get_hrv` (~66 tokens)

Get HRV night

One night of heart-rate variability: the summary (last-night average,
5-minute high, weekly average, baseline band, status) plus every reading
taken during sleep.

date: YYYY-MM-DD, the morning you woke up (default: today).

Input parameters:

- `date`

### `garmin_get_hrv_summaries` (~70 tokens)

Get HRV summaries

Nightly HRV summaries across a date range: last-night average, weekly
average, baseline band, status, and Garmin's feedback.

start, end: YYYY-MM-DD inclusive (default: the 7 days ending today).

Input parameters:

- `end`
- `start`

### `garmin_get_weight` (~130 tokens)

Get weight

Daily weight summaries over a range, the range average, and the nearest
weigh-ins before and after it (handy when the range itself has none). Weights are in grams; body composition
(BMI, body fat %, muscle and bone mass) appears when a smart scale
recorded it.

start, end: YYYY-MM-DD inclusive (default: the 7 days ending today).
include_all: list every weigh-in per day with its time and body
composition, not just the latest.

Input parameters:

- `end`
- `include_all` (boolean)
- `start`

### `garmin_get_weight_goals` (~53 tokens)

Get weight goals

Weight goals in effect during a date range and their target ranges.

start, end: YYYY-MM-DD inclusive (default: the 7 days ending today).

Input parameters:

- `end`
- `start`

### `garmin_get_food_log` (~121 tokens)

Get food log

Foods logged in Garmin Connect's nutrition tracker for a day, with
serving sizes, calories and nutrients consumed, nutrition goals, and a
per-meal breakdown.

date: YYYY-MM-DD (default: today).
meal_id: limit to one meal; ids appear in mealDetails of an unfiltered call.
include_media: also return logged food photos.

Input parameters:

- `date`
- `include_goals` (boolean)
- `include_media` (boolean)
- `include_nutrition` (boolean)
- `meal_id`

### `garmin_search_activities` (~563 tokens)

Search activities

Recorded activities (runs, rides, swims, strength, dives, ...), newest
first, with name, type, start time, distance, duration, pace/speed, HR,
power, cadence, calories, elevation, and training effect. Pass an
activityId to garmin_get_activity for splits and full detail.

All filters are optional and combine:
start, end: YYYY-MM-DD, by the activity's local start date.
search: text in the activity name or description.
activity_type: parent type key, e.g. running, cycling, swimming,
strength_training, hiking, walking. activity_subtype: a child key such as
trail_running or indoor_cycling. excluded_activity_subtypes: child keys to
leave out.
event_type: race, training, recreation, fitness, specialEvent, or
uncategorized. favorite: true for favorites only, false for non-favorites.
exclude_children: hide individual legs of multisport activities.
sort_by: a field such as distance, duration, or name (default: start time).
sort_order: asc or desc (default desc).
min_/max_distance (meters), min_/max_duration (timer seconds),
min_/max_elapsed_duration (seconds including pauses), min_/max_elevation
(gain, meters), min_avg_power (watts).
north, south, east, west: a bounding box in decimal degrees around the
start location; give all four or none.
Dives: min_/max_max_depth (centimeters), deco_dive, min_/max_bottom_time
(seconds).
required_fields: activity fields that must be present, e.g. avgPower.
limit, offset: page through results (each activity is about 3-4 KB).

Input parameters:

- `activity_subtype`
- `activity_type`
- `deco_dive`
- `east`
- `end`
- `event_type`
- `exclude_children` (boolean)
- `excluded_activity_subtypes`
- `favorite`
- `limit` (integer)
- `max_bottom_time`
- `max_distance`
- `max_duration`
- `max_elapsed_duration`
- `max_elevation`
- `max_max_depth`
- `min_avg_power`
- `min_bottom_time`
- `min_distance`
- `min_duration`
- `min_elapsed_duration`
- `min_elevation`
- `min_max_depth`
- `north`
- `offset` (integer)
- `required_fields`
- `search`
- `sort_by`
- `sort_order`
- `south`
- `start`
- `west`

### `garmin_get_activity` (~75 tokens)

Get activity

Full detail for one activity: summary metrics (distance, time, pace,
HR, power, cadence, elevation, training effect, calories), device and
location metadata, and split/lap summaries.

activity_id: activityId from garmin_search_activities or garmin_get_day.

Input parameters:

- `activity_id` (integer, required)

### `garmin_get_activity_workouts` (~54 tokens)

Get activity workouts

The structured workout(s) followed during an activity, step by step
with targets.

activity_id: activityId from garmin_search_activities or garmin_get_day.

Input parameters:

- `activity_id` (integer, required)

### `garmin_download_activity` (~114 tokens)

Download activity file

Download an activity's original file (a ZIP, usually holding a .fit)
and save it on the machine running this server as
activity-<activity_id>.zip, replacing any earlier download. Returns the
saved path, size, and the files inside.

activity_id: activityId from garmin_search_activities.
directory: where to save (default: GARMIN_MCP_DOWNLOAD_DIR, else a garmin
folder in the Downloads directory).

Input parameters:

- `activity_id` (integer, required)
- `directory`

### `garmin_get_profile` (~45 tokens)

Get profile settings

Profile settings: display name, measurement system and display formats,
time zone, hydration units and containers, and preferred training days.
Check measurementSystem before converting units for the user.

### `garmin_get_heart_rate_zones` (~66 tokens)

Get heart rate zones

Heart rate zone floors per sport, with the training method and the
resting, max, and lactate threshold heart rates the zones were built on.

generate_defaults: return Garmin's default zones when none are configured.

Input parameters:

- `generate_defaults` (boolean)

### `garmin_get_fitness_age` (~106 tokens)

Get fitness age

Fitness age versus chronological age as of a date, the achievable
fitness age, and the components behind it (vigorous days and minutes,
resting heart rate, BMI or body fat %), or the reason none is available.

date: YYYY-MM-DD (default: today).
full_history_scan: search all history for the latest value; false limits
it to the 28 days before date.

Input parameters:

- `date`
- `full_history_scan` (boolean)

### `garmin_get_menstrual_cycle` (~73 tokens)

Get menstrual cycle

Menstrual cycle summary as of a date: current phase, day in cycle, days
until the next phase, period length, fertile window, predicted ovulation
and cycle length, and pregnancy details when tracking a pregnancy.

date: YYYY-MM-DD (default: today).

Input parameters:

- `date`

### `garmin_get_menstrual_day` (~130 tokens)

Get menstrual cycle day

One day in detail: logged symptoms, flow, mood, and other entries, that
day's cycle summary, and weekly weight goal ranges during pregnancy.

date: YYYY-MM-DD (default: today).
today: the reference date for predictions (default: today).
reduced: return a lighter response.
skip_baby_movement: leave out kick counts.
include_analysis: add Garmin's cycle analysis.

Input parameters:

- `date`
- `include_analysis` (boolean)
- `reduced` (boolean)
- `skip_baby_movement` (boolean)
- `today`

## Diagnostics

Captured diagnostic sections: Provenance, Install scripts, Dependencies. The full working is on the page: https://verifymcp.io/servers/mason-levyy-garmin-personal-mcp/garmin-personal-mcp#diagnostics

## Score history

- 2026-10-23: 63
- 2026-10-22: 63

## Common questions

### What is the Garmin Connect MCP server?

Garmin Connect is an MCP server listed in the public MCP registry as io.github.Mason-Levyy/garmin-personal-mcp. Garmin Connect on Garmin's official Personal API: sleep, HRV, body battery, activities. This page covers its PyPI package (garmin-personal-mcp).

### Is the Garmin Connect MCP server safe to use?

Garmin Connect scores 63 out of 100 on VerifyMCP. We found no known CVEs affecting it as of 23 October 2026. Its build provenance is signed and verified. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.

### What tools does the Garmin Connect MCP server expose?

Garmin Connect exposes 26 tools: garmin_get_day, garmin_get_daily_summary, garmin_get_daily_summaries, garmin_get_steps, garmin_get_stress, and 21 more. Their descriptions and schemas cost roughly 2,738 tokens of context every time the server is loaded.

### Is the Garmin Connect MCP server still maintained?

Garmin Connect is still listed as active in the MCP registry. We last reached this channel on 23 October 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.

### What licence is the Garmin Connect MCP server under?

Garmin Connect declares the MIT licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.

## Links

- PyPI project: https://pypi.org/project/garmin-personal-mcp/
- Socket report: https://socket.dev/pypi/package/garmin-personal-mcp
- Repository: https://github.com/Mason-Levyy/garmin-personal-mcp
- Changelog RSS feed: https://verifymcp.io/servers/mason-levyy-garmin-personal-mcp/garmin-personal-mcp.xml
- Changelog JSON feed: https://verifymcp.io/servers/mason-levyy-garmin-personal-mcp/garmin-personal-mcp.json
- HTML version of this page: https://verifymcp.io/servers/mason-levyy-garmin-personal-mcp/garmin-personal-mcp