TrainingPeaks-MCP
Related Servers
Alternatives to TrainingPeaks-MCP
No user-submitted related servers found.
Related Servers
- AlicenseAqualityDmaintenanceA Model Context Protocol server for TrainingPeaks with an analytics focus — enabling real-time querying of training data, performance trends, CTL/ATL/TSB analysis, and training load optimization through Claude Desktop.14MIT
- AlicenseAqualityBmaintenanceLocal MCP server that connects Claude Desktop with Garmin and Apple Health data to read training and recovery, estimate heart rate and pace zones, analyze performance, and create structured workouts.22MIT
- 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
- FlicenseNot gradedqualityCmaintenanceMCP server for TrainingPeaks that reads workouts, fitness metrics (CTL/ATL/TSB), and health data, and creates/updates/deletes planned workouts. Enables AI-powered training plan management and automated adjustment based on performance, fatigue, and injury.-
- 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
- AlicenseAqualityFmaintenanceA Model Context Protocol (MCP) server for Intervals.icu integration. Access your training data, wellness metrics, and performance analysis through Claude and other LLMs.4835MIT
TDQS
Scored across 85 tools
Most tools target a distinct resource and action, and descriptions clearly separate overlapping concepts like workout notes vs. comments and cardio vs. strength workouts. A few pairs (tp_get_workout vs. tp_get_strength_workout, tp_get_workout_note vs. tp_get_note_comments) require careful reading, but no tools appear to do exactly the same thing.
The vast majority follow a consistent tp_verb_noun snake_case pattern (e.g., tp_get_workouts, tp_update_ftp, tp_delete_equipment). Minor exceptions like tp_auth_status and tp_log_metrics break the pattern slightly, but the overall convention is highly predictable.
85 tools is far beyond the typical well-scoped MCP server and even for a broad platform this creates a significant navigation burden. While each tool may have a legitimate purpose, the sheer number makes it difficult for an agent to efficiently discover and select the right tool.
The tool surface is extremely comprehensive, covering workouts, strength training, events, notes, equipment, libraries, groups, metrics, and more. Minor gaps exist, such as no training plan creation/editing and no per-template library deletion, but these are workable and do not create dead ends for most coaching workflows.