io.github.hhopke/intervals-icu-mcp

Fetch wellness records over a RANGE of recent days (default last 7). Use for trends, weekly summaries, "how has my sleep been this week?", recovery curves. For PMC/fitness chart CTL/ATL/TSB series use icu_get_fitness_chart. For a single specific date use icu_get_wellness_for_date instead — this tool always returns a multi-day list.

Fetch the wellness record for ONE specific date. Use when the user names a date — "show my HRV for Monday", "wellness on 2026-03-15", "how did I sleep last Thursday?". For ranges, weeks, or trends use icu_get_wellness_data.

List all workout-library folders + training plans the athlete has access to (personal, shared, and followed plans). Each folder ID can be passed to icu_get_workouts_in_folder to see its contents, or to icu_apply_training_plan to schedule it onto the calendar.

List the workouts stored in one specific library folder or training plan — name, type, structure, training load, intensity factor.

List the athletes this account can access — the caller plus anyone they follow or coach. Call this FIRST whenever a request concerns someone other than the default athlete, to resolve a name to the athlete_id that other tools take. Returns each athlete's access level, so you know before calling whether a write will be permitted, plus any tags and a short preview of the athlete notes. Entries with notes_truncated=true have longer notes; icu_get_athlete_profile returns the full text.

Search activities by name or tag, returning a LIGHT result list — id, name, type, date, distance, time only. Use this first for "find my X" queries. Only escalate to search_activities_full when you specifically need power, HR, training load, or intensity-factor data on the matches (heavier payload).

Search activities by name or tag, returning FULL Activity objects with power, HR, training load, intensity factor, normalized power, weather — every metric per result. Heavy payload. Use only when the lighter search_activities won't tell you what you need (e.g. "find my threshold rides with NP above 250W").

Search intervals ACROSS ALL the athlete's activities (cross-activity). Different from icu_get_activity_intervals (single-activity). Use to track progress on a workout type ("all my threshold intervals over the last year") or find comparable historical sessions. Returns the activities containing matching intervals, each with an `interval_summary` like "2x 8m 162w" (reps x duration at target).

Update an existing activity's metadata (name, type, distance, sub-type, RPE, etc.). Only fields you pass are sent; everything else stays unchanged. Strava-imported activities cannot be updated. Moving, elapsed and recording time cannot be changed after an activity exists (neither here nor in the web UI); they can only be set when a manual activity is created. Keys passed via `fields` are sent as-is and are not echoed back in the response.

REPLACE the text of an existing note on an activity (edit, not add). Use when the user wants to fix or rewrite a note they already left: "correct my note on that ride", "change the comment to say...". Only the author's own notes can be changed. Returns the old and the new text — the old text is not recoverable otherwise. To post an additional note use icu_add_activity_message.

Upload raw time-series streams (power, HR, cadence, etc.) onto an existing activity. Destructive — overwrites existing stream data. Accepts JSON array or CSV. Different from get_activity_streams (READ).

REPLACE the free-text notes kept on an athlete's own record — not an activity comment or a calendar note. Use for standing context about the athlete: "note on my profile that I'm injured", "update my athlete notes". The whole text is overwritten, so to add to existing notes read them first with icu_get_athlete_profile and send the combined text. For a comment on one activity use icu_add_activity_message; for a dated calendar note use icu_create_event.

Modify an existing custom chart/field/zones/panel. Use when the user wants to change one of their existing customizations: "rename my custom field", "make this chart public". Usually need icu_get_custom_items first to find the right `item_id`. Only fields you pass are sent — others are left unchanged. For `content` schema, see intervals-icu://custom-item-schemas.

Update an existing calendar event. Only fields you pass are sent — other fields remain unchanged. For category and training_availability semantics, see intervals-icu://event-categories. For WORKOUT `description` syntax, see intervals-icu://workout-syntax.

Update an existing gear item. Only fields you pass are sent.

Update an existing gear maintenance reminder. Only fields you pass are sent.

Update sport settings: FTP, FTHR, pace/swim thresholds, or explicit HR/power zones. Explicit zones replace the threshold-derived ones (e.g. to match a lab test). Changes apply from now on; past activities keep the zones they were analysed with. To re-zone past activities, tell the user to use Update zones in the Intervals.icu activity list view (not in the API).

Upsert wellness data for ONE specific date — creates the record if missing, otherwise updates the fields you pass. Only provided fields are sent. Subjective scales (fatigue, soreness, stress, mood, motivation, injury) are 1-5. Pass `locked=True` to stop device sync from overwriting manual entries. Writes to the authenticated athlete unless athlete_id names a managed athlete.

Change fields on an EXISTING library workout — only the fields you pass are sent. To save a new workout use icu_create_workout. This edits the library workout only; calendar events are separate records changed with icu_update_event.