Garmin Health MCP
Related Servers
Alternatives to Garmin Health MCP
No user-submitted related servers found.
Related Servers
- AlicenseAqualityBmaintenanceGarmin Connect for Claude and any MCP client, on Garmin's official Personal API. Read-only access to sleep, HRV, Body Battery, stress, heart rate, activities and weight with a revocable key, no password or scraping.261,189 PyPI69MIT
- AlicenseAqualityBmaintenanceEnables Claude to read and review your own Garmin training and recovery data through Garmin's official Connect Personal API, with tools for activities, daily summaries, sleep, HRV, and period analytics.71MIT
- AlicenseNot gradedqualityNot gradedmaintenanceEnables Claude and other MCP clients to read a user's Garmin Connect data through Garmin's official Personal API, supporting queries about recovery, sleep, HRV, activities, heart rate, stress, and related wellness metrics.MIT
- AlicenseNot gradedqualityBmaintenanceEnables Claude and any MCP client to read a user's own Garmin account in plain language, covering activities, time-series charts, thresholds, sleep, HRV, Body Battery, stress, readiness and trends. It also serves a private local dashboard that downloads the full training and health history, correlates metrics across views, and exports any table as CSV.MIT
- AlicenseAqualityCmaintenanceEnables Claude to access and query your Garmin Connect data, including sleep, activities, training load, and health metrics, through a set of read-only MCP tools.28154 PyPI5MIT
- AlicenseNot gradedqualityNot gradedmaintenanceEnables Claude and other remote OAuth-capable MCP clients to read personal Garmin Connect recovery, sleep, HRV, activity, and wellness data through Garmin's official Personal API.1,323 npmMIT
TDQS
Scored across 25 tools
Most tools target clearly distinct Garmin data domains, and the descriptions explicitly differentiate summary vs. detail tools such as get_sleep/get_sleep_summaries and get_hrv/get_hrv_summaries. There is still some overlap because get_daily_summaries aggregates many of the same metrics exposed by get_steps, get_heart_rate, get_stress, get_body_battery, get_spo2, and get_hydration.
Names are consistently snake_case and almost all use the get_<resource> pattern, with activity sub-resources predictably namespaced under get_activity_*. The single search_activities tool uses a different verb but still follows the same verb_noun convention and is semantically clear.
At 25 tools this is at the heavy end of the scale, and several tools are close summary/detail pairs or activity sub-metric calls that could be consolidated. Each tool covers a real data slice, but the surface feels broad and somewhat fragmented for an agent to navigate.
The read-only surface is broad, covering daily wellness, sleep, HRV, body battery, stress, weight, hydration, food, and detailed activity analysis. Minor gaps remain, such as training status/readiness, VO2 max, personal records, and planned-workout listing, but core health workflows are well supported.