If you have watched a video about using Claude AI for training analysis, there is a good chance it showed someone exporting their Garmin data, uploading the file to Claude, and asking for a training plan. It looks impressive. The AI reads your data and talks back to you like a coach who knows your history.

Then you try it yourself. And after a week or two, you quietly stop.

This article explains why that workflow has a ceiling, why local MCP installs are not the answer for most athletes, and what actually works long term.

The export workflow feels good the first time

The appeal makes sense. You grab a CSV or FIT file from Garmin Connect, drop it into Claude, and suddenly you have an AI that can see your heart rate, pace, cadence, and training load. You ask it to analyse your last month. It does. You ask it to suggest a workout for tomorrow. It does that too.

The problem is not the first conversation. The problem is everything after it.

Problem 1: Your data is always stale

Some people get around Claude's lack of memory by using a Project and pasting their training zones and background into the custom instructions. That helps with context. But it does not solve the core problem. Your fitness changes every day. The moment you finish a run, your export is out of date. Yesterday's fatigue levels, this morning's HRV, the session you just completed, none of that is in Claude unless you manually update it. And if your FTP or threshold pace changes after a test, you are editing your Project instructions by hand.

You end up maintaining a second version of your training data inside Claude. That is not AI coaching. That is data entry.

Problem 2: Claude can read but it cannot write back

Analysing your data is useful. But the thing that actually changes your training is having structured workouts land on your watch, ready to execute.

The export workflow is one-directional. Claude can tell you what to do. It cannot put that session on your Garmin. You are copying interval targets out of a chat window and manually building workouts in Garmin Connect or your training app. That gap between the plan and the watch is where most people give up.

Problem 3: Claude does not know your zones

A good training plan is built around your actual thresholds. Your FTP. Your threshold pace. Your heart rate zones. Without those numbers, Claude is guessing.

In the export workflow, you either paste your zones into every conversation manually or you accept that the sessions Claude writes back are generic. Neither is great. And if your FTP changes after a test, nothing updates automatically.

Problem 4: Local MCP installs are not built for athletes

Some tutorials go further and show you how to connect Claude directly to Garmin via an MCP server you run on your own computer. This is technically impressive and genuinely does more than the export workflow.

It also requires cloning a GitHub repository, running commands in a terminal, storing your Garmin credentials in a local config file, and keeping a process running on your machine every time you want to use it.

That is a reasonable setup for a developer. It is not a reasonable ask for a runner who just wants help with their training week.

Beyond the setup friction, these projects use Garmin's unofficial API. There is no guarantee it keeps working. Garmin has no obligation to support it, and it has broken before.

Problem 5: Claude has no tools to go deeper

When you upload an export file, Claude can only work with what is in that file. If it needs something else - your wellness data from this morning, your best efforts over the last six weeks, your upcoming race on the calendar - you have to go find it, export it separately, and upload it again.

A proper connection gives Claude tools it can call on demand. Need your current fitness and fatigue numbers? It fetches them. Want to know how last Tuesday's session compares to the same workout three months ago? It looks it up. The conversation drives what data gets pulled, not a file you prepared in advance.

Problem 6: The export workflow is desktop-only

You finish a hard session, you are still catching your breath, and you want to ask Claude what it means for the rest of the week. With the export workflow, that conversation does not happen until you are back at a computer, have downloaded your file, and uploaded it to Claude.

A remote MCP connection works wherever Claude works, on your phone, on a tablet, on any computer without installing anything. The data is always there because it lives in your training platform, not in a file on your desktop.

Why the intervals.icu path is different

Intervals.icu is a free training platform with a stable, documented public API and official sync partnerships with Garmin, Coros, Wahoo, Polar, Suunto, and others. Your device already syncs to it the same way it syncs to anywhere else. Nothing changes on the device side.

IcuSync connects Claude to your Intervals.icu account via MCP. One URL added to Claude. No install. No terminal. No stored passwords. Works on Claude web, mobile, and desktop on any plan including free.

Because the connection is persistent, Claude has access to your live training data every time you open a conversation. Your recent activities, your fitness and fatigue trends, your zones from your athlete profile - all of it is there without you doing anything.

And because IcuSync writes back to Intervals.icu, structured workouts Claude builds for you land on your calendar and sync to your watch automatically.

What this looks like in practice

You open Claude on a Tuesday morning and ask how your training load is sitting after last week. Claude checks your current CTL, ATL, and TSB and tells you.

You ask it to write a threshold session for Thursday using your actual pace zones. It does. The workout appears on your Intervals.icu calendar and syncs to your watch before you close the chat.

On Friday you tell Claude the session felt harder than expected. It looks at your wellness data from that morning sleep, HRV, resting heart rate and explains why.

None of that involves exporting a file, opening a terminal, or copying numbers between apps.

Getting started

You need a free Intervals.icu account with your device connected. If you are not already using it, setup takes about five minutes and your device will start syncing automatically.

Once that is in place, create an IcuSync account, connect your Intervals.icu account with one click, copy your MCP URL, and add it to Claude. The full setup is under five minutes.

The export workflow got you curious about what AI coaching could look like. This is what it actually looks like when it works.

Why the Garmin export and Claude workflow breaks down (and what to do instead)