Most of us already have an AI assistant open somewhere: Claude in a browser tab, ChatGPT on the phone, Cursor in the editor. Until now, if you wanted one of them to reason about your training, you had to become the go-between. Copy your readiness number out of IntervalCoach, paste it in, add some context, and hope you didn't leave out the thing that mattered.
Today that stops. You can connect IntervalCoach directly to Claude, ChatGPT or Cursor, and the assistant reads your training for itself.
It reads your engine, not a search result
This is the part that matters. A general AI assistant knows the textbook: it can tell you what a VO2max block is or how sleep affects recovery in the abstract. What it can't know is you. That's what the connection gives it.
Once you've linked your account, the assistant reads the things our engine has computed specifically for you:
- Your readiness, measured against your own baseline. Not a population average, your resting heart rate, HRV and sleep compared to your normal, with how you feel folded in.
- Your personal recovery curves. IntervalCoach learns how fast you clear different kinds of training stress, and how that changes as you get fitter. The assistant can see where you are on your own curve after Tuesday's intervals, not a generic 48-hour rule of thumb.
- Your adaptation and early-warning signals. The same signals we watch for the drift that shows up before you feel run down, or a resting heart rate creeping up before an illness lands.
- Your plan, your load target, your fitness trend. Where you are in the block, how the week is tracking, and the CTL/ATL/TSB story underneath it.
So when you ask "am I ready for a hard session tomorrow," the answer isn't a guess from general knowledge. It's your data, your curves, your baseline, read live.
The real power is what it connects to
Here's the thing about MCP: your assistant is almost never connected to only IntervalCoach. It's also connected to your calendar, your email, Slack, your notes. The moment your coaching brain sits in the same room as those tools, the assistant can do things neither side could do alone. It reads your training from us and acts through everything else you've connected.
Genuine examples, each spanning two or more tools:
- Training + calendar. "Look at my readiness and my plan for the week, then find the two days around my meetings that best fit my hard sessions, and block them in my calendar." Your assistant reads the load from us and writes the events through your calendar tool.
- Training + Slack. "Every morning, post my readiness score and today's session to my personal Slack channel, and flag it if we eased the workout overnight." A daily standup for your body, in the place you already check first.
- Training + email. "Draft an email to my coach summarising this week: what I did, how I recovered, and where my form is heading into the race." It pulls the real numbers and the recovery picture; you just hit send.
- Training + travel. "I'm flying to Denver on Thursday for ten days at altitude. Given where I am in my plan and how I've been recovering, suggest how to adjust that block, and add the sessions to my calendar."
- Training + notes. "Pull my last six weeks of workouts and my fitness trend into a Notion page I can share with my physio before Friday's appointment."
You're not copying numbers between apps anymore. You describe the outcome you want, and the assistant orchestrates it: IntervalCoach supplies the coaching intelligence, your other tools supply the reach.
Why we built it on MCP
MCP, the Model Context Protocol, is the open standard that makes all of the above possible. It's how assistants connect to live tools, and it's why IntervalCoach can sit alongside your calendar and Slack in the same conversation instead of on an island. We chose it on purpose: any client that supports MCP can connect, so you're not betting on us picking the winning assistant, and as more tools adopt it, they compose with your training automatically.
It also keeps you in control. You connect by signing in with your own account, the assistant only sees what your account can see, and you can disconnect at any time. Nothing moves without you asking for it first.
Coach+ is still the home ground
To be clear about where this fits: Coach+, the coaching chat built into IntervalCoach, isn't going anywhere, and for most people it's still the best place to talk training. It knows the full picture and it's tuned for exactly this.
The MCP connection is for the moments you're already somewhere else. You're deep in a ChatGPT conversation, or writing in Cursor, and you don't want to break your flow to switch apps. Now you don't have to. Your coach comes to the conversation you're already in.
How to connect
It takes a couple of minutes. In your assistant's connector settings, add the IntervalCoach server address:
https://www.intervalcoach.app/api/mcp
Sign in with your IntervalCoach account when prompted, approve the connection, and you're done. The step-by-step setup guide walks through each assistant.
The MCP connection is available on the Max plan. It's the same coaching toolset that runs Coach+, now reachable from the assistant you already keep open.
Give it a try, point Claude or ChatGPT at your own training, and tell me what you end up asking it. That's the part I'm most curious about.
— Martijn