garmin-personal-api-mcp
Related Servers
Alternatives to garmin-personal-api-mcp
No user-submitted related servers found.
Related Servers
- AlicenseBqualityBmaintenanceEnables Claude to access and query your Garmin Connect data—sleep, training, heart rate, and more—through a suite of read-only tools, with an optional write path for creating strength workouts.63MIT
- AlicenseBqualityBmaintenanceEnables users to analyze their own Garmin Connect data—activities, sleep, HRV, Body Battery, training readiness—directly inside Claude Desktop.132MIT
- AlicenseAqualityBmaintenanceDaash connects Garmin Connect to ChatGPT and Claude. Your assistant reads your runs, splits, sleep, HRV, Body Battery and recovery, and writes structured workouts and whole training plans to your Garmin calendar, so they're on your watch at the next sync. Free, hosted, open source. Works on free Claude.264MIT
- AlicenseAqualityBmaintenanceProvides Claude Code and Claude Desktop with safe, read-only access to your local Garmin training data, readiness decisions, run details, and trends so you can get coaching advice in natural language.159MIT
- AlicenseBqualityBmaintenanceConnects Claude to a personal Garmin Connect account so users can ask natural-language questions about sleep, HRV, body battery, stress, heart rate, training readiness and activities, and optionally create or schedule workouts and log weigh-ins. Reads are returned as trimmed summaries with optional full JSON, and writes stay disabled unless explicitly enabled.24MIT
- AlicenseAqualityBmaintenanceEnables 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.28169 PyPI5MIT
TDQS
Scored across 23 tools
Tools are organized around a clear pattern: one aggregated day tool plus per-metric range getters, which keeps most purposes distinct. A few boundaries could confuse an agent—garmin_get_day vs garmin_get_daily_summaries, and garmin_get_sleep vs garmin_get_sleep_detail—but the descriptions explicitly differentiate the aggregate vs range vs single-night-detail cases.
Nearly all tools follow garmin_get_<resource> or garmin_<verb>_<noun> (garmin_list_activities, garmin_download_activity_fit), which is predictable. The one deviation is garmin_api_get, which uses noun_verb ordering as a generic escape hatch, a minor inconsistency.
At 23 tools the surface is on the heavy side for the domain, though each metric-specific getter earns a reasonable place. The breadth of Garmin data (sleep, HRV, stress, activities, weight, nutrition) justifies most of them, but the aggregate plus per-metric split inflates the count.
Coverage is broad: profile, daily summaries, sleep (summary and detail), HRV, Body Battery, stress, steps, hydration, activities (list/get/splits/FIT download), performance metrics, weight and goals, SpO2, fitness age, and nutrition. The generic garmin_api_get escape hatch fills any remaining gaps, so there are no dead ends.