Garmin Connect API and MCP server Let your AI agent coach you from Garmin Connect.

ToolWhat it doesAccess

• list_activities Activities with type, date, distance, duration and average heart rate. read

  Lists the activities on your Activities page, newest first. Filter by activity type and by date range, then pass an activity_id to get_activity or download_activity. Pages hold up to 100 activities; pass next_cursor back as cursor for the next page.

  MCP callgarmin_read → list_activities

  REST endpointGET https://cotlet.dev/api/v1/garmin/activities

  Parameters

  Parameters: list_activities

  Name	Type	Description
  type string	string	Activity type as Garmin Connect names it, e.g. running or cycling.
  from date	date	First day to include.
  to date	date	Last day to include. Default: today.
  limit integer	integer	1 to 100. Default: 25.
  cursor string	string	Next page cursor from the previous call.

  Example response

  {
    "activities": [
      {
        "activity_id": "9000000101",
        "name": "Long Run",
        "type": "running",
        "date": "2026-10-24",
        "distance_km": 21.1,
        "duration_min": 118,
        "avg_heart_rate": 152
      },
      {
        "activity_id": "9000000087",
        "name": "Tempo Run",
        "type": "running",
        "date": "2026-10-22",
        "distance_km": 12,
        "duration_min": 58,
        "avg_heart_rate": 161
      }
    ],
    "next_cursor": null
  }

• get_activity One activity with its summary, splits and heart rate zones. read

  Returns one activity as Garmin Connect shows it: totals, lap splits and time in each heart rate zone. Nothing is changed. Fields the device did not record, such as power on a run without a sensor, are left out.

  MCP callgarmin_read → get_activity

  REST endpointGET https://cotlet.dev/api/v1/garmin/activities/{activity_id}

  Parameters

  Parameters: get_activity

  Name	Type	Description
  activity_id string required	string	Activity ID from list_activities.

  Example input

  {
    "activity_id": "activity_8c41d2"
  }

  Example response

  {
    "activity_id": "9000000101",
    "name": "Long Run",
    "type": "running",
    "date": "2026-10-24",
    "distance_km": 21.1,
    "duration_min": 118,
    "avg_heart_rate": 152,
    "max_heart_rate": 171,
    "splits": [
      {
        "km": 1,
        "pace_min_per_km": "5:35"
      },
      {
        "km": 2,
        "pace_min_per_km": "5:32"
      }
    ]
  }

• download_activity The activity as its original FIT file, or as GPX or TCX. read

  Exports one activity from the web app and returns a download link to the file. original is the FIT file the device recorded. GPX and TCX are not offered for every activity type, and Garmin exports multisport activities only as FIT. Nothing is changed.

  MCP callgarmin_read → download_activity

  REST endpointGET https://cotlet.dev/api/v1/garmin/activities/{activity_id}/download

  Parameters

  Parameters: download_activity

  Name	Type	Description
  activity_id string required	string	Activity ID from list_activities.
  format string	string	original, gpx or tcx. Default: original.

  Example input

  {
    "activity_id": "activity_8c41d2"
  }

  Example response

  {
    "activity_id": "9000000101",
    "format": "original",
    "file_name": "9000000101.zip",
    "download_url": "https://files.cotlet.dev/example/9000000101.zip"
  }

ToolWhat it doesAccess

• get_sleep One night of sleep: score, total time and sleep stages. read

  Returns the night that ends on the given date: sleep score, total sleep time and the time in each stage, as Garmin Connect shows it. Empty when the watch was not worn that night. Nothing is changed.

  MCP callgarmin_read → get_sleep

  REST endpointGET https://cotlet.dev/api/v1/garmin/sleep

  Parameters

  Parameters: get_sleep

  Name	Type	Description
  date date	date	Day to read. Default: today.

  Example response

  {
    "date": "2026-10-26",
    "sleep_score": 82,
    "total_sleep_min": 452,
    "stages_min": {
      "deep": 74,
      "light": 241,
      "rem": 98,
      "awake": 39
    }
  }

• get_hrv_status Overnight heart rate variability and the HRV status Garmin assigns. read

  Returns the overnight HRV average for the date and the status Garmin shows: Balanced, Unbalanced, Low, Poor or No Status. Garmin needs about three weeks of consistent sleep data before it gives a status, so a new device returns No Status. Nothing is changed.

  MCP callgarmin_read → get_hrv_status

  REST endpointGET https://cotlet.dev/api/v1/garmin/hrv-status

  Parameters

  Parameters: get_hrv_status

  Name	Type	Description
  date date	date	Day to read. Default: today.

  Example response

  {
    "date": "2026-10-26",
    "overnight_avg_ms": 58,
    "seven_day_avg_ms": 56,
    "status": "Balanced"
  }

