io.github.hhopke/intervals-icu-mcp
Related Servers
Alternatives to io.github.hhopke/intervals-icu-mcp
No user-submitted related servers found.
Related Servers
- AlicenseNot gradedqualityFmaintenanceIntegrates Intervals.icu training data, wellness records, workouts, and calendar events with AI assistants through MCP tools.14 npm1MIT
- 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
- AlicenseAqualityAmaintenanceMCP 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
- AlicenseAqualityBmaintenanceMCP server that connects AI agents to Intervals.icu, enabling access to training data such as activities, wellness metrics, calendar events, gear, power curves, and custom items. Includes a running coach AI template for automated post-session analysis.1912 npm1MIT
- FlicenseNot gradedqualityCmaintenanceEnables interaction with the Intervals.icu API, providing tools to manage workouts, messages, wellness data, and more through any MCP client.3-
- AlicenseAqualityDmaintenanceEnables interaction with Intervals.icu data, including activities, wellness, and calendar events, via natural language.1016 npm1MIT
TDQS
Scored across 64 tools
Each tool has a clearly distinct purpose, and the descriptions explicitly differentiate them from similar ones (e.g., histograms vs curves, single vs bulk operations). The thorough 'Different from X' notes eliminate ambiguity, making misselection unlikely despite the large number.
All tools follow a uniform `icu_verb_noun` pattern (e.g., icu_get_power_curves, icu_create_event, icu_bulk_delete_events). The prefix is consistent, verbs are clear and standard (get/create/update/delete), and no mixed conventions are present.
64 tools is extreme for an MCP server, far exceeding the 25+ threshold for 'too many'. Even for a broad training platform, this overwhelms an agent's tool selection and adds significant token overhead. Many operations could be combined or parameterized (e.g., single vs bulk variants).
The tool set covers the major domains—activities, workouts, calendar, gear, wellness, fitness, settings, and custom items—with CRUD-like operations. Minor gaps exist (no delete for custom items or sport settings, no single activity creation, no file upload), but these are edge cases that agents can work around.