A
licenseA
qualityA
maintenanceMCP server for Intervals.icu that enables AI assistants to manage athletic training data, including activities, calendar events, wellness metrics, and workout libraries.
19
Apache 2.0
intervals-icu-mcp
by hadidwirsty
Related Servers
Alternatives to intervals-icu-mcp
No user-submitted related servers found.
Related Servers
- AlicenseAqualityBmaintenanceMCP 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
- AlicenseNot gradedqualityBmaintenanceMCP server for intervals.icu that reads training data (activities, wellness, calendar) and creates structured workouts on the calendar, which are pushed to devices like Garmin, Wahoo, Zwift, Coros, Suunto via the official API.12 npmMIT
- AlicenseNot gradedqualityFmaintenanceIntegrates Intervals.icu training data, wellness records, workouts, and calendar events with AI assistants through MCP tools.12 npm1MIT
- AlicenseAqualityBmaintenanceEnables natural-language access to Intervals.icu training data, wellness metrics, activities, events, and workout management through MCP-compatible clients.64MIT
- AlicenseAqualityFmaintenanceA Model Context Protocol (MCP) server for Intervals.icu integration. Access your training data, wellness metrics, and performance analysis through Claude and other LLMs.4836MIT
TDQS
A3.7/5.0
Scored across 19 tools
Disambiguation5/5
Each tool targets a distinct resource and action. Activity-related tools are separated by data granularity (list, details, intervals, streams, messages), and event/custom item tools follow clear CRUD patterns. No two tools appear to serve the same purpose.
Naming Consistency5/5
All tools use a consistent verb_noun pattern in snake_case. Retrieval uses get_, creation uses add_/create_, updates use update_/add_or_update_, and deletion uses delete_. Minor variation like add_or_update_ is predictable.
Tool Count4/5
At 19 tools, this is above the ideal 3-15 range but appropriate for the broad scope covering activities, events, wellness, gear, power curves, and custom items. The tools are grouped by domain and each is justified; still, a few could be consolidated, so not a perfect 5.
Completeness4/5
Core workflows are well covered: activities have read and message addition, events have full CRUD, and custom items have full CRUD. Gaps include no activity update/delete, no gear management, and no wellness update, but these may be outside the API's intended scope or rare needs.
Maintenance
ActivityActive
ResponsivenessNo issues