garmin-health-mcp
Related Servers
Alternatives to garmin-health-mcp
No user-submitted related servers found.
Related Servers
- AlicenseAqualityBmaintenanceConnects MCP clients to Garmin Connect data, enabling queries about activities, sleep, heart rate, body battery, and training status.162MIT
- AlicenseNot gradedqualityCmaintenanceConnects to Garmin Connect to expose fitness and health data to MCP-compatible clients, enabling activity management, health metrics, training analytics, workout creation, and more via natural language.MIT
- AlicenseNot gradedqualityDmaintenanceConnects to Garmin Connect and exposes fitness and health data (activities, steps, heart rate, sleep, body composition) to MCP-compatible clients like Claude.MIT
- AlicenseNot gradedqualityCmaintenanceConnects to Garmin Connect and exposes fitness and health data to MCP-compatible clients, enabling activity management, health metrics, training and performance analytics, workout creation/scheduling, gear, nutrition, and related data access.MIT
- FlicenseNot gradedqualityCmaintenanceEnables read-only access to Garmin Connect data through OAuth, including activities, sleep, HRV, body battery, training status, and scheduled TrainingPeaks workouts.-
- AlicenseNot gradedqualityCmaintenanceEnables read-only access to Garmin Connect health and activity data, including daily summaries, sleep, heart rate, stress, Body Battery, HRV, training readiness, activities, and devices.MIT
TDQS
Scored across 21 tools
Most tools target clearly distinct slices of data (per-activity detail vs activities list, power vs load, readiness logging vs readiness history). Some overlap exists among the aggregate/view tools (daily, weekly_report, timeseries, dashboard_data, chart) and between morning_check and daily, but the descriptions do a good job of separating their intended uses.
All names are consistently snake_case and readable. The only deviation is a mix of noun-only names (activities, daily, calories, intraday, sync) and verb-led names (log_garmin_readiness, set_athlete, list_metrics, load_focus), which is minor and does not impede understanding.
21 tools is on the high side, but each maps to a distinct Garmin data domain (sleep/HRV, load, activities, power, readiness, charts, sync). There is mild redundancy among the aggregation/view tools (chart, dashboard_data, timeseries, weekly_report), but the surface is not bloated arbitrarily.
Coverage is broad: recovery, sleep, HRV, load, activities, power, readiness estimation/calibration, plus a raw api_get escape hatch for gaps like weight/hydration/SpO2. The main gaps are native Garmin Training Readiness/Status (explicitly unavailable) and write/fitness-management operations, but core read workflows are covered.