TrainingPeaks MCP server Let your AI agent plan your TrainingPeaks week.

ToolWhat it doesAccess

• list_calendar_workouts Planned and completed workouts between two dates, with compliance. read

  Returns every workout on the calendar between start_date and end_date, oldest day first. Each workout shows its planned values next to its completed values, so a skipped workout has no completed values. compliance is the colour TrainingPeaks shows: green, yellow, orange, red (not completed) or grey (unplanned). Without athlete_id it reads your own calendar.

  MCP calltrainingpeaks_read → list_calendar_workouts

  REST endpointGET https://cotlet.dev/api/v1/trainingpeaks/calendar-workouts

  Parameters

  Parameters: list_calendar_workouts

  Name	Type	Description
  start_date date required	date	First day to read.
  end_date date required	date	Last day to read.
  athlete_id string	string	Athlete from list_athletes. Default: your own calendar.

  Example input

  {
    "start_date": "2026-10-01",
    "end_date": "2026-10-01"
  }

  Example response

  {
    "workouts": [
      {
        "workout_id": "wk_88121",
        "date": "2026-11-02",
        "title": "Easy run",
        "sport": "Run",
        "planned": {
          "duration_minutes": 45,
          "tss": 38
        },
        "completed": {
          "duration_minutes": 47,
          "tss": 40
        },
        "compliance": "green"
      },
      {
        "workout_id": "wk_88124",
        "date": "2026-11-04",
        "title": "Threshold intervals",
        "sport": "Bike",
        "planned": {
          "duration_minutes": 75,
          "tss": 85
        },
        "completed": null,
        "compliance": "red"
      }
    ]
  }

• get_workout One workout with its description, planned and completed values and comments. read

  Returns the workout's description, planned and completed values and the pre and post activity comments. The structured intervals are included for workouts built in the Workout Builder. Use workout_id from list_calendar_workouts.

  MCP calltrainingpeaks_read → get_workout

  REST endpointGET https://cotlet.dev/api/v1/trainingpeaks/workouts/{workout_id}

  Parameters

  Parameters: get_workout

  Name	Type	Description
  workout_id string required	string	Workout from list_calendar_workouts.

  Example input

  {
    "workout_id": "workout_8c41d2"
  }

  Example response

  {
    "workout_id": "wk_88121",
    "date": "2026-11-02",
    "title": "Easy run",
    "sport": "Run",
    "description": "Keep it conversational.",
    "planned": {
      "duration_minutes": 45,
      "tss": 38
    },
    "completed": {
      "duration_minutes": 47,
      "tss": 40
    },
    "comments": [
      {
        "author": "Lena Ford",
        "text": "Legs felt heavy at first."
      }
    ]
  }

• list_events Upcoming events and goals with their date and priority. read

  Returns events and goals from today on, soonest first, with the priority set in TrainingPeaks. The A priority event is the one automatic periodization uses. Without athlete_id it reads your own calendar.

  MCP calltrainingpeaks_read → list_events

  REST endpointGET https://cotlet.dev/api/v1/trainingpeaks/events

  Parameters

  Parameters: list_events

  Name	Type	Description
  athlete_id string	string	Athlete from list_athletes. Default: your own calendar.

  Example response

  {
    "events": [
      {
        "name": "City Half Marathon",
        "date": "2027-03-14",
        "priority": "A"
      },
      {
        "name": "Spring 10K",
        "date": "2027-02-07",
        "priority": "B"
      }
    ]
  }

• add_workout Plan a workout on a calendar day. writeasks first

  Creates a planned workout on the given day with the values you pass. It appears on the calendar like one added with the plus icon. On an athlete's calendar the athlete sees it, which is why the call is confirmed. By default you confirm each call; you can switch that off for this tool.

  MCP calltrainingpeaks_write → add_workout

  REST endpointPOST https://cotlet.dev/api/v1/trainingpeaks/workouts

  Parameters

  Parameters: add_workout

  Name	Type	Description
  date date required	date	Calendar day.
  title string required	string	Workout name.
  sport string required	string	Sport as TrainingPeaks lists it, e.g. Run or Bike.
  description string	string	Text shown in the workout description.
  planned_duration_minutes integer	integer	Planned duration in minutes.
  planned_tss number	number	Planned TSS.
  athlete_id string	string	Athlete from list_athletes. Default: your own calendar.

  Example input

  {
    "date": "2026-11-11",
    "title": "Threshold intervals",
    "sport": "Bike",
    "description": "Warm up, then intervals at threshold.",
    "planned_duration_minutes": 75,
    "planned_tss": 85
  }

  Example response

  {
    "workout_id": "wk_88131",
    "date": "2026-11-11",
    "title": "Threshold intervals",
    "sport": "Bike",
    "planned": {
      "duration_minutes": 75,
      "tss": 85
    },
    "status": "planned"
  }

