Futureweb Intervals MCP
Related Servers
Alternatives to Futureweb Intervals MCP
No user-submitted related servers found.
Related Servers
- AlicenseNot gradedqualityBmaintenanceMCP 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 npmMIT
- AlicenseAqualityCmaintenanceMCP server for Intervals.icu that enables AI assistants to manage athletic training data, including activities, calendar events, wellness metrics, and workout libraries.19Apache 2.0
- AlicenseBqualityAmaintenanceMCP 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.35759 npm1AGPL 3.0
- AlicenseAqualityAmaintenanceRead/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.701,969 PyPI121MIT
- AlicenseBqualityBmaintenancePrivacy-first MCP server for Strava activities, streams, routes and training data.29295 npm3MIT
- FlicenseNot gradedqualityBmaintenancePrivacy-focused Garmin Connect MCP server for triathlon training, enabling analysis of health metrics, activities, training load, and structured workout creation.-
TDQS
Scored across 59 tools
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.
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.
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.
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.