How to Integrate Claude With Strava for AI Training Plans

Your Strava feed is a goldmine of training context: every ride, run, and swim, with distance, duration, pace, power, and heart rate. It's the perfect raw material for an AI coach. The catch is that Claude can't log into Strava and read it for you — there's no built-in connection between the two. So "integrate Claude with Strava" really means one of two things, and this guide covers both.

The honest version up front: Strava is a source for analysis, not a destination. You don't upload training plans back to Strava — you use your Strava history to inform a smarter plan, then send that plan to TrainingPeaks, Intervals.icu, or your calendar.

Path A: Bring Your Strava Data to Claude Manually

If you want to drive the conversation yourself, you can feed Claude a summary of your recent Strava activity and let it build from there.

1. Pull a summary of your recent activities

You don't need to paste raw GPS files — Claude reasons best from a clean summary. Grab the last 4–8 weeks from your Strava training log and condense it: date, sport, duration, distance, and any power or heart-rate averages you care about. A simple weekly rollup works great too.

Example summary you paste into Claude:

Last 6 weeks (run + bike):
- Wk1: 4 runs / 32km, 2 rides / 3h. Longest run 12km.
- Wk2: 5 runs / 41km, 1 ride / 1.5h. Longest run 15km.
- Wk3: travel - 2 easy runs / 14km only.
- Wk4: 5 runs / 46km, 2 rides / 4h. Longest run 18km.
- Wk5: 5 runs / 44km, 3 rides / 5h. Some Z4 intervals.
- Wk6: 4 runs / 38km, 2 rides / 3.5h. Legs felt flat.

2. Ask Claude to analyze, then plan

Prompt:

"Based on this Strava history, assess my recent volume,
sport balance, consistency, and likely fatigue. Then build
an 8-week plan toward a half marathon on November 9th.
Keep my long run progression realistic given what I've
actually been doing. Output as CSV with columns:
day,sport,subtype,title,duration_minutes,tss,description,phase"

Because you've grounded Claude in real numbers, the plan won't prescribe a 26km long run next week when your longest this month was 18km. That's the whole point of using history instead of a blank prompt.

3. Get the plan onto your calendar

Take Claude's CSV to TrainingDojo's importer, connect TrainingPeaks or Intervals.icu, set your start date, and import. If you're on Intervals.icu, the Intervals.icu CSV import guide walks through it; for TrainingPeaks, see the bearer token guide.

The Friction With the Manual Path

Path A works, but it has real limits worth naming:

• You do the data wrangling. Summarizing weeks of activities by hand is tedious and easy to fudge.
• It's a snapshot. The moment you train again, your pasted summary is stale.
• Detail gets lost. A hand-written rollup drops the nuance — interval splits, decoupling, how hard "hard" actually was.

That's exactly the gap the built-in path closes.

Path B: Let Coach Dojo Read Strava for You

TrainingDojo's Coach Dojo connects to Strava directly with read-only OAuth, so the AI sees your history without you copying a thing.

1. Open Coach Dojo and choose Strava as your history source.
2. Approve the standard Strava authorization screen (read-only; tokens are encrypted at rest).
3. Coach Dojo pulls your recent activity summaries and reads volume, sport mix, long-session durability, consistency, and a load trend.
4. It asks a few subjective questions Strava can't answer — your goal race, current fatigue, travel, injuries.
5. It generates a plan you can download, import to TrainingPeaks/Intervals.icu, or convert to structured workouts.

It's the same idea as the Claude workflow — history-grounded planning — but the analysis is automatic, detailed, and always current. Learn more about Strava data sync for AI coaching and how to connect Strava to Coach Dojo.

Which Path Should You Use?

• Use Claude manually when you enjoy steering the conversation, want to combine Strava context with your own notes, or like iterating on the plan in chat.
• Use Coach Dojo when you want the data work done for you and a plan that's already formatted for import.
• Honestly? Both. Let Coach Dojo establish the history-grounded baseline, then take the result into Claude if you want to debate the details.

The Bottom Line

Claude doesn't plug into Strava, but your Strava history is still the best fuel for an AI training plan — whether you summarize it into Claude yourself or let Coach Dojo read it automatically. Either way the finished plan flows out to TrainingPeaks, Intervals.icu, or a CSV calendar, not back to Strava.

Prefer to start from a structured platform instead? See how to integrate Claude with TrainingPeaks or integrate Claude with Intervals.icu, or read our take on the AI running coach for endurance athletes.