intervals-mcp
Related Servers
Alternatives to intervals-mcp
No user-submitted related servers found.
Related Servers
- AlicenseNot gradedqualityBmaintenanceAn 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
- AlicenseNot gradedqualityBmaintenanceMCP server that connects Claude and ChatGPT to the Intervals.icu API, enabling retrieval and management of activities, events, wellness data, power curves, and custom items.GPL 3.0
- AlicenseNot gradedqualityCmaintenanceA self-hosted, multi-tenant MCP server that exposes the Intervals.icu API—activities, events, wellness, power curves, gear, and custom items—as MCP tools for Claude.GPL 3.0
- FlicenseNot gradedqualityDmaintenanceProvides MCP servers for Claude to access fitness data from Strava and intervals.icu, enabling natural language queries for activity analysis, advanced training metrics, and wellness tracking.1-
- FlicenseNot gradedqualityCmaintenanceMCP server that gives Claude access to real-time Garmin Connect and Strava data for analyzing training and suggesting sessions.-
- AlicenseAqualityAmaintenanceMCP 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
TDQS
Scored across 9 tools
Each tool has a clearly distinct purpose: connection check, block upload/list/delete/export, fitness trend, power curve, period review, and activity details. The descriptions further clarify any potential overlap, such as upload vs. export or review_period vs. get_activity.
All tool names follow a consistent verb_noun pattern with lowercase and underscores: check_connection, upload_block, list_block, delete_block, get_fitness, get_power_curve, export_block, review_period, get_activity. There are no deviations or mixed conventions.
With 9 tools, the server is well-scoped. Each tool covers a distinct aspect of the workout planning and analysis workflow, and the count is within the ideal 3-15 range.
The tool surface covers the full lifecycle from connection verification and threshold fetching to uploading, listing, deleting, exporting blocks, reviewing period performance, and fetching activity details. A minor gap is the lack of a dedicated tool to retrieve a single workout's planned structure without exporting the entire block, but this is workable.