• move_workout Move a workout to another calendar day. writeasks first

  Moves one workout to the new day and keeps its planned and completed values. On an athlete's calendar the athlete sees the change, which is why the call is confirmed. By default you confirm each call; you can switch that off for this tool.

  MCP calltrainingpeaks_write → move_workout

  REST endpointPOST https://cotlet.dev/api/v1/trainingpeaks/workouts/{workout_id}/move

  Parameters

  Parameters: move_workout

  Name	Type	Description
  workout_id string required	string	Workout from list_calendar_workouts.
  date date required	date	New calendar day.

  Example input

  {
    "workout_id": "workout_8c41d2",
    "date": "2026-10-01"
  }

  Example response

  {
    "workout_id": "wk_88124",
    "date": "2026-11-05",
    "title": "Threshold intervals",
    "status": "planned"
  }

• comment_on_workout Add a comment to a workout. writeasks first

  Adds a comment to the workout that the athlete and the coach can both read. Comments cannot be edited by this tool. By default you confirm each call; you can switch that off for this tool.

  MCP calltrainingpeaks_write → comment_on_workout

  REST endpointPOST https://cotlet.dev/api/v1/trainingpeaks/workouts/{workout_id}/replies

  Parameters

  Parameters: comment_on_workout

  Name	Type	Description
  workout_id string required	string	Workout from list_calendar_workouts.
  text string required	string	Comment text.

  Example input

  {
    "workout_id": "workout_8c41d2",
    "text": "text"
  }

  Example response

  {
    "workout_id": "wk_88121",
    "comment_id": "cm_5012",
    "text": "Good pacing. Keep Thursday easy.",
    "status": "posted"
  }

ToolWhat it doesAccess

• list_workout_library Your Workout Library folders and the workouts in them. read

  Returns each library with its workouts, in the order TrainingPeaks shows them. Use library_workout_id in add_workout_from_library. A Basic athlete account holds 5 workouts in its Library; Premium holds more.

  MCP calltrainingpeaks_read → list_workout_library

  REST endpointGET https://cotlet.dev/api/v1/trainingpeaks/workout-libraries

  Parameters

  Parameters: list_workout_library

  Name	Type	Description
  library string	string	Only this library name.

  Example response

  {
    "libraries": [
      {
        "library": "Base block",
        "workouts": [
          {
            "library_workout_id": "lib_301",
            "title": "Easy run",
            "sport": "Run"
          },
          {
            "library_workout_id": "lib_302",
            "title": "Long run",
            "sport": "Run"
          }
        ]
      }
    ]
  }

• add_workout_from_library Put a Workout Library workout on a calendar day. writeasks first

  Copies the library workout to the day, like dragging it from the Library to the calendar. The library keeps its own copy. On an athlete's calendar the athlete sees it, which is why the call is confirmed. By default you confirm each call; you can switch that off for this tool.

  MCP calltrainingpeaks_write → add_workout_from_library

  REST endpointPOST https://cotlet.dev/api/v1/trainingpeaks/library-workouts/{library_workout_id}/workout-from-libraries

  Parameters

  Parameters: add_workout_from_library

  Name	Type	Description
  library_workout_id string required	string	Workout from list_workout_library.
  date date required	date	Calendar day.
  athlete_id string	string	Athlete from list_athletes. Default: your own calendar.

  Example input

  {
    "library_workout_id": "library_workout_8c41d2",
    "date": "2026-10-01"
  }

  Example response

  {
    "workout_id": "wk_88140",
    "date": "2026-11-10",
    "title": "Easy run",
    "sport": "Run",
    "status": "planned"
  }

• list_training_plans Your Training Plans with their length. Coach accounts only. read

  Returns the Training Plans you created, each a multi-week block of training. Use plan_id in apply_training_plan. An athlete account gets a permission error.

  MCP calltrainingpeaks_read → list_training_plans

  REST endpointGET https://cotlet.dev/api/v1/trainingpeaks/training-plans

  Parameters

  No parameters.

  Example response

  {
    "plans": [
      {
        "plan_id": "plan_77",
        "name": "10K build",
        "weeks": 8
      },
      {
        "plan_id": "plan_81",
        "name": "Base block",
        "weeks": 4
      }
    ]
  }

