A
licenseNot graded
qualityD
maintenanceEnables listing, creating, editing, deleting, and scheduling structured workouts (run, cycle, swim, triathlon) on Garmin Connect via natural language.
MIT
Garmin Connect Workouts MCP
by slaat
Related Servers
Alternatives to Garmin Connect Workouts MCP
No user-submitted related servers found.
Related Servers
- AlicenseNot gradedqualityFmaintenanceEnables creation, management, and scheduling of Garmin Connect workouts from natural language descriptions, plus viewing activities, calendar data, and weather information from completed workouts.29MIT
- AlicenseBqualityDmaintenanceEnables creation of Garmin Connect workouts using natural language descriptions. Supports multi-sport workouts with heart rate zones and automatic sync to Garmin devices.313 npm2ISC
- AlicenseAqualityCmaintenanceEnables building and uploading structured workouts to Garmin Connect using YAML or natural language, supporting running, cycling, and strength with zones and circuits.243MIT
- AlicenseNot gradedqualityBmaintenanceEnables AI assistants to read Garmin activities and create/schedule structured workouts and multi-week training plans on Garmin Connect, syncing to the user's watch.1MIT
- AlicenseNot gradedqualityBmaintenanceEnables AI assistants to read Garmin activities and create/schedule structured workouts and multi-week training plans directly on Garmin Connect, syncing to your watch with guided prompts.1MIT
TDQS
A4.6/5.0
Scored across 8 tools
Disambiguation5/5
Each tool targets a distinct action on a distinct resource: CRUD operations on workouts, list/get, schedule, auth status, and login. The only pair that could seem close—check_garmin_auth vs authenticate_garmin—is clearly separated by probe vs. act descriptions.
Naming Consistency5/5
All tools follow a consistent verb_garmin_<noun> pattern (create/list/get/update/delete/schedule_garmin_workout, check/authenticate_garmin). The verb is always first and snake_case is uniform, making the set predictable.
Tool Count5/5
Eight tools is well-scoped for a workout-management MCP: five for CRUD/list, one scheduling action, and two for authentication lifecycle. No redundant or unnecessary tools.
Completeness4/5
The workout lifecycle is fully covered with create, list, get, update, and delete, and schedule and auth handle adjacent needs. Minor gaps exist—there is no unschedule/calendar-view counterpart to schedule_garmin_workout—but agents can accomplish the core workflows without dead ends.
Maintenance
ActivityMaintained
ResponsivenessNo issues