Skip to main content
Glama
santibacat

intervals-mcp

by santibacat
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python

Related Servers

Alternatives to intervals-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.
      9
      MIT

    • catence

      rifusaki
      A
      license
      B
      quality
      A
      maintenance
      MCP server for local fitness-data extraction and analysis from Garmin Connect, Intervals.icu, and Strava. Provides read-only analytical tools over DuckDB and targeted Strava enrichment.
      35
      425
      AGPL 3.0

    • 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

      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
      15
      1
      MIT
    Deploy Server
    RayrunBuild, deploy, and operate MCP servers without becoming an infrastructure team.ray.runAd

    TDQS

    B3.4/5.0

    Scored across 14 tools

    Disambiguation5/5

    Each tool addresses a distinct operation: draft plan lifecycle (create, clone, rename, get, list, schedule, unschedule), workout management (add, update), athlete context (profile, personal context, fact), and performance data. No two tools have overlapping purposes.

    Naming Consistency5/5

    All tool names follow a consistent verb_noun pattern using snake_case (e.g., rename_draft_plan, get_training_context, set_personal_fact). The convention is uniform across all 14 tools.

    Tool Count5/5

    14 tools cover the domain of training plan management (library plans, workouts, scheduling, athlete data, performance curves) without being excessive or too sparse. Each tool has a clear role.

    Completeness3/5

    Core workflows for draft plans are present (create, read, update via rename/add_workout/update_workout, schedule/unschedule), but missing delete operations (no delete_draft_plan or remove_workout_from_draft). This gap could cause issues if agents need to remove plans or workouts.

    Maintenance

    ActivitySlowing
    ResponsivenessNo issues

    Resources