garmin-mcp
Related Servers
Alternatives to garmin-mcp
No user-submitted related servers found.
Related Servers
- AlicenseNot gradedqualityCmaintenanceProvides read access to Garmin Connect health and training data (sleep, heart rate, stress, HRV, activities) and supports writes like creating workouts, editing activities, and exporting files.1,323 npmMIT
- FlicenseAqualityDmaintenanceProvides read-only access to your Garmin Connect health data, including sleep, HRV, body battery, stress, training readiness, and activities, through an MCP server.214-
- AlicenseNot gradedqualityDmaintenanceExposes personal Garmin wellness data through MCP tools for accessing summary, sleep, HRV, heart rate, stress, body battery, and historical data.MIT
- AlicenseAqualityBmaintenanceEnables local, read-only access to Garmin Connect training and wellness data, including activities, sleep, HRV, and daily summaries, for client-side analysis through stdio.5MIT
- AlicenseAqualityCmaintenanceEnables read-only querying of your own Garmin Connect data — sleep, HRV, resting HR, Body Battery, activities, training volume, body composition, and nutrition — through Garmin's official Personal API using a revocable key. Returns compact, unit-labelled JSON shaped around questions so whole date ranges fit in context.91MIT
- 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,568 PyPI69MIT
TDQS
Scored across 13 tools
Each tool targets a distinct Garmin data domain, and descriptions explicitly prioritize tools (e.g., garmin_recovery_status for recovery questions, garmin_sleep_analysis for sleep questions). Potential confusion exists between closely related analytical tools like garmin_daily_summary, garmin_trends, and garmin_recovery_status, but the descriptions clarify their boundaries well.
All tools consistently follow the garmin_ prefix with snake_case naming throughout. The singular/plural distinction between garmin_activity and garmin_activities is clear and intentional.
13 tools is well within the ideal 3-15 range and each covers a distinct, useful slice of Garmin health and fitness data. No tool feels redundant or excessive.
The surface covers a broad range of wellness domains with a strategic raw-API escape hatch for uncovered endpoints like hydration or nutrition. Minor gaps include dedicated structured workout or training plan tools, but the raw API fallback mitigates these.