MyWhoosh MCP Server
Click on "Deploy Server".
Wait a few minutes for the server to deploy. Once ready, it will show a "Started" state.
In the chat, type
@followed by the MCP server name and your instructions, e.g., "@MyWhoosh MCP Server Create a 30-minute interval workout"
That's it! The server will respond to your query, and you can continue using it as needed.
Here is a step-by-step guide with screenshots.
MyWhoosh MCP Server

A Model Context Protocol (MCP) server for MyWhoosh that allows you to access the MyWhoosh API directly from your AI provider (like Cursor, Claude Desktop, etc.). Create workouts, manage training sessions, schedule tasks, and more - all through natural language.
Installation
1. Clone the repository
git clone https://github.com/mywhoosh-community/mywhoosh-mcp-server.git
cd mywhoosh-mcp-server2. Install dependencies
npm install3. Build the project
npm run build4. Configure the MCP server
Add the following configuration to your AI provider (e.g., in Cursor under MCP Settings):
{
"mcpServers": {
"mywhoosh-mcp-server": {
"command": "node",
"args": ["PATH_TO_PROJECT\\build\\index.js"],
"env": {
"MYWHOOSH_USERNAME": "${input:mywhoosh-username}",
"MYWHOOSH_PASSWORD": "${input:mywhoosh-password}"
}
}
},
"inputs": [
{
"id": "mywhoosh-username",
"type": "promptString",
"description": "Enter your MyWhoosh username"
},
{
"id": "mywhoosh-password",
"type": "promptString",
"description": "Enter your MyWhoosh password",
"password": true
}
]
}Important: Replace PATH_TO_PROJECT with the absolute path to your cloned repository (e.g., C:\\Users\\admin\\Desktop\\mywhoosh-mcp-server on Windows or /home/user/mywhoosh-mcp-server on Linux/Mac).
Configuration in different AI providers
Cursor
Open the Command Palette (
Ctrl+Shift+P/Cmd+Shift+P)Search for "MCP: Edit Configuration"
Paste the configuration above
Claude Desktop
Edit the configuration file:
Windows:
%APPDATA%\Claude\claude_desktop_config.jsonmacOS:
~/Library/Application Support/Claude/claude_desktop_config.jsonLinux:
~/.config/Claude/claude_desktop_config.json
Related MCP server: MyWhoosh MCP Server
Usage
After installation, you can use the MCP server directly in your AI provider. Examples:
"Create a 30-minute interval workout"
"Show me my scheduled training sessions"
"Change my MyWhoosh settings"
License
ISC License - see LICENSE file for details.
Support
For issues or questions, please create an Issue on GitHub.
Available Tools
47 toolscreateTaskA
Create a calendar task to schedule events, workouts, or free rides.
TASK TYPES:
E_Event: Schedule a group event (use event UUID as taskTypeId)
E_Simple_Workout: Schedule any workout (custom or standard, use workout ID as taskTypeId)
E_FreeRide: Schedule a free ride session
SCHEDULING WORKOUTS:
Use TaskType: "E_Simple_Workout" (for both custom and standard workouts)
Set TaskTypeId to the workout ID (from uploadCustomWorkout or standard workout ID)
TaskStartedTimeEpoc: Unix timestamp when workout should start
TaskEndEpochTime: Unix timestamp when workout should end (start + duration)
Include workout details like Name, Description, TSS
EXAMPLE - Schedule Workout: { "taskType": "E_Simple_Workout", "taskStartedTimeEpoc": 1735200000, "taskTypeId": "176540733485", "taskName": "Interval Power Builder", "taskDescription": "Intensive interval training", "tss": 65 }
Inputs: taskName (required), taskType (required), taskTypeId (required), taskStartedTimeEpoc (required), +9 more.
deleteCustomWorkoutB
Delete a custom workout from MyWhoosh.
Inputs: workoutId (required).
deleteTaskB
Delete a calendar task.
Inputs: taskId (required).
downloadCalendarWorkoutsB
Download calendar workouts for the player.
Inputs: no named parameters.
downloadCustomWorkoutsFromS3A
Download and extract all custom workouts from MyWhoosh S3 bucket. Returns the workout data as parsed JSON objects.
Inputs: no named parameters.
downloadFavoriteWorkoutsA
Download favorite workouts for the player.
Inputs: no named parameters.
getAgeConfigA
Get age-based feature access configuration.
Inputs: no named parameters.
getAllPlayerLeaderboardsA
Get all player arcade leaderboards (Easy, Medium, Hard).
Inputs: no named parameters.
getArcadeLeaderboardB
Get arcade mode leaderboard.
Inputs: no named parameters.
getBundleInfoA
Get shop bundle information (coins, gems packages).
Inputs: no named parameters.
getCalculationsA
Get XP and coin reward calculations and level progression data.
Inputs: currentLevel.
getChallengesA
Get all available challenges and achievements.
Inputs: no named parameters.
getCoachesA
Get list of available coaches.
Inputs: no named parameters.
getConnectappHostA
Get connect app host information for the player.
Inputs: no named parameters.
getControllableBotsB
Get controllable companion bot configurations (Smasher, Climber, Attacker, etc.).
Inputs: no named parameters.
getCustomWorkoutUploadA
Get S3 URL for downloading custom workouts.
Inputs: no named parameters.
getDateRangeTaskListA
Get calendar tasks within a date range.
Inputs: endDate (required), startDate (required).
getDraftingPelotonB
Get drafting peloton configuration with wind effect quadrants.
Inputs: no named parameters.
getEnvironmentByAppVersionA
Get environment type (PROD/DEV) based on app version.
Inputs: platform, appVersion, buildVersion.
getEventsB
Get list of upcoming and current events.
Inputs: sportsMode.
getFitnessNetworkA
Get connected fitness networks (Strava, Garmin, etc.).
Inputs: no named parameters.
getGameTitleDataB
Get game configuration including worlds, version info, and settings.
Inputs: no named parameters.
getGarageItemsB
Get garage/shop items metadata (bikes, equipment, etc.).
Inputs: no named parameters.
getGroupWorkoutsB
Get list of available group workouts.
Inputs: no named parameters.
getJunctionInfoA
Get junction/route information for all available routes.
Inputs: no named parameters.
getMaintenanceStatusA
Get maintenance status and notifications. Does not require authentication.
Inputs: no named parameters.
getMissionProgressB
Get mission challenge progress.
Inputs: no named parameters.
getMissionsB
Get available missions and challenges.
Inputs: no named parameters.
getMyFriendsA
Get list of friends and online friends.
Inputs: no named parameters.
getPacerBotB
Get pacer bot configurations for group rides.
Inputs: no named parameters.
getPendingRideB
Get pending ride data for recovery.
Inputs: no named parameters.
getPlayerAchievementsA
Get player achievement progress and completed achievements.
Inputs: no named parameters.
getPlayerDataB
Get player profile data including stats, equipment, and settings.
Inputs: no named parameters.
getPlayerDistanceB
Get player distance statistics for a number of days.
Inputs: days.
getPlayerGhostRideDataA
Get player ghost ride data for replaying past rides.
Inputs: no named parameters.
getPlayerTrophiesJerseysB
Get player trophies and earned jerseys.
Inputs: no named parameters.
getRoutesA
Get all available routes for free ride mode, organized by world.
Inputs: no named parameters.
getSeasonPassProgressB
Get season pass progress for a specific season.
Inputs: seasonId (required).
getServerTimeA
Get current server time as Unix timestamp.
Inputs: no named parameters.
getTreasureHuntA
Get treasure hunt gate information.
Inputs: no named parameters.
getVODB
Get video on demand content for workouts.
Inputs: no named parameters.
getWorldRoutePlayerCountA
Get current player and bot counts per world and route.
Inputs: no named parameters.
loginA
Authenticate with MyWhoosh and get access tokens. Required before using other endpoints.
Inputs: password (required), username (required), deviceId.
redeemCouponB
Redeem a coupon code for coins or gems.
Inputs: couponCode (required).
registerUserB
Register a new MyWhoosh user account.
Inputs: email (required), dobDay (required), gender (required), height (required), +9 more.
updatePlayerDataB
Update player profile data (equipment, settings, etc.).
Inputs: playerData (required).
uploadCustomWorkoutA
Upload or update custom cycling workouts to MyWhoosh.
CREATING NEW WORKOUTS:
Use a new unique workout ID (timestamp or random large number)
Define all workout properties and steps
UPDATING EXISTING WORKOUTS:
Use the same workout ID as the existing workout
Include all workout properties (changed and unchanged)
Only modify the fields you want to update (e.g., Name, Description, WorkoutStepsArray)
Keep other fields the same as the original workout
WORKOUT STRUCTURE:
Each workout consists of multiple steps (WorkoutStepsArray)
Steps are executed sequentially
Power values are FTP multipliers (0.55 = 55% FTP, 1.0 = 100% FTP, 1.2 = 120% FTP)
Time is in seconds
STEP TYPES:
E_Normal: Steady power interval (use Power field)
E_WarmUp: Ramp up from StartPower to EndPower
E_CoolDown: Ramp down from StartPower to EndPower
E_FreeRide: Free ride with optional message
INTERVALS:
Group steps into intervals by setting the same IntervalId (e.g., 1, 2, 3)
Steps with IntervalId = 0 are not part of an interval
Intervals can repeat (e.g., 3x [5min @ 80% FTP, 3min @ 120% FTP])
EXAMPLE WORKOUT:
5min warmup @ 55% FTP (Id: 1, StepType: E_Normal, Power: 0.55, Time: 300)
10min ramp 55% to 120% FTP (Id: 2, StepType: E_WarmUp, StartPower: 0.55, EndPower: 1.2, Time: 600)
3x [5min @ 80%, 3min @ 120%] (IntervalId: 1 for all 6 steps)
5min cooldown 120% to 55% (Id: 8, StepType: E_CoolDown, StartPower: 1.2, EndPower: 0.55, Time: 300)
Inputs: workouts (required).
Tool Schema Changelog
Recent tool additions, removals, and schema changes observed during successful MCP inspections.
Loading tool schema changelog…
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.
Maintenance
Related MCP Connectors
Connect Intervals.icu to Claude and ChatGPT: read training, plan workouts. Training never stored.
Access approved FITsociety clients, schedules, bookings and coaching data with AI assistants.
Ask your AI about your fitness: activities and data from Garmin, COROS, Strava, GPX and more
Create, personalize and deliver branded workouts and programs from any AI assistant.
Related MCP Servers
- AlicenseAqualityDmaintenanceEnables interaction with Intervals.icu data, including activities, wellness, and calendar events, via natural language.1025 npm1MIT
- -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.-
- AlicenseAqualityBmaintenanceEnables natural-language access to Intervals.icu training data, wellness metrics, activities, events, and workout management through MCP-compatible clients.64MIT
- FlicenseNot gradedqualityAmaintenanceEnables AI assistants to query and create workouts with structured intervals, manage calendars and events, analyze power PRs and CTL/ATL/TSB fitness trends, handle workout libraries, equipment and health metrics through natural language. Uses secure cookie-based authentication stored in the system keyring, so no API approval is required and any account can be set up in minutes.-