Skip to main content
Glama
oscarantxo-web

Intervals.icu MCP Server

by oscarantxo-web
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Remote

Related Servers

Alternatives to Intervals.icu MCP Server

No user-submitted related servers found.

    Related Servers

    • 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

    • 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-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
      12 npm
      1
      MIT

    • fitness-mcp-server

      ewongz
      F
      license
      Not graded
      quality
      D
      maintenance
      Provides 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
      -
    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.8/5.0

    Scored across 21 tools

    Disambiguation5/5

    Each tool maps to a distinct resource and action: activities, events, notes, custom items, wellness, gear, and profile are clearly separated. Within the activity group, list/detail/interval/stream/message endpoints are well differentiated by their descriptions.

    Naming Consistency4/5

    Most tools follow a predictable verb_noun pattern like get_activities, create_custom_item, delete_event, and add_activity_message. Minor inconsistencies exist: icu_get_athlete_profile uses an unusual prefix, and add_or_update is used for events/notes while create/update is used for custom items.

    Tool Count4/5

    21 tools is above the typical 3-15 sweet spot, but the count maps naturally to multiple distinct Intervals.icu domains: activities, events/calendar, custom items, wellness, gear, and athlete profile. It feels slightly heavy rather than bloated or redundant.

    Completeness4/5

    The set covers the main workflows well: reading activity data, managing events and notes, full CRUD for custom items, and pulling wellness, gear, and profile information. Minor gaps exist—no activity write/delete operations, no note deletion, and no wellness or gear updates—but these are workable for a mostly read-oriented integration.

    Maintenance

    ActivityMaintained
    ResponsivenessNo issues

    Resources