Intervals.icu MCP Server
Related Servers
Alternatives to Intervals.icu MCP Server
No user-submitted related servers found.
Related Servers
- AlicenseNot gradedqualityCmaintenanceEnables Claude and ChatGPT to access and manage Intervals.icu data, including activities, events, wellness metrics, power curves, and custom items through natural language.GPL 3.0
- AlicenseNot gradedqualityBmaintenanceConnects to Intervals.icu to let users query training data, create workouts, manage calendar events, and coach athletes through natural language in Claude Desktop.9MIT
- AlicenseAqualityCmaintenanceConnects Claude with the Intervals.icu API to retrieve fitness data including activities, workouts, wellness metrics, and training events.10345GPL 3.0
- AlicenseNot gradedqualityBmaintenanceEnables Claude AI to access and manage intervals.icu training data, including workouts, wellness, and fitness trends, through natural language conversation.MIT
- FlicenseAqualityDmaintenanceEnables AI assistants to access and analyze intervals.icu training data including activities, fitness metrics (CTL/ATL/TSB), wellness stats, and calendar events. Supports natural language querying of athletic performance for training insights and workout planning.6-
- FlicenseAqualityDmaintenanceEnables AI assistants to interact with Intervals.icu fitness tracking and wellness data, allowing users to fetch, filter, and group activities or health metrics. It provides structured summaries of workouts and physical well-being through natural language queries.4-
TDQS
Scored across 21 tools
Most tools target distinct resources or distinct data views (list vs details vs streams vs intervals), so selection is usually clear. The main potential confusions are get_activity_details vs get_activity_raw and add_or_update_event vs add_or_update_note, but the descriptions distinguish these adequately.
The tool names largely follow a consistent verb_noun pattern: get_, create_, update_, delete_, and add_or_update_. Minor deviations like add_activity_message instead of add_or_update_activity_message and get_gear_list instead of get_gears are acceptable but keep it from being perfectly uniform.
21 tools is on the higher side, but the server covers a broad API surface: activities, events, notes, custom items, gear, wellness, and power curves. The included diagnostic tool get_activity_raw adds some bloat, but overall the count is reasonable for the domain.
The tool set covers the main lifecycle needs for activities, events, and custom items, with good read/write coverage. Minor gaps exist, such as no delete_note, no activity update/delete, and read-only gear access, but agents can complete most typical workflows without dead ends.