MyWhoosh MCP Server
Related Servers
Alternatives to MyWhoosh MCP Server
No user-submitted related servers found.
Related Servers
- -licenseNot gradedqualityNot gradedmaintenanceEnables AI assistants to interact with the MyWhoosh API using natural language, allowing users to create workouts, manage training sessions, schedule tasks, and adjust settings.-
- AlicenseAqualityDmaintenanceEnables interaction with Intervals.icu data, including activities, wellness, and calendar events, via natural language.1018 npm1MIT
- AlicenseNot gradedqualityFmaintenanceEnables creation, management, and scheduling of Garmin Connect workouts from natural language descriptions, plus viewing activities, calendar data, and weather information from completed workouts.28MIT
- AlicenseNot gradedqualityCmaintenanceEnables querying workouts, fitness metrics (CTL/ATL/TSB), and power personal records from TrainingPeaks using natural language.2MIT
- AlicenseAqualityAmaintenanceEnables users to describe workouts in plain English and have them created as structured Garmin Connect workouts with pace, HR, power, cadence targets, and repeat blocks. Also provides full workout lifecycle management including listing, updating, deleting, and scheduling to the calendar.28112 npmMIT

Orchestra MCP Serverofficial
FlicenseNot gradedqualityAmaintenanceEnables interaction with the Orchestra API for managing pipelines, runs, logs, and artifacts through natural language.-
TDQS
Scored across 47 tools
Multiple tools have overlapping purposes, such as getAllPlayerLeaderboards vs getArcadeLeaderboard, getChallenges vs getMissions vs getMissionProgress, and getCustomWorkoutUpload vs downloadCustomWorkoutsFromS3. These similar names and descriptions can easily confuse an agent.
The naming follows a consistent camelCase verb_noun pattern, with most tools using 'get' as the verb. Minor deviations like 'login' (verb only) and 'downloadCustomWorkoutsFromS3' (extra qualifier) exist but do not obscure the overall predictable style.
With 47 tools, the server is heavily overloaded. This far exceeds the typical well-scoped range of 3-15 tools and makes it difficult for an agent to navigate, even though the domain is broad.
The surface covers major areas like authentication, workouts, tasks, events, and shop, but lacks obvious lifecycle operations such as updating tasks (only create/delete) and has no direct single-workout retrieval (only bulk download methods). These gaps require agent workarounds but are not fatal.