mywhoosh-mcp
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| MYWHOOSH_TZ | No | Time zone used for scheduling. | Europe/Berlin |
| MYWHOOSH_PASSWORD | No | MyWhoosh account password. Can be provided via environment variable instead of using the macOS Keychain. | |
| MYWHOOSH_USERNAME | No | MyWhoosh account username/email. Can be provided via environment variable instead of using the macOS Keychain. |
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
Create, list, delete and schedule MyWhoosh custom cycling workouts. Power is in % FTP. Workouts appear in the MyWhoosh app under Custom Workouts after a resync/restart. Calls may be issued in parallel; the server serializes writes itself.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {
"listChanged": false
} |
| prompts | {
"listChanged": false
} |
| resources | {
"subscribe": false,
"listChanged": false
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| mywhoosh_create_workoutA | Create a custom cycling workout in MyWhoosh. blocks are executed in order. Power in % FTP (e.g. 90 = 90% FTP). erg_mode=True: trainer holds the target power (ERG). False: rider controls resistance. ftp_watts is optional and only used to compute kJ. Text (name, description, messages) is transliterated to ASCII (ö->oe, ß->ss, – -> -), because MyWhoosh drops all non-ASCII characters. Example blocks: {"type":"warmup","duration_s":600,"start_power":50,"end_power":75} {"type":"interval","duration_s":240,"power":105,"repeat":4,"rest_duration_s":180,"rest_power":55} {"type":"steady","duration_s":1200,"power":70,"cadence":90} {"type":"cooldown","duration_s":300,"start_power":65,"end_power":45} |
| mywhoosh_update_workoutA | Replace an existing custom workout in place (same id), e.g. to fix a typo or change targets. Same arguments as mywhoosh_create_workout plus workout_id; the whole workout is replaced. The id stays, so calendar entries keep pointing at it. Calendar entries keep their own copy of name and TSS, which is not updated: re-schedule if those must change. |
| mywhoosh_delete_workoutA | Delete a custom cycling workout by id (see mywhoosh_list_workouts). If the workout is used by a training plan, nothing is deleted unless force=True. |
| mywhoosh_list_workoutsA | List custom cycling workouts stored in MyWhoosh (newest first). include_steps adds a compact per-step breakdown. name_contains filters case-insensitively. |
| mywhoosh_schedule_workoutA | Put a custom workout (id from mywhoosh_list_workouts/mywhoosh_create_workout) on the MyWhoosh calendar. date: YYYY-MM-DD, start_time: HH:MM, both local time (Europe/Berlin). |
| mywhoosh_list_scheduled_workoutsA | List MyWhoosh calendar entries between two dates (YYYY-MM-DD, inclusive, local time). |
| mywhoosh_unschedule_workoutA | Remove a calendar entry by task_id (from mywhoosh_list_scheduled_workouts). The workout itself stays. |
| mywhoosh_get_profileA | FTP, weight, height and best power values stored in the MyWhoosh profile. Workout targets in MyWhoosh are % of this FTP, so check it before planning watt targets. |
| mywhoosh_set_ftpA | Set the cycling FTP in the MyWhoosh profile (watts, 50-600). Rewrites the profile with only FtpPlayer changed and verifies that nothing else changed. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 9 tools
Each tool maps to a distinct resource+action: workout CRUD, calendar scheduling, and profile FTP access are cleanly separated. create_workout and update_workout are distinguished by the explicit 'replace in place' wording and the workout_id parameter.
All nine tools follow the same mywhoosh_verb_noun snake_case pattern (mywhoosh_create_workout, mywhoosh_list_scheduled_workouts, mywhoosh_set_ftp). No mixed conventions or vague verbs.
Nine tools is well within the ideal 3-15 range and every tool covers a real operation. Nothing feels like padding or an accidental duplicate.
Workout lifecycle (create/update/delete/list) and calendar (schedule/list/unschedule) are fully covered, with profile read/write for FTP. Minor gaps: no get_workout-by-id (only list with filters), and profile writes are limited to FTP (no weight/height update).