• apply_training_plan Apply a Training Plan to athletes from a start date or an end date. writeasks first

  Applies the plan to every athlete in athlete_ids. You give a start_date, or an end_date to count back from, the same choice TrainingPeaks offers when you click apply. The plan's workouts land on each athlete's calendar. Coach accounts only. By default you confirm each call; you can switch that off for this tool.

  MCP calltrainingpeaks_write → apply_training_plan

  REST endpointPOST https://cotlet.dev/api/v1/trainingpeaks/plans/{plan_id}/training-plan/apply

  Parameters

  Parameters: apply_training_plan

  Name	Type	Description
  plan_id string required	string	Plan from list_training_plans.
  athlete_ids array required	array	Athletes from list_athletes.
  start_date date	date	First day of the plan. Give this or end_date.
  end_date date	date	Last day of the plan. Give this or start_date.

  Example input

  {
    "plan_id": "plan_8c41d2",
    "athlete_ids": "athlete ids"
  }

  Example response

  {
    "plan_id": "plan_77",
    "applied_to": [
      "ath_20418",
      "ath_20433"
    ],
    "start_date": "2026-12-01",
    "status": "applied"
  }

ToolWhat it doesAccess

• list_athletes Athletes in your Athlete Library, with their groups. Coach accounts only. read

  Returns the athletes in the coach's Athlete Library with the group each one is in. Use athlete_id as the athlete parameter of the other tools. An athlete account has no Athlete Library and gets a permission error.

  MCP calltrainingpeaks_read → list_athletes

  REST endpointGET https://cotlet.dev/api/v1/trainingpeaks/athletes

  Parameters

  Parameters: list_athletes

  Name	Type	Description
  group string	string	Only athletes in this group name.

  Example response

  {
    "athletes": [
      {
        "athlete_id": "ath_20418",
        "name": "Lena Ford",
        "group": "10K group"
      },
      {
        "athlete_id": "ath_20433",
        "name": "Marco Reyes",
        "group": "10K group"
      }
    ]
  }

ToolWhat it doesAccess

• list_metrics Metrics logged on the calendar between two dates, newest first. read

  Returns the metric entries on the calendar between start_date and end_date, newest first. Each entry has the metric type exactly as TrainingPeaks names it in your Metrics list, so you can reuse the type in add_metric. Without athlete_id it reads your own calendar.

  MCP calltrainingpeaks_read → list_metrics

  REST endpointGET https://cotlet.dev/api/v1/trainingpeaks/metrics

  Parameters

  Parameters: list_metrics

  Name	Type	Description
  start_date date required	date	First day to read.
  end_date date required	date	Last day to read.
  athlete_id string	string	Athlete from list_athletes. Default: your own calendar.

  Example input

  {
    "start_date": "2026-10-01",
    "end_date": "2026-10-01"
  }

  Example response

  {
    "metrics": [
      {
        "date": "2026-11-04",
        "type": "Weight",
        "value": 71.6,
        "unit": "kg"
      },
      {
        "date": "2026-11-03",
        "type": "Weight",
        "value": 71.9,
        "unit": "kg"
      }
    ]
  }

• add_metric Record a metric on a calendar day. writeasks first

  Records one value for a metric type on the day, like entering a Metric with the plus icon. Take the type from list_metrics so it matches your Metrics list. On an athlete's calendar the athlete sees the entry, which is why the call is confirmed. By default you confirm each call; you can switch that off for this tool.

  MCP calltrainingpeaks_write → add_metric

  REST endpointPOST https://cotlet.dev/api/v1/trainingpeaks/metrics

  Parameters

  Parameters: add_metric

  Name	Type	Description
  date date required	date	Calendar day.
  type string required	string	Metric type as named in list_metrics.
  value number required	number	Value to record.
  athlete_id string	string	Athlete from list_athletes. Default: your own calendar.

  Example input

  {
    "date": "2026-10-01",
    "type": "type",
    "value": 1
  }

  Example response

  {
    "date": "2026-11-05",
    "type": "Weight",
    "value": 71.4,
    "unit": "kg",
    "status": "saved"
  }

• get_fitness_chart CTL, ATL and TSB per day from the Performance Management Chart. read

  Returns one row per day between start_date and end_date: ctl (long-term fitness), atl (short-term fatigue) and tsb (form, CTL minus ATL). The numbers are those of the Dashboard chart, so they follow the CTL and ATL start values set there. They can differ from the numbers on the Home view.

  MCP calltrainingpeaks_read → get_fitness_chart

  REST endpointGET https://cotlet.dev/api/v1/trainingpeaks/fitness-chart

  Parameters

  Parameters: get_fitness_chart

  Name	Type	Description
  start_date date required	date	First day to read.
  end_date date required	date	Last day to read.
  athlete_id string	string	Athlete from list_athletes. Default: your own chart.

  Example input

  {
    "start_date": "2026-10-01",
    "end_date": "2026-10-01"
  }

  Example response

  {
    "days": [
      {
        "date": "2026-11-01",
        "ctl": 52.4,
        "atl": 58.1,
        "tsb": -5.7
      },
      {
        "date": "2026-11-02",
        "ctl": 52.6,
        "atl": 56.9,
        "tsb": -4.3
      }
    ]
  }