Skip to main content
Glama
hhopke

intervals-icu-mcp

by hhopke
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Hybrid

Related Servers

Alternatives to intervals-icu-mcp

  • intervals.mcp

    ryansheppard
    F
    license
    A
    quality
    D
    maintenance
    Enables AI assistants to access and analyze intervals.icu training data including activities, fitness metrics (CTL/ATL/TSB), wellness stats, and calendar events. Supports natural language querying of athletic performance for training insights and workout planning.
    6
    -

  • garmin-connect-mcp

    Nicolasvegam
    A
    license
    A
    quality
    F
    maintenance
    An MCP server that provides access to Garmin Connect fitness, health, and training data through 61 specialized tools. It enables users to query activities, sleep metrics, and performance stats directly within AI clients like Claude or Cursor.
    97
    165 npm
    180
    MIT

  • Intervals.icu MCP Server

    VSidhArt
    F
    license
    A
    quality
    D
    maintenance
    Enables AI assistants to interact with Intervals.icu fitness tracking and wellness data, allowing users to fetch, filter, and group activities or health metrics. It provides structured summaries of workouts and physical well-being through natural language queries.
    4
    -

  • Wahoo MCP Server

    armonge
    A
    license
    B
    quality
    D
    maintenance
    An MCP server for interacting with the Wahoo Cloud API to manage workouts, routes, training plans, and power zones. It enables users to list, retrieve, and create fitness data through secure OAuth 2.0 authentication.
    9
    7
    GPL 3.0

  • Strava MCP Server

    justmytwospence
    A
    license
    A
    quality
    D
    maintenance
    An MCP server that enables interaction with the Strava API v3 to manage fitness activities, athlete profiles, segments, and routes. It supports retrieving detailed performance metrics, exploring geographic data, and managing club information through natural language.
    43 npm
    ISC

Related Servers

  • 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.
    14 npm
    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

  • 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
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.9/5.0

Scored across 64 tools

Disambiguation5/5

Each tool's description explicitly contrasts it with adjacent tools (e.g., 'Different from...', 'Use for... NOT for...'), making even near-duplicates like the three download formats precisely distinguishable. The agent can reliably select the correct tool despite the large set.

Naming Consistency5/5

All tools follow a predictable icu_<verb>_<noun> pattern (get/create/update/delete/bulk_create/apply/duplicate), with only minor conventional variance such as add vs. get for messages. The naming is uniform across all subdomains.

Tool Count1/5

64 tools vastly exceeds any reasonable tool-set size, even for a full-platform integration. The sheer count forces an agent to parse an enormous list and would be better served by splitting into multiple focused MCP servers.

Completeness4/5

The tool surface covers activities, workouts, calendar, athlete, wellness, gear, and customizations almost exhaustively, including batch operations and historical backfills. Minor gaps exist (e.g., no delete_activity, no delete_workout_folder), but these are workable.

Maintenance

ActivityActive
ResponsivenessSlow

Resources