Skip to main content
Glama
hadidwirsty

intervals-icu-mcp

by hadidwirsty
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

Related Servers

Alternatives to intervals-icu-mcp

No user-submitted related servers found.

    Related Servers

    • intervals.icu-mcp

      jelmervdm
      A
      license
      A
      quality
      A
      maintenance
      MCP 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-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.
      30 npm
      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
      35
      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

    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

    ActivityMaintained
    ResponsivenessNo issues

    Resources