Coros Training Hub vs Intervals.icu Compared
By Toby Pattullo
Australian Deaflympic marathon and ultra runner, and the solo developer behind IcuSync.
If you run or ride with a Coros watch, you already have a lot for free. EvoLab tracks training load, recovery, VO2 max and race predictions out of the box, no subscription, unlocked after a single 25-minute run. Training Hub adds a calendar, a structured workout builder, and free coach feedback on top.
So why do some Coros users also connect Intervals.icu? We looked into it, and the honest answer is: it depends what kind of athlete you are. Here's a straight comparison, including what changed with Coros' own AI integration in 2026.
At a glance
| Coros Training Hub | Intervals.icu | |
|---|---|---|
| Cost | Free with any Coros watch | Free, paid tier for extra features |
| Power-duration curve, running | Not available (pace-based model instead) | Yes |
| Power-duration curve, cycling | Max Mean Power curve only | Full Power-duration Curve |
| Multi-device / multi-brand history | Coros data only | Yes, works across Garmin, Coros, Wahoo, Suunto, Polar and more |
| Wellness data (sleep, HR, steps) | Split between phone app and web | Unified in one dashboard |
| Structured workout builder | Yes | Yes, more granular |
| Syncs with Coros watch | Native, it's the same platform | Yes, official supported 3rd party app |
| AI data access | Coros MCP (official) | Any MCP-compatible AI, including IcuSync |
| AI can read training data | Yes | Yes |
| AI can write a workout to your device today | Not yet, listed as "coming soon" | Yes, today, via IcuSync |
| AI write access, brand coverage when available | Coros only | Garmin, Coros, Wahoo, Suunto, Zwift, Amazfit, HUAWEI Health (Polar: activity sync only, no workout push) |
| Paid AI plan required | Coros recommends Claude Pro / ChatGPT Plus; requirement is set by the AI platform, not Coros | No, works on Claude's free plan too |
What Coros Training Hub already does well
- EvoLab is free on every watch and doesn't need a subscription
- Training Load, recovery time, VO2 max and race prediction are calculated automatically
- Coros Coaches, a pool of real human coaches, will review your EvoLab data and answer training questions for free, though it's shared support rather than a private 1:1 coach and typically takes 1 to 3 business days to hear back
- The structured workout builder and calendar sync straight to your watch
If you're a casual or budget-conscious runner who mainly wants "am I training too hard this week," Training Hub covers that on its own. You don't need anything else.
Where Coros Training Hub falls short
Two gaps show up consistently once training gets more serious.
No power-duration curve for running. Coros made a deliberate choice to model running by pace rather than power. Even if you have a Stryd pod paired natively, EffortPace still reports your effort as a pace figure, not watts. For cycling there's a Max Mean Power curve, but running has no equivalent. If you train by power (like Canova-style running with a power meter), this matters.
Wellness data is split across two places. Daily steps, energy, 24-hour heart rate and sleep live in the phone app. EvoLab and training analysis live on the Training Hub website. There's no single view that pulls both together, so you end up switching between app and browser to see the full picture.
Single-device history. Training Hub only sees Coros data. If you've switched watch brands over the years, train with Zwift, or work with a coach who has athletes on Garmin, Wahoo and Coros, Training Hub can't unify that.
What changed: the Coros MCP
In May 2026, Coros became the first major watch brand to launch an official MCP (Model Context Protocol) integration, letting you connect your Coros account directly to Claude or ChatGPT and ask questions about your training in plain language. It's a genuinely useful addition and worth understanding clearly, because it's easy to overstate what it does right now.
Here's what it actually is, based on Coros' own official MCP repository and support documentation:
- Read-only, for now, but the write tools are visibly on the way. Coros' own tool list includes
generateTrainingPlanandupdateTrainingPlan, both explicitly marked "coming soon." They're not live yet. Today, an AI connected to Coros MCP can build you a training plan, but it stays inside the chat, it doesn't land on your calendar or your watch. Coros' support documentation says a write-enabled update is planned "before September 2026," so this is worth rechecking regularly, it could ship at any time. - No power data. Scanning the full tool list, there's no tool for cycling power, running power, a power curve, or FTP estimation, even with a power meter paired. This is the clearest ongoing gap for power-based training.
- Lap and interval detail is now supported directly, this expanded since the integration launched. Dedicated tools now let an AI query lap and segment data per activity, and even a custom time window within an activity (useful for pulling "just the last 10 minutes"). For full second-by-second or GPS route detail, you still need the .FIT file, retrievable through the MCP but capped at 50 files a day.
- The paid-plan requirement comes from the AI platform, not Coros. Coros' support page recommends Claude Pro or ChatGPT Plus and says free tiers often don't support MCP connections, but Coros' own MCP documentation is explicit that COROS MCP itself is free, any subscription or quota requirement is set by whichever AI platform you connect it to, and that can change over time.
None of this makes the Coros MCP bad. It's a real signal that native AI training tools are coming to watch platforms, and reading your own training data through natural language, including lap-level detail, is genuinely useful today. But if what you actually want is for an AI to build a workout and have it show up on your watch, that's not live yet on Coros MCP, and when it ships, it'll only work with Coros gear.
Comparing the MCP tool sets directly
Both MCPs are real, official integrations, and it's worth seeing what each one can actually do rather than comparing marketing claims. Coros MCP tool names are taken directly from Coros' own repository, IcuSync tool names are our own.
| Capability | Coros MCP | IcuSync (via Intervals.icu) |
|---|---|---|
| Activity history and details | Yes (querySportRecords, getActivityDetail) | Yes (get_training_history, get_activity_detail) |
| Lap/segment and custom time-window analysis | Yes (queryActivityLapData, queryCustomActivityLapData) | Partial, via activity detail and extended metrics |
| Raw .FIT file access | Yes, capped at 50/day (downloadActivityFitFiles) | Not exposed as a tool |
| Power-duration curve (running and cycling) | Not available , no power tool in the list | Yes (get_power_curves) |
| Best efforts / all-time bests | Not available | Yes (get_best_efforts) |
| Climb segment detection | Not available | Yes (get_climb_segments) |
| Ride power pattern analysis | Not available | Yes (get_ride_power_patterns) |
| Fitness, fatigue, form (CTL/ATL/TSB-style) | Yes (queryFitnessAssessmentOverview, queryTrainingLoadAssessment) | Yes (get_fitness, get_training_summary) |
| Sleep, HRV, stress, daily health | Yes, with detailed raw curves (querySleepHrv, queryHealthCheckTimeSeries, queryStressTimeSeries) | Yes, at daily summary level (get_wellness) |
| Menstrual cycle tracking | Yes (queryMenstruationCycles) | Not available |
| Read planned training schedule | Yes (queryTrainingSchedule) | Yes (get_events) |
| Generate and write a training plan to your account | Coming soon, not live (generateTrainingPlan) | Yes, live today (push_workout) |
| Edit an existing planned workout | Coming soon, not live (updateTrainingPlan) | Yes, live today (edit_workout) |
| Delete a planned workout | Not available | Yes, live today (delete_workout) |
| Write wellness data back to your account | Not available | Yes (push_wellness) |
| Update completed activity metadata | Not available | Yes (update_activity) |
| Update sport zones / thresholds (FTP, LTHR, etc.) | Not available | Yes (update_sport_settings) |
| Devices covered | Coros only | Garmin, Coros, Wahoo, Suunto, Zwift, Amazfit, HUAWEI Health (Polar: activity sync, no workout push) |
The pattern is fairly clean: Coros MCP currently goes deeper on raw daily health data (detailed HRV and stress curves, menstrual cycle tracking, which IcuSync doesn't touch at all), while it has no power analytics and no write capability yet. IcuSync's strength is the opposite: power-duration curves, climb and ride-pattern analysis, and a full set of write tools that already work today, across seven device ecosystems rather than one.
What Intervals.icu adds
Coros is already an official supported sync partner for Intervals.icu, so your data flows over automatically through native device sync, no Strava workaround needed, no manual export.
Once it's there, you get:
- A real power-duration curve for both running and cycling
- One unified training history, even if you've owned different watch brands or train across multiple platforms
- A more detailed structured workout builder, syncing structured workouts to Garmin, Coros, Wahoo, Suunto, Zwift, Amazfit and HUAWEI Health via Intervals.icu, not just one brand. Polar activity sync is supported, but workout push isn't available for Polar.
- A single dashboard for wellness and training data instead of splitting between app and web
And if you want an AI assistant that can build a workout and actually push it to your Coros calendar today, rather than waiting for a promised update, that's what IcuSync (a connector between Claude and Intervals.icu) is built for. It works on Claude's free plan, not just a paid tier, and it isn't tied to one watch brand.
What IcuSync actually is, and how to try it
IcuSync is a connector that links Claude directly to your Intervals.icu account. Once it's connected, you can ask Claude to look at your actual training data, power curve, fitness trend, recent workouts, and build or adjust a workout in plain language. The part that matters most: Claude can then push that workout straight to your Intervals.icu calendar, and from there it syncs to your watch through Intervals.icu's normal device sync, including Coros.
It costs about $20 USD a year. There's no separate app to install and no coaching logic baked in, it just hands your data to Claude and lets Claude reason about it, the same way you'd talk through your training with a coach.
Getting set up as a Coros user takes three steps:
- Make sure Intervals.icu is connected to your Coros account (Coros lists Intervals.icu as an official supported third-party app, so this is a normal connection, not a workaround)
- Connect IcuSync to Claude, works with any Claude plan, including free
- Ask Claude something like "build me a threshold workout for Thursday and add it to my calendar", it pushes to Intervals.icu, which syncs it to your Coros watch
So, is it worth adding?
If you're happy with EvoLab's pace-based zones, stay on one platform, and don't need cross-device history, Training Hub alone is a solid, free setup. Keep it simple.
If you train by power, have switched devices over the years, coach athletes on mixed hardware, or want an AI assistant that can actually write a workout to your calendar rather than just describe one, that's where Intervals.icu earns its place on top of what Coros already gives you.