IcuSync - Claude AI MCP connector for Intervals.icu (no technical setup required)

AI Tools
21

Hi Shan,

Thanks for the feedback, really appreciate it!

Cadence : Claude can now see your cadence data and compare how it changes at different paces across runs (and RPM vs power for cycling too).

Miles : this should now be fixed automatically. Claude will detect your unit preference from your intervals.icu profile without needing to add anything to project instructions.

Both updates are live, start a fresh conversation and give it a try!

Thank you,
Toby

22

Quick update: new tool added

IcuSync now has a get_power_curves tool, bringing the total to 12 tools.

You can now ask Claude things like:

  • “Show me my run power curve for the last 90 days”
  • “How does my current season cycling power curve compare to last season?”
  • “Where are my weaknesses on the bike based on my power curve?”

The tool supports flexible time periods including rolling days (e.g. 90d), seasons, or a custom date range. It returns your best power across 12 key durations from 5 seconds to 2 hours, along with CP and FTP model estimates.

To pick up the new tool, disconnect and reconnect IcuSync in your Claude, then start a fresh conversation.

23

Hi! Hi! This is a really interesting tool. I bought a subscription: [email protected]

1 Like
24

After configuring the connector, what do I need to do to, for example, get a report on the current form?

25

Hello,
Is Claude able to analyse lap by km from a running session when we have a continue run without laps.
Example today I did a 8 km MAF test. I can not analyse the test km by km as intervals.icu does not generate 1 km lap.
My little experience with ChatGpt intervals.icu shows that IA is not able to retrieve the run data km by km.

1 Like
26

Hi Toby,

This looks like a interesting project! As an Intervals.icu user, the idea of having an MCP connector for Claude sounds like a huge workflow improvement.

I’m very interested in trying it out. Would it be possible to get free test access to put it through its paces and see how it works with my data?

Looking forward to hearing from you and thanks for building this!

Best regards, Pavel

1 Like
27

Thanks Vladimir, welcome aboard! Once the connector is set up, just ask Claude something like “give me a summary of my current fitness” or “what does my training look like this week?” and it will pull your data from intervals.icu and respond. If you want more ideas, there are example prompts on the IcuSync website at icusync.icu. Looking forward to hearing how you go.

1 Like
28

Hi Pavel, thanks for sign up, it’s done, looking forward to hearing how you go. Thank you

29

Hi, good question. IcuSync does return km-by-km data for continuous runs. intervals.icu auto-generates 1 km splits in the background even when you have no manual laps, and the get_activity_detail tool surfaces those as individual intervals with pace, heart rate, power, and cadence for each km. So for your 8 km MAF test, Claude would be able to show you how your HR and pace changed across each kilometre. Give it a try with something like “analyse my MAF test from today km by km.”

30

Hi @TobyPattullo ! Is it possible to get elevation data from intervals? I would like to see the gradient of each of my intervals

32

Hi Mattics,

Elevation gain per interval is already available in IcuSync so Claude can calculate the gradient for each interval automatically.

Try asking something like: “Show me the elevation gain and gradient for each interval in my last ride”

A full altitude profile (the shape of the climb metre by metre) is something we’ve considered but decided not to include for now as it would significantly impact performance.

33

Hi Toby! This is what im getting when im typing in the sentence you mentioned. Does it matter if it’s a run or ride? I’m trying get details for a run.

" IcuSync doesn’t return elevation gain or gradient per interval — confirmed from the raw data above. FIT file is the only reliable path.

To get true per-interval gradient you’d need to parse the altitude stream against lap splits from the Garmin FIT export. Want me to write a script that does that?"

Earlier, when I asked it to pull the run details of the latest run, it did say this so I do know that it sees the overall grade

“Short run, minimal elevation (+45ft) — power numbers unaffected by grade”

34

Hi Mattics,

Claude gave you incorrect information there — elevation gain per interval is definitely available in IcuSync. I just tested it and it’s coming through correctly for runs.

Here’s a real example from my 50km trail run, IcuSync can show elevation gain and calculate gradient per interval like this:

Interval Type Distance Elevation Gradient Pace
5 Climb 1.51km +75m 5.0% 6:25/km
8 Climb 4.70km +472m 10.0% 10:30/km
12 Rolling 5.56km +111m 2.0% 6:39/km
14 Long section 19.95km +122m 0.6% 6:12/km

Try asking: “For each interval in my last run, show me the elevation gain, distance, and calculate the gradient as a percentage”

Claude will calculate the gradient automatically from the elevation and distance data.

Cheers,
Toby

35

Hi Toby - I have had IcuSync create my cycling workout, starting with a ramp test (yay :frowning: ) to sanity check my FTP. It was able to see the workout once I completed and uploaded to Intervals, but I had to guide it through a few steps that you might be able to clean up:

  1. It wanted to use a calculation of 90% of the last step completed when the standard model is 75% (Ramp Test Makes FTP Testing More Efficient and Less Stressful). IcuSync agreed with me that 75% was better once I suggested it consider the standard, but you might be able to bias it that way to start.
  2. It offered to update my FTP in Intervals, so I gave it permission to proceed. It then came back and confessed that it can’t actually do that (not a big deal). Can you either prompt it to lead with not being able to adjust those values or give it the ability to do so? The first is probably the smarter path.
1 Like
36

Tnx, all is ok!

1 Like
37

Hi Dave,

Great feedback, both fixed:

Ramp test calculation : Claude will now use 75% of best 1-minute power as the standard formula from the start, no need to correct it.

FTP update : IcuSync is read-only for training settings so Claude can’t write back to intervals.icu. It will now tell you upfront rather than offering to do something it can’t. To update your FTP manually: intervals.icu → Settings → Cycling → update FTP.

Start a fresh conversation and it should behave correctly on both.

Thank you,
Toby

38

Thanks!

Heh - one Ramp Test a quarter is enough for me! I’ll check it after I finish this plan.

1 Like
39

I’m not able to make the connector work. I’ve added the connector and used the MCP URL as detailed in the instructions, yet when I try to use it in a conversation this is what I get:

I can see the IcuSync connector in your account, but it’s currently not connected and its tools aren’t enabled in chat. I’d need to connect it first before I can access any data through it.

If I click the “Connect” button I just get the “couldn’t reach the MCP server” error, and nothing changes.

For reference, I have created the connector naming it “IcuSync” and copy-pasting the MCP URL provided in the IcuSync webpage. I have not configured the optional OAuth parameters.

40

Nevermind, I figured this out. I had inadvertently misconfigured the intervals.icu API integration.

41

Glad you got it sorted! If any part of the setup felt confusing let me know, always looking to improve the instructions.