• get_body_battery Body Battery for a day: the morning level, the day's high and low, and what drained it. read

  Returns the Body Battery levels Garmin Connect charts for the day, on its scale of 5 to 100: the level at waking, the highest and the lowest. Sleep charges it and activity and stress drain it. Nothing is changed.

  MCP callgarmin_read → get_body_battery

  REST endpointGET https://cotlet.dev/api/v1/garmin/body-battery

  Parameters

  Parameters: get_body_battery

  Name	Type	Description
  date date	date	Day to read. Default: today.

  Example response

  {
    "date": "2026-10-26",
    "at_wake": 78,
    "highest": 82,
    "lowest": 24,
    "charged": 61,
    "drained": 58
  }

• get_training_status Training status, training readiness and VO2 max as Garmin Connect shows them. read

  Returns the training status label, the training readiness score and VO2 max for the date. Garmin calculates readiness from sleep score, recovery time, HRV status, acute load and sleep and stress history. Only devices that support these metrics fill them; the rest come back empty.

  MCP callgarmin_read → get_training_status

  REST endpointGET https://cotlet.dev/api/v1/garmin/training-status

  Parameters

  Parameters: get_training_status

  Name	Type	Description
  date date	date	Day to read. Default: today.

  Example response

  {
    "date": "2026-10-26",
    "training_status": "Productive",
    "training_readiness": 71,
    "vo2_max": 52
  }

ToolWhat it doesAccess

• list_workouts Workouts in your library, with name, sport and number of steps. read

  Lists the workouts under Training & Planning > Workouts, newest first. Pass a workout_id to schedule_workout. Nothing is changed.

  MCP callgarmin_read → list_workouts

  REST endpointGET https://cotlet.dev/api/v1/garmin/workouts

  Parameters

  Parameters: list_workouts

  Name	Type	Description
  sport string	string	Filter by sport, e.g. running or cycling.
  limit integer	integer	1 to 100. Default: 50.

  Example response

  {
    "workouts": [
      {
        "workout_id": "wk_3301",
        "name": "Tempo 3 x 10 min",
        "sport": "running",
        "steps": 9
      },
      {
        "workout_id": "wk_3290",
        "name": "Easy 40 min",
        "sport": "running",
        "steps": 1
      }
    ]
  }

• get_training_calendar Scheduled workouts and activities on your calendar in a date range. read

  Returns what your Garmin Connect training calendar holds between two dates: scheduled workouts, training plan sessions and finished activities, earliest first. Without dates it covers the next 7 days. Nothing is changed.

  MCP callgarmin_read → get_training_calendar

  REST endpointGET https://cotlet.dev/api/v1/garmin/training-calendar

  Parameters

  Parameters: get_training_calendar

  Name	Type	Description
  from date	date	Start of the range. Default: today.
  to date	date	End of the range. Default: 7 days after from.

  Example response

  {
    "days": [
      {
        "date": "2026-10-29",
        "scheduled": [
          {
            "workout_id": "wk_3301",
            "name": "Tempo 3 x 10 min"
          }
        ],
        "activities": []
      },
      {
        "date": "2026-10-31",
        "scheduled": [],
        "activities": []
      }
    ]
  }

• create_workout New workout in your library from a list of steps. It is not scheduled or sent anywhere. write

  Builds a workout under Training & Planning > Workouts > Create a Workout and returns its workout_id. Each step has a type such as warm up, run, recover or cool down, a duration or distance and an optional target. The workout stays in your library until schedule_workout puts it on a date. It reaches no one and you can delete it in Garmin Connect, so it runs without asking.

  MCP callgarmin_write → create_workout

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

  Parameters

  Parameters: create_workout

  Name	Type	Description
  name string required	string	Workout name, e.g. "Tempo 3 x 10 min".
  sport string required	string	Sport as Garmin Connect names it, e.g. running or cycling.
  steps object required	object	List of { type, duration_min or distance_km, target }. type: warm up, run, recover, cool down or repeat.

  Example input

  {
    "name": "Tempo 3 x 10 min",
    "sport": "sport",
    "steps": "steps"
  }

  Example response

  {
    "workout_id": "wk_3301",
    "name": "Tempo 3 x 10 min",
    "sport": "running",
    "steps": 9
  }

• schedule_workout Put a workout from your library on a date in your training calendar. writeasks first

  Adds the workout to your Garmin Connect training calendar on the date you give and returns the calendar entry. Garmin's manuals say scheduled workouts in Connect can be sent to your device and overwrite the training calendar already on it, so this changes what your watch shows after its next sync. By default you confirm each call; you can switch that off for this tool.

  MCP callgarmin_write → schedule_workout

  REST endpointPOST https://cotlet.dev/api/v1/garmin/workouts/{workout_id}/schedule

  Parameters

  Parameters: schedule_workout

  Name	Type	Description
  workout_id string required	string	Workout ID from list_workouts or create_workout.
  date date required	date	Day to schedule it on.

  Example input

  {
    "workout_id": "wk_3301",
    "date": "2026-10-29"
  }

  Example response

  {
    "workout_id": "wk_3301",
    "date": "2026-10-29",
    "status": "scheduled",
    "name": "Tempo 3 x 10 min"
  }