Intervals.icu MCP server Let your AI agent run your Intervals.icu training.

ToolWhat it doesAccess

• list_activities Completed activities in a date range with type, duration, distance and training load, newest first. read

  Returns the activities Intervals.icu shows for your account between two dates, newest first. Each row has the id, name, sport type, start time, moving time, distance, training load and average power or heart rate where the activity has them. Strava-sourced activities show date and id only, because Intervals.icu may not pass their data on. Pass an id to get_activity for the full detail.

  MCP callintervals_icu_read → list_activities

  REST endpointGET https://cotlet.dev/api/v1/intervals-icu/activities

  Parameters

  Parameters: list_activities

  Name	Type	Description
  oldest date required	date	First day to include.
  newest date required	date	Last day to include.
  type string	string	Only this sport, e.g. Ride, Run, Swim, WeightTraining.

  Example input

  {
    "oldest": "2026-10-01",
    "newest": "2026-10-01"
  }

  Example response

  {
    "activities": [
      {
        "id": "i88120456",
        "name": "Sunday long ride",
        "type": "Ride",
        "start_date_local": "2026-11-01T08:42:10",
        "moving_time": 12840,
        "distance": 82400,
        "icu_training_load": 124,
        "average_watts": 168
      },
      {
        "id": "i88104311",
        "name": "Easy spin",
        "type": "Ride",
        "start_date_local": "2026-10-30T17:05:00",
        "moving_time": 2700,
        "distance": 12100,
        "icu_training_load": 58,
        "average_watts": 132
      }
    ]
  }

• get_activity One activity with its detected intervals, notes, RPE and feel. read

  Returns one activity by id: summary figures, the intervals Intervals.icu detected (duration, average power and heart rate), the description, RPE and feel. Intervals come in the order they happen in the activity. An activity that came from Strava returns only its date and id.

  MCP callintervals_icu_read → get_activity

  REST endpointGET https://cotlet.dev/api/v1/intervals-icu/activity

  Parameters

  Parameters: get_activity

  Name	Type	Description
  id string required	string	Activity id from list_activities.

  Example input

  {
    "id": "id"
  }

  Example response

  {
    "id": "i88120456",
    "name": "Sunday long ride",
    "type": "Ride",
    "start_date_local": "2026-11-01T08:42:10",
    "moving_time": 12840,
    "icu_training_load": 124,
    "icu_rpe": 6,
    "feel": 2,
    "description": "Steady tempo, felt good.",
    "intervals": [
      {
        "id": 1,
        "label": "Interval 1",
        "moving_time": 1200,
        "average_watts": 212,
        "average_heartrate": 148
      },
      {
        "id": 2,
        "label": "Interval 2",
        "moving_time": 1200,
        "average_watts": 208,
        "average_heartrate": 151
      }
    ]
  }

• update_activity Change the name, description, RPE or feel of a completed activity. write

  Changes only the fields you pass on one of your activities. RPE is 1 to 10. The recorded data stays as it is. Returns the activity as saved. It reaches no one and a second call puts the old values back, so it does not ask for confirmation.

  MCP callintervals_icu_write → update_activity

  REST endpointPATCH https://cotlet.dev/api/v1/intervals-icu/activity

  Parameters

  Parameters: update_activity

  Name	Type	Description
  id string required	string	Activity id from list_activities.
  name string	string	New name.
  description string	string	New description.
  rpe integer	integer	Rate of perceived exertion, 1 to 10.
  feel integer	integer	Feel, on the scale the activity page shows.

  Example input

  {
    "id": "id"
  }

  Example response

  {
    "id": "i88120456",
    "name": "Sunday long ride",
    "icu_rpe": 6,
    "description": "Legs heavy in the last interval."
  }

• add_activity_comment Post a comment on an activity, visible to your coach and followers. writeasks first

  Adds a comment to one activity. Coaches and athletes who follow the activity can read it. Returns the comment with its time. By default you confirm each call; you can switch that off for this tool.

  MCP callintervals_icu_write → add_activity_comment

  REST endpointPOST https://cotlet.dev/api/v1/intervals-icu/activities/{activity_id}/comment

  Parameters

  Parameters: add_activity_comment

  Name	Type	Description
  activity_id string required	string	Activity id from list_activities.
  comment string required	string	Text of the comment.

  Example input

  {
    "activity_id": "activity_8c41d2",
    "comment": "comment"
  }

  Example response

  {
    "activity_id": "i88120456",
    "comment": "Felt strong on the climbs today.",
    "created": "2026-11-06T09:12:00"
  }

