garmin-connect-mcp
Related Servers
Alternatives to garmin-connect-mcp
No user-submitted related servers found.
Related Servers
- FlicenseNot gradedqualityBmaintenanceEnables AI assistants to access and manage Garmin Connect data through 95 tools, including real-time activities, metrics, and downloads.-
- AlicenseCqualityBmaintenanceEnables access to Garmin Connect fitness data through 39 fine-grained tools covering body, heart, sleep, stress, activity, steps, hydration, devices, nutrition, goals, and user profile.403MIT
- AlicenseAqualityBmaintenanceEnables MCP clients to read the user's own Garmin data—including activities, sleep, HRV, Body Battery, stress, steps, heart rate, and weight—through Garmin's official Personal API, with all 26 endpoints exposed as read-only tools.2651 npmMIT
- AlicenseCqualityDmaintenanceEnables users to access and analyze Garmin China fitness and health data, including activities, recovery, trends, and weather heat stress, through 55 tools.55MIT
- 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
- AlicenseAqualityCmaintenanceEnables MCP clients to read a user's own Garmin data—including activities, sleep, HRV, Body Battery, stress, steps, heart rate, weight, and more—through 26 read-only tools backed by Garmin's Personal API.2651 npmMIT
TDQS
Scored across 10 tools
Each tool targets a distinct resource+action: searching activities, fetching one activity, downloading its file, daily multi-metric health, single-metric trends, cycle tracking, HR zones, profile, and auto-detected wellness activities. The only soft overlaps are garmin_get_daily_health vs garmin_get_health_trend (different axes, explicitly cross-referenced) and garmin_get_raw, which duplicates everything but is clearly framed as a last-resort escape hatch.
All ten tools use the same garmin_ prefix with snake_case verb_noun structure (garmin_search_activities, garmin_get_activity, garmin_download_activity_file). Even the generic escape hatch follows the pattern as garmin_get_raw, so the convention is uniform throughout.
Ten tools is squarely in the well-scoped range, and each covers a distinct slice of Garmin Connect data (activities, health, trends, cycle, zones, profile). Nothing feels redundant or padded; garmin_get_raw adds breadth without a proliferation of narrow tools.
The surface covers the read lifecycle well: discovery, detail, raw file download, per-day and cross-day health metrics, plus user context needed to interpret units. Gaps are mostly write-side (no weight/activity/food logging, no workout upload), which is a reasonable scope for a Garmin data reader but leaves some obvious operations unreachable.