Skip to main content
Glama
eddmann

intervals-icu-mcp

by eddmann
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Remote

Related Servers

Alternatives to intervals-icu-mcp

No user-submitted related servers found.

    Related Servers

    • 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

    • coros-mcp

      cygnusb
      A
      license
      A
      quality
      A
      maintenance
      A Model Context Protocol (MCP) server that fetches sleep, HRV, and training data from the unofficial Coros API and exposes them to AI assistants like Claude, enabling natural language queries about fitness metrics and workout management.
      26
      122
      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.6/5.0

    Scored across 48 tools

    Disambiguation4/5

    Most tools have clearly distinct purposes, but search_activities and search_activities_full are near-duplicates differing only in response detail. Similarly, get_calendar_events and get_upcoming_workouts overlap somewhat, though descriptions mitigate ambiguity.

    Naming Consistency5/5

    All tools follow a consistent verb_noun snake_case pattern (e.g., get_activity_details, create_event, delete_gear). Minor singular/plural deviations like get_workout_library vs get_workouts_in_folder do not undermine predictability.

    Tool Count2/5

    With 48 tools, the surface far exceeds the typical 3-15 range. Many tools could be consolidated (e.g., histograms, search variants, bulk operations), making the set feel bloated and overwhelming for agents.

    Completeness3/5

    Core activity and calendar management are well covered, but there are notable gaps: no activity upload, no delete for gear reminders, no single-gear retrieval, and no workout creation/editing. Some CRUD cycles are incomplete.

    Maintenance

    ActivityInactive
    ResponsivenessUnresponsive

    Resources