Intervals.icu MCP Server
Related Servers
Alternatives to Intervals.icu MCP Server
No user-submitted related servers found.
Related Servers
- AlicenseAqualityDmaintenanceMCP server that connects Claude and ChatGPT to the Intervals.icu API, enabling retrieval and management of activities, events, wellness data, power curves, and custom items.21GPL 3.0
- AlicenseAqualityDmaintenanceA Model Context Protocol (MCP) server for Intervals.icu integration. Access your training data, wellness metrics, and performance analysis through Claude and other LLMs.4840MIT
- AlicenseNot gradedqualityCmaintenanceAn MCP server that connects Claude to intervals.icu training data, enabling advanced physiological analysis, activity and wellness management, and conversational insights using proprietary metrics like CCI and HRV correction.MIT
- AlicenseAqualityDmaintenanceAn MCP server that lets Claude plan cycling training in intervals.icu, upload workouts to the calendar, and review planned versus actual outcomes, fitness trends, and power curves.9MIT
- AlicenseAqualityCmaintenanceMCP server for Intervals.icu that enables AI assistants to manage athletic training data, including activities, calendar events, wellness metrics, and workout libraries.19Apache 2.0
- FlicenseNot gradedqualityDmaintenanceProvides MCP servers for Claude to access fitness data from Strava and intervals.icu, enabling natural language queries for activity analysis, advanced training metrics, and wellness tracking.1-
TDQS
Scored across 32 tools
Most tools target clearly distinct resources and actions, and the activity sub-tools (details, streams, intervals, interval stats, best efforts) are differentiated by explicit descriptions. Minor ambiguity remains between add_or_update_event and add_or_update_note, since notes are event-like, and between the several activity-analytics tools.
The set overwhelmingly uses consistent snake_case verb_noun naming such as get_activities, create_custom_item, delete_event, and update_wellness. Minor deviations like get_gear_list and the mixed update vs add_or_update conventions prevent a perfect score.
At 32 tools, the surface is heavy, though the domain is broad and includes activities, events, wellness, custom items, workouts, athlete settings, and gear. Several activity-analysis tools are individually useful, but the overall count is borderline excessive and could benefit from consolidation.
Core lifecycle operations are well covered: activities can be listed, searched, inspected, and annotated; events have create/update/delete/range-delete; wellness supports read and write; and custom items have full CRUD. Gaps remain around workout-library CRUD and gear management beyond listing, but agents can still accomplish most training workflows.