ToolWhat it doesAccess

• list_events Planned workouts, notes and races on your calendar in a date range. read

  Returns the calendar entries between two dates in date order: planned workouts, notes and races, each with id, category, sport type, name, start date and the workout text. Entries added by other apps are included. Use the id with update_event or delete_event.

  MCP callintervals_icu_read → list_events

  REST endpointGET https://cotlet.dev/api/v1/intervals-icu/events

  Parameters

  Parameters: list_events

  Name	Type	Description
  oldest date required	date	First day to include.
  newest date required	date	Last day to include.
  category enum	enum	WORKOUT or NOTE. Default: both.

  Example input

  {
    "oldest": "2026-10-01",
    "newest": "2026-10-01"
  }

  Example response

  {
    "events": [
      {
        "id": 55120931,
        "category": "WORKOUT",
        "type": "Ride",
        "start_date_local": "2026-11-09T00:00:00",
        "name": "Sweet spot 3x10",
        "description": "- 10m 55% Warmup\n\n3x\n- 10m 90%\n- 5m 50%\n\n- 10m 50% Cooldown"
      },
      {
        "id": 55120940,
        "category": "NOTE",
        "start_date_local": "2026-11-10T00:00:00",
        "name": "Rest day",
        "description": "No training."
      }
    ]
  }

• create_event Add a planned workout or a note to your calendar. write

  Adds one entry on a day of your calendar. A WORKOUT takes its steps as Intervals.icu workout text in description: one dash line per step with a duration and a target, repeats written as 3x on their own line. Returns the new event with its id. It reaches no one and you undo it with delete_event, so it does not ask for confirmation. Devices connected to Intervals.icu receive it as the app does for any planned workout.

  MCP callintervals_icu_write → create_event

  REST endpointPOST https://cotlet.dev/api/v1/intervals-icu/events

  Parameters

  Parameters: create_event

  Name	Type	Description
  category enum required	enum	WORKOUT or NOTE.
  start_date_local datetime required	datetime	Local day, e.g. 2026-11-09T00:00:00.
  name string required	string	Title shown on the calendar.
  type string	string	Sport for a workout, e.g. Ride, Run, WeightTraining.
  description string	string	Workout text for a WORKOUT, or the text of a NOTE.

  Example input

  {
    "category": "WORKOUT",
    "start_date_local": "2026-11-09T00:00:00",
    "name": "Sweet spot 3x10",
    "type": "Ride",
    "description": "- 10m 55% Warmup\n\n3x\n- 10m 90%\n- 5m 50%\n\n- 10m 50% Cooldown"
  }

  Example response

  {
    "id": 55120931,
    "category": "WORKOUT",
    "type": "Ride",
    "start_date_local": "2026-11-09T00:00:00",
    "name": "Sweet spot 3x10",
    "description": "- 10m 55% Warmup\n\n3x\n- 10m 90%\n- 5m 50%\n\n- 10m 50% Cooldown"
  }

• update_event Change the day, name or text of a planned workout or note. write

  Changes the fields you pass on one calendar entry and leaves the rest. Moving a workout is a new start_date_local. Returns the updated event. It reaches no one and a second call puts the old values back, so it does not ask for confirmation.

  MCP callintervals_icu_write → update_event

  REST endpointPATCH https://cotlet.dev/api/v1/intervals-icu/event

  Parameters

  Parameters: update_event

  Name	Type	Description
  id integer required	integer	Event id from list_events.
  start_date_local datetime	datetime	New local day.
  name string	string	New title.
  description string	string	New workout text or note text.

  Example input

  {
    "id": 1
  }

  Example response

  {
    "id": 55120931,
    "category": "WORKOUT",
    "type": "Ride",
    "start_date_local": "2026-11-11T00:00:00",
    "name": "Sweet spot 3x10"
  }

• delete_event Remove one planned workout or note from your calendar. write

  Deletes one calendar entry by id. Completed activities are not touched. It reaches no one; if you delete the wrong entry, create it again with create_event. It does not ask for confirmation.

  MCP callintervals_icu_write → delete_event

  REST endpointDELETE https://cotlet.dev/api/v1/intervals-icu/events

  Parameters

  Parameters: delete_event

  Name	Type	Description
  id integer required	integer	Event id from list_events.

  Example input

  {
    "id": 1
  }

  Example response

  {
    "deleted": 1,
    "id": 55120940
  }

