COROS + Claude / ChatGPT

New connector

Claude and ChatGPT, with your COROS training behind them

COROS has its own MCP server, and OpenAthlete uses it to sync your watch. On top, OpenAthlete adds a calendar with training load, your other devices and your coach, and lets Claude or ChatGPT plan run, trail and bike workouts that go to your COROS.

Create a free account How it works

Free on every plan
OAuth, no password shared
Claude, ChatGPT, any MCP client

Example conversation

Trail race in eight weeks: 50 km, 2,400 m of climbing. Check my weekly vertical and plan the next four weeks.

Since September you've averaged 1,150 m of climbing a week, with one 1,900 m week. You climb 1,000 m/h on 15–20% slopes. I've planned four weeks building to 2,000 m: hill repeats on Tuesdays (8 × 3' uphill at threshold), a long hilly run on Saturdays, the fourth week lighter. 16 sessions, heading to your APEX 2 Pro.get_training_volume · get_capacities · plan_sessions

Claude · OpenAthlete MCP · COROS data

How it works

Three steps, about five minutes

Connect COROS to OpenAthlete

Create a free account, open Settings › Integrations and sign in with COROS on its own authorisation page. OpenAthlete receives a token, never your password.

COROS connection guide

Add OpenAthlete to Claude or ChatGPT

In Claude, add a custom connector; in ChatGPT, turn on developer mode and create a connector. Paste the address below and approve on the OpenAthlete page.

https://api.openathlete.org/mcp

Claude guide ChatGPT guide The MCP server

Ask

Write as you would to a coach. The assistant calls the tools it needs, shows which ones, and asks before it changes your calendar.

Two official sign-ins, no password handed over

COROS's own MCP server uses OAuth too, and OpenAthlete connects through it: you sign in on COROS's page, pick your region, and OpenAthlete receives a token.

What the AI sees

What your assistant reads and writes, from COROS

The assistant never talks to COROS directly. It works on what OpenAthlete has synced, through 23 MCP tools.

sync

OpenAthlete

MCP

Claude · ChatGPT

Planned sessions go back to the watch

Activities: Every new activity, fetched about every 30 minutes (COROS sends no notifications)
History on connection: All of it, at COROS's pace: 50 activity files a day, so years of training take several days
Sleep, HRV, wellness: HRV, resting heart rate, sleep, naps, VO2max
Training load and form: Computed by OpenAthlete from heart rate (TRIMP): fitness, fatigue and form, projected over the sessions to come
Plan in the calendar: Yes: up to 60 sessions per request, with structured steps and targets from your zones, % of VMA, FTP or HR max
Send workouts to COROS: Yes, for running, trail running and cycling. COROS does not let apps delete a planned session: a deleted one becomes a “removed” placeholder

Metric import is off by default: turn on “Import metrics” for COROS in OpenAthlete.

Ask it

What COROS users ask

Under each prompt, the OpenAthlete tools the assistant calls to answer it.

“What is my climbing speed on 15 to 20% slopes? Use it to estimate my time on a 900 m climb.”

get_capacities

“My HRV has been low three nights running. Should I still do Saturday's long run?”

get_metrics→get_calendar→update_session

“Copy last week to next week, but turn the Wednesday intervals into hill repeats.”

get_calendar→copy_sessions→update_session

“I rolled my ankle on a descent today. Log it and rework the next ten days.”

create_period→move_sessions→update_session

“How does my heart rate drift on outings over four hours? I want to pace the first half of my 50 km.”

get_capacities→get_activities

Side by side

COROS's own AI and MCP, and OpenAthlete

What each one does, checked on 3 November 2026. Nothing stops you from using both.

From COROS

An official MCP server (mcp.coros.com/mcp) since May 2026, for Claude, ChatGPT in developer mode, Cursor and Gemini CLI.
Since 21 September 2026 it creates workouts and 4 to 16-week plans for road running, trail running and cycling. Deleting them is done in the COROS app.
It reads COROS data only: workouts, daily health, HRV, sleep, EvoLab load and fitness.

OpenAthlete MCP server

Claude, ChatGPT, Cursor or any MCP client, on the AI plan you already have
Plans running, trail and cycling sessions in your calendar, with targets from your zones; they go to your COROS.
Every device in one history: Garmin, COROS, Suunto, Polar and FIT files, with training load and form
Free, open source (AGPL), self-hostable. Your coach can work on your calendar through the same server.

If COROS is your only device and you train alone, COROS's own MCP may be all you need. OpenAthlete earns its place with one calendar for load and form, other devices, a coach, or your data on your own server.

Questions about COROS and AI

Yes. COROS runs one at mcp.coros.com/mcp, and since September 2026 it can create workouts and plans as well as read your data. OpenAthlete itself connects to your COROS account through that server.

For what COROS's server doesn't hold: training load and form across all your devices, a calendar your coach sees too, periods for illness or travel, workouts with targets from your zones, and up to 60 sessions in one request. It is also open source and can run on your own server.

Running, trail running and cycling. Other sports stay in the OpenAthlete calendar. COROS does not let apps delete a planned session, so if the assistant deletes one, COROS keeps a placeholder marked as removed.

It is new (November 2026). History arrives over several days because COROS serves 50 activity files a day. If something looks off, tell us on GitHub or Discord.

No. The MCP server is free on every OpenAthlete plan, Free included. The model runs on your Claude or ChatGPT account, so their plan limits apply. Supporter (€5 a month) only covers the AI features inside OpenAthlete and unlimited coached athletes.

Other devices