Connect TrainerRoad to Claude Code
Yes. Connect TrainerRoad in the Memory.fit app, add one Memory.fit address to Claude Code, and Claude Code reads your planned workouts by date, workout name and planned duration.
Claude Code can also write your plans back to Memory.fit, where you see them in the app.
What Claude Code needs: on a computer, Claude Code, about a minute.
1:27 · On YouTube soonThe whole setup in 1:27. The chats in it are examples: Claude Code's answers depend on your data.
- 0:00Connect your TrainerRoad calendar
- 0:27Add Memory.fit to Claude Code
- 0:56Ask Claude Code and fuel around TrainerRoad
The address to add to Claude Code
https://api.memory.fit/mcp?src=mcp-trainerroad-claude-codeMCP address: https://api.memory.fit/mcp
What it reads
What Claude Code reads from TrainerRoad
Through TrainerRoad's calendar link, pasted into the Memory.fit app.
- Planned workouts by date
- Workout name
- Planned duration
- Planned TSS and intensity factor, when TrainerRoad includes them
The tools that read it:get_workoutsget_training_planget_day
What it can do
What Claude Code can do with it
- Plans written back
- Yes. Claude Code reads your training and writes the sessions it plans back to Memory.fit, asking before each change unless you allowed it.
- Where it runs
- Your terminal, on a computer.
- Good to know
- Claude Code adds Memory.fit with one command in your terminal and signs in from /mcp. It reads your TrainerRoad workouts there, and before it changes your plan it asks for your yes; once you allow it, it shows on Plan in the Memory.fit app, next to your TrainerRoad workout.
Setup
Set up TrainerRoad in Claude Code
1. TrainerRoad in the Memory.fit app
- 01On trainerroad.com, open Profile → Calendar Sync and copy your Calendar URL.
- 02In the Memory.fit app, open Settings → Health data → TrainerRoad.
- 03Paste the link and tap Connect.
- 04Memory.fit checks your calendar every hour. Moved or removed workouts follow.
2. Memory.fit in Claude Code
Claude CodeOn a computer · Claude Code · about a minute
- 01In your terminal, run the command
- 02Start Claude Code and run /mcp
- 03Pick memory-fit and sign in to Memory.fit
claude mcp add --transport http memory-fit "https://api.memory.fit/mcp?src=mcp-trainerroad-claude-code"Other routes
TrainerRoad in Claude Code without Memory.fit
TrainerRoad has no official route to Claude Code.
Try it
Ask Claude Code about your TrainerRoad data
“Read my TrainerRoad workouts for next week and tell me which days need the most fuel.”
Uses:get_workoutsget_day
“Which of next week's TrainerRoad workouts are the longest, and when are they?”
Sunday's endurance ride, 2 h at 09:00, is the longest. Thursday's sweet spot comes next, 1 h 30 at 18:00. Everything else is an hour or less.
From the video. Answers depend on your data.
Uses:get_workouts
“Fit two easy runs around my TrainerRoad plan this week.”
Uses:get_workoutsplan_session
“Plan my fuel and meals for Saturday around my TrainerRoad workout.”
Planned. Saturday: 2,450 kcal with 330 g of carbs, a last meal at 16:00 before Pettit at 18:00, and a recovery dinner at 19:30. It's on your Plan.
From the video. Answers depend on your data.
Uses:get_workoutsset_day_targetsset_meal_plan
Limits
Limits, said plainly
- The calendar link carries planned workouts only. A ride you finish reaches your AI when a head unit or watch you connect to Memory.fit recorded it too.
- TrainerRoad sends finished rides to Garmin Connect and Strava. Strava's copy never reaches your AI, and we don't count on the copy it uploads to Garmin Connect.
- Memory.fit checks your TrainerRoad calendar every hour, so a moved workout follows within the hour.
- Your AI's own subscription is separate from Memory.fit's.
Questions
TrainerRoad in Claude Code, in short.
Not from TrainerRoad. Memory.fit is a hosted MCP server: connect TrainerRoad in the Memory.fit app, add one Memory.fit address to Claude Code, and Claude Code reads it.
Memory.fit is $9 a month or $69 a year, with 7 days free, for every device and every AI you connect. Claude Code's own plan, if it has one, is separate.
Memory.fit works in every country, and Claude Code's requirements name no region.
Claude Code gets only the permissions you allow, every change shows in the Memory.fit app with who made it, and you can disconnect Claude Code or TrainerRoad at any time.
Yes, by default. When Claude Code wants to write a session or a target to Memory.fit, it shows the request and waits for your yes, unless you allowed Memory.fit's tools for the session.
Keep going
More on TrainerRoad and Claude Code
- TrainerRoad MCP: every AI
- What Memory.fit reads from TrainerRoad
- Claude Code and Memory.fit
- Set up Claude Code on a computer
- Connect TrainerRoad to ChatGPT
- Connect TrainerRoad to Claude
- Connect TrainerRoad to Grok Bot
- Connect TrainerRoad to Muse
- Connect TrainerRoad to Dots
- Connect TrainerRoad to Grok
- Connect Garmin to Claude Code
- Connect Apple Health to Claude Code
- Connect WHOOP to Claude Code
- Connect Oura to Claude Code
- Connect COROS to Claude Code
- Connect intervals.icu to Claude Code
- Connect Samsung Health to Claude Code
- Connect Health Connect to Claude Code
- Connect Apple Watch to Claude Code
- Connect Polar to Claude Code
- Connect Suunto to Claude Code
- Connect Wahoo to Claude Code
- Connect Withings to Claude Code
- Connect Hevy to Claude Code
- Connect TrainingPeaks to Claude Code
- Connect Zwift to Claude Code
- Connect Concept2 to Claude Code
Checked on November 3, 2026 by the Memory.fit team.
Your next chapter starts with everything you've learned.
On Android now. iPhone is coming: join the waitlist and we'll email you the day Memory.fit is on the App Store.
No spam. One email when it's ready.