ToolWhat it doesAccess

• list_wellness Daily wellness entries in a date range: weight, resting heart rate, sleep, fatigue and mood. read

  Returns one entry per day between two dates, oldest first, with the fields you or your device filled in: weight, resting heart rate, sleep, soreness, fatigue, stress, mood and comments. Days without data are left out. The fitness, fatigue and form values Intervals.icu calculates for each day come with the entry when the app shows them.

  MCP callintervals_icu_read → list_wellness

  REST endpointGET https://cotlet.dev/api/v1/intervals-icu/wellness

  Parameters

  Parameters: list_wellness

  Name	Type	Description
  oldest date required	date	First day to include.
  newest date required	date	Last day to include.

  Example input

  {
    "oldest": "2026-10-01",
    "newest": "2026-10-01"
  }

  Example response

  {
    "wellness": [
      {
        "id": "2026-11-04",
        "weight": 72.4,
        "restingHR": 48,
        "sleepSecs": 27000,
        "soreness": 2,
        "mood": 4
      },
      {
        "id": "2026-11-05",
        "weight": 72.3,
        "restingHR": 50,
        "sleepSecs": 25200,
        "soreness": 3,
        "mood": 3
      }
    ]
  }

• update_wellness Set wellness values for one day: sleep, weight, soreness, fatigue, stress, mood and comments. write

  Writes the values you pass for one day and keeps the others. Sleep is in hours; soreness, fatigue, stress and mood use the scales the Intervals.icu wellness form shows. Returns the day as saved. It reaches no one and a second call corrects it, so it does not ask for confirmation. A device that syncs the same day may write its own values over yours.

  MCP callintervals_icu_write → update_wellness

  REST endpointPATCH https://cotlet.dev/api/v1/intervals-icu/wellness

  Parameters

  Parameters: update_wellness

  Name	Type	Description
  date date required	date	Day to write.
  sleep_hours number	number	Hours of sleep.
  weight number	number	Body weight in kilograms.
  soreness integer	integer	Soreness, on the form scale.
  fatigue integer	integer	Fatigue, on the form scale.
  mood integer	integer	Mood, on the form scale.
  comments string	string	Free text for the day.

  Example input

  {
    "date": "2026-10-01"
  }

  Example response

  {
    "id": "2026-11-06",
    "sleepSecs": 27000,
    "soreness": 3,
    "mood": 4,
    "comments": "Slept well"
  }

ToolWhat it doesAccess

• get_sport_settings FTP, threshold heart rate, max heart rate and zones for one sport. read

  Returns the thresholds Intervals.icu uses for one sport: FTP, threshold heart rate, max heart rate, threshold pace and the zones built from them. Read it before writing workouts in percent so the targets match the athlete. It changes nothing.

  MCP callintervals_icu_read → get_sport_settings

  REST endpointGET https://cotlet.dev/api/v1/intervals-icu/sport-settings

  Parameters

  Parameters: get_sport_settings

  Name	Type	Description
  type string required	string	Sport, e.g. Ride, Run, Swim.

  Example input

  {
    "type": "type"
  }

  Example response

  {
    "type": "Ride",
    "ftp": 248,
    "lthr": 168,
    "max_hr": 189,
    "power_zones": [
      55,
      75,
      90,
      105,
      120,
      150,
      999
    ]
  }

• get_power_curve Best power for set durations over a date range. read

  Returns the best average power for standard durations (5 seconds to 1 hour) across the activities in a date range, with the date of each effort. Use it to check whether a recent best effort sits above your current FTP. Strava-sourced activities do not count because their data is not returned.

  MCP callintervals_icu_read → get_power_curve

  REST endpointGET https://cotlet.dev/api/v1/intervals-icu/power-curve

  Parameters

  Parameters: get_power_curve

  Name	Type	Description
  oldest date required	date	First day to include.
  newest date required	date	Last day to include.
  type string	string	Sport. Default: Ride.

  Example input

  {
    "oldest": "2026-10-01",
    "newest": "2026-10-01"
  }

  Example response

  {
    "type": "Ride",
    "bests": [
      {
        "seconds": 300,
        "watts": 318,
        "date": "2026-10-12"
      },
      {
        "seconds": 1200,
        "watts": 262,
        "date": "2026-10-19"
      },
      {
        "seconds": 3600,
        "watts": 238,
        "date": "2026-09-28"
      }
    ]
  }