A
licenseNot graded
qualityC
maintenanceEnables Claude to read recent Garmin training and wellness data via intervals.icu and to create, update, or delete structured workouts that sync to Garmin Connect and a Garmin watch.
MIT
garmin-mcp-bridge
Related Servers
Alternatives to garmin-mcp-bridge
No user-submitted related servers found.
Related Servers
- AlicenseNot gradedqualityCmaintenanceEnables Claude to read recent Garmin training and wellness data through intervals.icu and to create, update, or delete structured workouts that sync to a Garmin watch.MIT
- AlicenseNot gradedqualityCmaintenanceEnables Claude to read recent Garmin activities and wellness data through intervals.icu, design structured workouts, and create, update, or delete planned workouts that sync to Garmin Connect and the user's watch.MIT
- AlicenseNot gradedqualityCmaintenanceEnables Claude to read recent Garmin training and wellness data and to create, update, or delete structured workouts through intervals.icu so they sync to Garmin Connect and a user's watch.MIT
- AlicenseNot gradedqualityCmaintenanceEnables Claude to read recent training and wellness data through intervals.icu and create, update, or delete structured workouts that sync to a Garmin watch.MIT
- AlicenseNot gradedqualityCmaintenanceEnables Claude to read recent activities and wellness data (sleep, HRV, resting heart rate) and to create, update, or delete structured planned workouts through intervals.icu, which syncs them to Garmin Connect and onto the user's watch.MIT
TDQS
A4.1/5.0
Scored across 9 tools
Disambiguation5/5
Each tool targets a distinct resource and action: connection health, athlete profile, completed activities (list/detail/streams), daily wellness, and planned workouts (list/create/delete). The list/get/stream progression for activities is clear, and completed vs. planned activities are explicitly separated.
Naming Consistency5/5
All tool names follow a consistent verb_noun snake_case pattern: get_* for singular resources, list_* for collections, create_/delete_* for mutations, and check_connection for the operational check. There is no mixing of naming conventions or vague verbs.
Tool Count5/5
Nine tools is well within the ideal 3-15 range and each serves a distinct step in the coaching workflow: connection check, profile setup, activity review, wellness monitoring, and workout planning. No tool feels redundant or like padding.
Completeness5/5
The surface covers a full coaching loop: read athlete profile, review completed activities with detail and streams, check wellness/autoregulation, and manage planned workouts through list/create/delete. The idempotent create via external_id effectively covers updates, and delete is explicitly wired to list output.
Maintenance
ActivityInactive
ResponsivenessNo issues