Skip to main content
Glama
jelmervdm

intervals.icu-mcp

by jelmervdm
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Remote

Related Servers

Alternatives to intervals.icu-mcp

No user-submitted related servers found.

    Related Servers

    • intervals-icu-mcp

      hadidwirsty
      A
      license
      A
      quality
      B
      maintenance
      MCP 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.
      19
      25 npm
      1
      MIT

    • intervals-icu-mcp

      eddmann
      A
      license
      A
      quality
      F
      maintenance
      A Model Context Protocol (MCP) server for Intervals.icu integration. Access your training data, wellness metrics, and performance analysis through Claude and other LLMs.
      48
      36
      MIT

    • intervals-mcp

      ale7canna
      A
      license
      Not graded
      quality
      B
      maintenance
      MCP 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.
      13 npm
      MIT

    • intervals-icu-mcp

      andiarenaleandro-ux
      A
      license
      Not graded
      quality
      B
      maintenance
      An 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
    Deploy Server
    One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

    TDQS

    A4.1/5.0

    Scored across 19 tools

    Disambiguation5/5

    Each tool targets a distinct resource and action: activities vs events vs wellness vs workouts are clearly separated. The meta tools (route_tools/call_routed_tool) stand apart from the domain tools, and get/list/update/delete versions are unambiguous.

    Naming Consistency5/5

    All domain tools follow a consistent verb_noun pattern (list_activities, get_event, update_wellness) using snake_case. The two meta tools deviate slightly but are a separate routing layer, not part of the core domain pattern.

    Tool Count4/5

    19 tools is toward the upper end of reasonable for a comprehensive platform API covering athlete profile, activities, events, wellness, and workouts. The count is justified by the breadth of functionality, though it could feel heavy for simple tasks.

    Completeness4/5

    Full CRUD coverage for activities and events, plus read/update for wellness and read-only for workout library. The only notable gap is lack of create/update/delete for structured workouts, but scheduling is handled via events, so the surface is largely complete for the domain.

    Maintenance

    ActivityStale
    ResponsivenessNo issues

    Resources