COROS AI

COROS AI: what can AI do with your COROS data?

COROS offers its own MCP, a connection that lets an AI such as ChatGPT or Claude read your COROS data and build workouts. You can also use Memory.fit, which reads COROS through it and adds your other devices, meals and fuel.

Your AI reads your COROS sessions, sleep, HRV and resting heart rate, and plans workouts that Memory.fit puts on your COROS calendar.

Get it onGoogle Play

What COROS's own AI connection does

COROS MCP connects your COROS account to AI tools. COROS lists ChatGPT (in Developer Mode), Claude Desktop, Cursor and Gemini CLI. The AI can read workouts, VO2max, threshold pace, race predictions, training load, sleep, HRV and heart rate, and can build workouts and plans for road running, trail running and cycling.

Plans run 4 to 16 weeks, and the AI can edit items but not delete them; deleting is done in the COROS app. Fetching FIT files is capped at 50 per day. COROS does not state a price on that page.

  • Clients: ChatGPT, Claude Desktop, Cursor, Gemini CLI
  • Builds running and cycling workouts and plans
  • 50 FIT file requests a day
  • Covers COROS only

COROS in Memory.fit

Memory.fit reads COROS through COROS's own MCP, so the daily FIT limit is shared with any AI you connect to COROS directly. You connect COROS in the Memory.fit app, add Memory.fit to your AI, and it reads your COROS data next to your other sources.

One COROS connection does both jobs: Memory.fit reads your data, and adds or updates only the sessions your AI plans on your COROS calendar.

  • Reads: activities with heart rate, power and cadence, sleep, HRV, resting heart rate, VO2max
  • Writes: structured run and bike sessions with steps and targets, up to 90 days ahead
  • Swims and strength sessions stay in the Memory.fit app
  • A session your AI moves leaves a copy marked Cancelled that you delete in the COROS app

Which one to use

COROS's own MCP is a good fit if COROS is your only device and you want nothing more. Memory.fit fits when you also use another device, want meals and fuel in the same place, or want one memory that every AI shares.

In your AI

The AI you already use, with your data in Memory.fit.

Every AI, with its own steps

What to send

Copy one, send it to your AI.

  • “Read my COROS runs from the last six weeks and my sleep in Memory.fit, and tell me if I'm ready for a harder block.”

    Tools:get_workoutsget_sleepget_trends

  • “Put a 6 x 1 km session on my COROS for Tuesday at threshold pace using Memory.fit.”

    Tools:plan_sessionset_session_structuresend_session_to_devices

  • “Plan carbs per hour for Saturday's three hour ride in Memory.fit.”

    Tools:get_workoutsset_session_fuel_plan

  • “How has my resting heart rate moved with my training load this month? Check Memory.fit.”

    Tools:get_daily_metricsget_training_load

Questions

In short.

  • COROS offers an MCP server that lets an AI tool read your COROS data and build workouts for running and cycling.

  • Both work. COROS's covers COROS. Memory.fit reads COROS through it and adds your other devices, meals and fuel, and one memory every AI shares.

  • Yes. Memory.fit sends structured run and bike sessions to your COROS calendar, up to 90 days ahead.

  • COROS lets an AI edit but not delete items, so a removed session leaves a copy marked Cancelled that you delete in the COROS app.

Your next chapter starts with everything you've learned.

On Android now. iPhone is coming: join the waitlist and we'll email you the day Memory.fit is on the App Store.

No spam. One email when it's ready.

Get it onGoogle Play