garmin-connect-mcp
Related Servers
Alternatives to garmin-connect-mcp
No user-submitted related servers found.
Related Servers
- AlicenseBqualityBmaintenanceProvides local, Keychain-secured access to all 26 Garmin Connect Personal API GET endpoints plus 8 summary tools. Enables users to query sleep, HRV, Body Battery, activities, profile, weight, and other connected health data through their own Personal API key.341Apache 2.0
- AlicenseBqualityBmaintenanceEnables Claude or any MCP client to read your own Garmin Connect health data — sleep, HRV, heart rate, stress, Body Battery, weight, nutrition, and activities — through Garmin's official, key-based read-only Personal API with no password login or scraping. Activity tools pull the original FIT files to provide laps, computed splits, time in heart-rate zones, and session stats.25Apache 2.0
- AlicenseAqualityBmaintenanceUnofficial read-only Garmin Connect data: sleep, HRV, heart rate, stress, recovery analysis.13MIT
- FlicenseNot gradedqualityDmaintenanceEnables querying your Garmin Connect data including recent activities, detailed metrics, and daily stats through natural language.-
- AlicenseAqualityBmaintenanceEnables ChatGPT and compatible AI clients to query read-only Garmin Connect data—including sleep, HRV, heart rate, Body Battery, wellness metrics, and activities—through a hosted OAuth-backed MCP connection using a personal API key.2151MIT
- AlicenseNot gradedqualityBmaintenanceConnects Garmin Connect to AI assistants, answering questions about training, sleep, HRV and recovery with metrics computed in code rather than guessed from raw JSON. Queries daily readiness, training load, activity FIT analysis and personal records through a self-hosted Cloudflare Worker with OAuth.16 npm8MIT
TDQS
Scored across 9 tools
Most tools have clearly distinct purposes: list_activities vs get_activity, get_training_summary, get_body_composition, get_nutrition, and get_profile are easy to tell apart. The main overlap is get_recovery vs get_day_detail, since both surface sleep, HRV, and Body Battery data, though the range-vs-single-day distinction helps. garmin_api_get is an intentional escape hatch with explicit usage guidance.
Eight of nine tools follow a consistent snake_case verb_noun pattern using get_ or list_ prefixes. garmin_api_get is a minor deviation, but it still uses snake_case and signals its special escape-hatch role. Overall naming is predictable and readable.
Nine tools is well-scoped for a read-only Garmin Connect data server. Each tool covers a distinct data area—recovery, day detail, activities, training, body composition, nutrition, profile—and the escape hatch adds flexibility without bloating the set. No tool feels redundant or superfluous.
The surface covers the core health/fitness domains: recovery, sleep, HRV, activities, training load, body composition, nutrition, and profile. Minor gaps exist for less common metrics like SpO2, fitness age, and goals, but garmin_api_get provides a documented escape hatch for those cases. This is broadly complete for typical agent workflows.