Skip to main content
Glama
Futureweb Intervals MCP

Futureweb Intervals MCP

Related Servers

Alternatives to Futureweb Intervals MCP

No user-submitted related servers found.

    Related Servers

    • 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.
      44 npm
      MIT
    • A
      license
      A
      quality
      C
      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
    • 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
      759 npm
      1
      AGPL 3.0
    • A
      license
      A
      quality
      A
      maintenance
      Read/write MCP server for Intervals.icu — 51 tools spanning activities, streams, wellness, calendar, gear, and sport zones, plus structured workout generation with a built-in syntax reference for cycling, running, and swimming.
      70
      1,969 PyPI
      121
      MIT
    • F
      license
      Not graded
      quality
      B
      maintenance
      Privacy-focused Garmin Connect MCP server for triathlon training, enabling analysis of health metrics, activities, training load, and structured workout creation.
      -

    TDQS

    A3.8/5.0

    Scored across 59 tools

    Disambiguation3/5

    Several analytics tools overlap in scope (e.g., get_activity_report vs get_activity_details, get_training_summary vs get_weekly_summary, get_durability vs get_power_hr_efficiency), so choosing correctly requires reading the detailed cross-references. The descriptions do help, but the set is not cleanly separated.

    Naming Consistency5/5

    Nearly all tools follow a predictable snake_case verb_noun or verb_topic pattern (get_*, add_*, update_*, compare_*, analyze_*). Minor compound forms like add_or_update_event are still clear and consistent with the overall convention.

    Tool Count1/5

    With 59 tools, the server is far beyond the typical 3-15 scoped set and falls into the extreme-mismatch range of 50+ tools. Even for a broad training platform, many read/analysis variants could be consolidated without losing coverage.

    Completeness4/5

    Core lifecycle coverage is strong across activities, wellness, calendar events, notes, messages, workout library writes, and extensive analysis. However, gaps remain, including the referenced but absent update_sport_settings, no update/delete for library workouts, and read-only-only gear/custom-item administration.

    Maintenance

    ActivityActive
    ResponsivenessNo recent community issues