Intervals.icu MCP Server
Related Servers
Alternatives to Intervals.icu MCP Server
No user-submitted related servers found.
Related Servers
- AlicenseAqualityBmaintenanceProvides AI assistants with read-only access to an athlete's Intervals.icu training data, including activities, wellness metrics, zones, and planned events, for use with MCP clients like ChatGPT and Claude.15MIT
- AlicenseNot gradedqualityNot gradedmaintenanceEnables Claude to retrieve recent activities and wellness data and to create, update, or delete structured workouts that sync through intervals.icu to Garmin Connect and the user's watch.MIT
- AlicenseAqualityBmaintenanceEnables AI assistants like Claude to read a single user's own Strava account through its API: profile and totals, activities with laps, splits, zones and per-second streams, plus segments, routes, gear and clubs. It is strictly read-only, using the user's own Strava API application and OAuth tokens stored locally, and returns model-friendly, context-sized data.14MIT
- AlicenseBqualityBmaintenanceEnables Claude and other MCP clients to query Garmin Connect health, training, activity, and body data, analyze FIT files, and create structured workouts that sync to a Garmin watch.39MIT
- FlicenseNot gradedqualityDmaintenanceProvides Claude with read-only access to Garmin Connect data including daily health metrics, training status, activity details, and trends through 32 tools.-
- AlicenseNot gradedqualityNot gradedmaintenanceEnables Claude to read recent activities and wellness metrics (sleep, HRV, resting heart rate) and to create, update, or delete structured workouts pushed to an intervals.icu calendar that syncs to Garmin Connect and the user's watch.MIT
TDQS
Scored across 22 tools
Most tools target distinct resource/action pairs, especially the many activity-specific getters. The main overlap is between get_athlete and get_athlete_profile, which could be confused despite descriptions clarifying public versus full athlete data.
Tool names consistently use snake_case verb_noun patterns such as get_event, list_activities, create_event, and update_wellness. The use of search_activities instead of list_activities is semantically appropriate rather than a naming inconsistency.
With 22 tools, the surface is slightly heavy but reasonable for a sports-training API covering activities, streams, intervals, wellness, events, workouts, gear, and routes. Most tools correspond to distinct operations, though some activity-detail tools could feel numerous.
The server covers reading and analyzing activities, wellness, events, workouts, gear, and routes, plus a few write operations. However, notable gaps exist: no update/delete for events, and no create/update/delete for workouts, gear, or routes, limiting lifecycle management.