garmin-mcp
Related Servers
Alternatives to garmin-mcp
No user-submitted related servers found.
Related Servers
- FlicenseNot gradedqualityDmaintenanceProvides Claude with read-only access to Garmin Connect data including daily health metrics, training status, activity details, and trends through 32 tools.-
- FlicenseAqualityBmaintenanceExposes your Garmin Connect data (activities, sleep, recovery, training status) to Claude in read-only mode.7-
- AlicenseBqualityAmaintenanceEnables users to analyze their own Garmin Connect data—activities, sleep, HRV, Body Battery, training readiness—directly inside Claude Desktop.132MIT
- AlicenseAqualityDmaintenanceEnables Claude Desktop to access and analyze Garmin wearable health data including sleep, HRV, Body Battery, and activity metrics. Users can query their health trends, track recovery, and generate interactive HTML dashboards using natural language.96MIT
- AlicenseBqualityAmaintenanceConnects Claude Desktop to Garmin Connect, enabling natural language queries of fitness activity data, health metrics, sleep analysis, workout management, and device information with 94 available tools.1101MIT
- FlicenseNot gradedqualityCmaintenanceConnects Garmin watch data to Claude Desktop, allowing users to ask natural language questions about their health and activity data from Garmin Connect.-
TDQS
Scored across 28 tools
Most get_* tools target distinct metrics (sleep, HRV, body battery, stress, etc.), but some overlap exists: get_sleep includes overnight HRV, and get_daily_briefing explicitly fuses six other tools. Descriptions are detailed enough to disambiguate, but an agent could hesitate between the composite and individual tools.
All tools follow a consistent verb_noun pattern in snake_case: get_* for read operations, preview_*/create_* for workout creation, delete_workout, schedule_workout/unschedule_workout. Nearly every tool name clearly indicates its action and resource, with no mixed conventions.
With 28 tools, the server exceeds the 25+ threshold for 'too many'. While the Garmin domain is broad, many tools could be consolidated (e.g., get_daily_briefing already combines six), and the count feels heavy for an agent to navigate efficiently.
The surface covers a wide range of health metrics and workout CRUD (preview, create, list, delete, schedule/unschedule). Minor gaps exist: no workout update (only delete and recreate) and no detailed view of a single workout template's steps, but core workflows are well-supported.