Comprehensive Model Context Protocol server for managing Home Assistant through AI assistants.
Garmin Connect is installed from its publisher's own source and answers where it runs, so this marketplace is not in the path of a single call. There is no address here to send one to, and a panel that pretended otherwise would be showing you an answer we made up. Install it and call it from your own client — the Installation tab has the entry for each one.
What it does
Garmin Connect on Garmin's official Personal API: sleep, HRV, body battery, activities.
Quickstart
# 1 — add it to Claude Code
claude mcp add --scope user mason-levyy-garmin-connect-mcp '--' uvx garmin-personal-mcp
# 2 — ask your agent for something these tools do
# garmin_get_day, garmin_get_daily_summary, garmin_get_daily_summaries and 23 more
Garmin Connect costs nothing on mcprush: there is no plan to choose here, no cap to set and nothing mcprush can bill you for.
Collected from a public index. Nobody has claimed this account, so nothing here was written by its author — claim it if it is yours.
Where are you running it?
Every route below installs the same thing and ends at the same approval screen. This one runs on your machine: your client starts Garmin Connect as a process under your own user, with your files and your network, so the tool surface below is what it can do to your computer rather than to a server somewhere else. Its scan result is on the Security tab — read the surface before you approve it.
This is a public server: you run it yourself and this marketplace is not in the path. You need uv (docs.astral.sh/uv): uvx comes with it. Claude Code registers it in one command; --scope user makes it available in every project. The '--' is in quotes so that PowerShell passes it on.
claude mcp add --scope user mason-levyy-garmin-connect-mcp '--' uvx garmin-personal-mcpReconnect, or start a new session, and the tools appear in the model’s tool list.
Nothing is required, but it can take GARMIN_PERSONAL_API_KEY (Garmin Connect Personal API key (optional; 'garmin-personal-mcp auth' saves one instead)), GARMIN_MCP_DOWNLOAD_DIR (Where garmin_download_activity saves activity files) if you want to set them.
One config entry your client uses to start the process locally. A local server runs with your file system and your network, which is why it is priced without metering.
26 tools, with what each one reads, writes and reaches shown before you agree — the same list on every route above. Read the tool surface.
Tool surface
What the model actually sees. Descriptions are diffed on every release — see version history.
Read from its source code. A server that builds its tool list when it starts can list more tools than this.
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.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| date | string | no | — |
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.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| date | string | no | — |
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…
| Parameter | Type | Required | Notes |
|---|---|---|---|
| start | string | no | — |
| end | string | no | — |
Daily total steps, distance (meters), and step goal.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| start | string | no | — |
| end | string | no | — |
Daily overall stress level (0-100) and seconds spent in high, medium, low, and rest stress.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| start | string | no | — |
| end | string | no | — |
Daily water intake, goal, estimated sweat loss, and intake logged during activities, all in mL.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| start | string | no | — |
| end | string | no | — |
Daily Body Battery: amount charged and drained, plus the events that moved it (sleep, activities, stress) with Garmin's feedback.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| start | string | no | — |
| end | string | no | — |
| chunks | integer | no | — |
Resting, minimum, and maximum heart rate for a day, the 7-day resting average, and any abnormal high/low heart rate alerts.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| date | string | no | — |
| include_samples | boolean | no | — |
Blood oxygen (pulse ox) for a day: average, lowest, latest, sleep average, 7-day average, hourly averages, and altitude acclimation.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| date | string | no | — |
| include_samples | boolean | no | — |
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.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| start | string | no | — |
| end | string | no | — |
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.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| date | string | no | — |
Nightly sleep records across a date range, same fields as
| Parameter | Type | Required | Notes |
|---|---|---|---|
| start | string | no | — |
| end | string | no | — |
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.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| date | string | no | — |
Nightly HRV summaries across a date range: last-night average, weekly average, baseline band, status, and Garmin's feedback.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| start | string | no | — |
| end | string | no | — |
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.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| start | string | no | — |
| end | string | no | — |
| include_all | boolean | no | — |
Weight goals in effect during a date range and their target ranges.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| start | string | no | — |
| end | string | no | — |
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.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| date | string | no | — |
| meal_id | integer | no | — |
| include_goals | boolean | no | — |
| include_nutrition | boolean | no | — |
| include_media | boolean | no | — |
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.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| start | string | no | — |
| end | string | no | — |
| search | string | no | — |
| activity_type | string | no | — |
| activity_subtype | string | no | — |
| excluded_activity_subtypes | array | no | — |
| event_type | string | no | — |
| favorite | boolean | no | — |
| exclude_children | boolean | no | — |
| sort_by | string | no | — |
| sort_order | string | no | — |
| min_distance | integer | no | — |
| max_distance | integer | no | — |
| min_duration | integer | no | — |
| max_duration | integer | no | — |
| min_elapsed_duration | integer | no | — |
| max_elapsed_duration | integer | no | — |
| min_elevation | integer | no | — |
| max_elevation | integer | no | — |
| min_avg_power | integer | no | — |
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.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| activity_id | integer | yes | — |
The structured workout(s) followed during an activity, step by step with targets.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| activity_id | integer | yes | — |
Download an activity's original file (a ZIP, usually holding a .fit) and save it on the machine running this server as
| Parameter | Type | Required | Notes |
|---|---|---|---|
| activity_id | integer | yes | — |
| directory | string | no | — |
Profile settings: display name, measurement system and display formats, time zone, hydration units and containers, and preferred training days.
Takes no parameters.
Heart rate zone floors per sport, with the training method and the resting, max, and lactate threshold heart rates the zones were built on.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| generate_defaults | boolean | no | — |
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.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| date | string | no | — |
| full_history_scan | boolean | no | — |
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.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| date | string | no | — |
One day in detail: logged symptoms, flow, mood, and other entries, that day's cycle summary, and weekly weight goal ranges during pregnancy.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| date | string | no | — |
| today | string | no | — |
| reduced | boolean | no | — |
| skip_baby_movement | boolean | no | — |
| include_analysis | boolean | no | — |
- Every tool, no call limit
- No card, and mcprush charges nothing for it
- Source published under MIT
- Runs on your machine — nothing of it reaches our gateway
- Nothing to cap, because mcprush bills nothing
What counts against your monthly calls
| Tool | Unit | Calls used | Out of the allowance |
|---|
Nothing here is billable: mcprush charges nothing to install Garmin Connect or to call it, at any volume.
Two independent axes, because powerful and malicious are different questions. The grade is threat only. The capability level is blast radius, and it is never a penalty on the grade — it is priced as one subtract-only term in the score, where you can see it.
| Term | Level | What it prices | Points |
|---|---|---|---|
| capability-exposure | minimal | capability blast radius (minimal) — client exposure if the model is manipulated | −0 |
| verification-discount | source | publisher verification (provenance) — cryptographic build provenance ties the artifact to its source | −0 |
| coverage-honesty | source | inspection depth (source) — how much of the target the scan could see | −0 |
What the scan could actually read
A grade is only as meaningful as its coverage, so the scanner publishes its own depth before it publishes its result.
Tools were statically extracted from the published source (26 recovered), not enumerated from a running server. Tool-poisoning, Unicode-smuggling, capability and toxic-flow analysis ran on this inferred surface, but a mis-parsed registration could be missed or mis-attributed, so tool-derived findings are capped below “confirmed”. To grade the real runtime surface, scan the running server: --command "npx -y <package>".
Capability — what it could do if the model were manipulated
Tags derived from each tool’s schema and the implementation, not from what the tool calls itself. minimal is the level these add up to.
| Tool | Capability tags | Why the tag was assigned |
|---|---|---|
| garmin_get_day | no tags | |
| garmin_get_daily_summary | no tags | |
| garmin_get_daily_summaries | no tags | |
| garmin_get_steps | no tags | |
| garmin_get_stress | no tags | |
| garmin_get_hydration | no tags | |
| garmin_get_body_battery | no tags | |
| garmin_get_heart_rate | no tags | |
| garmin_get_spo2 | no tags | |
| garmin_get_wellness_activities | no tags | |
| garmin_get_sleep | no tags | |
| garmin_get_sleep_summaries | no tags | |
| garmin_get_hrv | no tags | |
| garmin_get_hrv_summaries | no tags | |
| garmin_get_weight | no tags | |
| garmin_get_weight_goals | no tags | |
| garmin_get_food_log | no tags | |
| garmin_search_activities | no tags | |
| garmin_get_activity | no tags | |
| garmin_get_activity_workouts | no tags | |
| garmin_download_activity | untrusted-input | untrusted-input: keyword "download" |
| garmin_get_profile | no tags | |
| garmin_get_heart_rate_zones | no tags | |
| garmin_get_fitness_age | no tags | |
| garmin_get_menstrual_cycle | no tags | |
| garmin_get_menstrual_day | no tags |
Toxic-flow graph
The lethal trifecta, checked as a graph rather than as a checklist: untrusted input, a sensitive source and an external sink have to meet before there is a path worth worrying about.
The public result for this release does not print the flow graph, so there is nothing to show here. That is not the same as "no paths were found": what the scan did read is above, under coverage.
Supply chain and provenance
This is the first scan of this surface here, so there is nothing yet to compare it against.
Every result on this tab comes from one deterministic pass over the published package — offline, rule by rule, and auditable line by line above. Same methodology version, same bytes, same score.
Release history
Always latest — the install command names no version, so it installs the newest release when it runs; the current release on file is 0.3.0. Pin a release below and the command asks for exactly that one.
No release note was published with this version.
No release note was published with this version.
- The version this listing was on when mcprush began following its releases. The registry was not asked when it shipped, so this row carries no date.
One review per account, from a signed-in account that does not publish this listing. Nothing else is asked — you can say what you think before you install it. Publishers can reply once per review, and a review can be edited or deleted by whoever wrote it.
Any signed-in account that does not publish Garmin Connect can review it, once — before installing it or after. A review from an account that has installed it is marked as one.
Nobody has reviewed this listing. The rating on the card is the mean of the reviews written here and nothing else, so there is no rating until somebody writes the first — which takes a signed-in account that does not publish it, and nothing else.