Connect Claude or ChatGPT to your training data
Tempo runs a hosted Model Context Protocol server. Add it as a connector and your assistant can read your training history, fitness, wellness and fueling — and write back to your plan. No exporting, no pasting screenshots into a chat window.
What you can ask
The useful questions are usually the ones that span two or three things at once — the kind that are tedious to answer by clicking between screens.
“Why did my HRV tank after Tuesday's ride?”
Reads Tuesday's workout in full — duration, intensity, zone distribution, training stress — then the wellness series around it, and your fueling that day. The answer usually lives in the interaction between those three, which is exactly what gets lost when you screenshot one chart into a chat.
“Schedule next week's intervals.”
Fetches Tempo's cycling plan-building protocol, checks your current form and what is already on the calendar, then writes the sessions into next week. They appear in Tempo and sync to your head unit.
“Am I building fitness or just accumulating fatigue?”
Reads the Fitness (CTL), Fatigue (ATL) and Form (TSB) series alongside ramp rate and monotony, and reads them together — a rising load with flat fitness is a different problem from a rising load with rising fitness.
“I signed up for a gravel race on May 3rd. Add it and build the block backwards from there.”
Creates the event, then schedules the workouts leading into it against the plan-building protocol and your current fitness.
“I'm in Girona for ten days from the 14th. Mark it and move my hard days around the travel.”
Writes a calendar note for the trip, then reschedules the affected sessions rather than leaving you to drag each one.
“Was I under-fueled last week?”
Reads nutrition intake against the week's training demand and the energy-availability series — the screening most training platforms have no data for at all.
“That last ride felt like an 8. Log it and tell me if that's a bad sign.”
Writes the RPE against the workout, then compares your reported effort to the measured load. A session that felt much harder than it scored is a signal worth catching early.
What it can read
Everything Tempo holds about your riding and recovery — so an assistant reasons from the whole picture, not one chart.
Workout history
Every synced ride and session, and the full detail of any one of them — power and heart-rate streams, zone distribution, laps, training stress.
Fitness and form
The daily training-load series: Fitness (CTL), Fatigue (ATL), Form (TSB), acute-to-chronic ratio, ramp rate, monotony. This is what turns “am I building fitness or just tired?” into an answerable question.
Performance ceilings
Critical power and W′, power bests across durations, and cardio bests for a period — the numbers behind a threshold conversation.
Wellness
Sleep, resting heart rate, HRV, weight and the rest of the daily recovery picture, from whichever wearable you have connected.
Nutrition and fueling
Daily intake against demand, plus the fueling plan for a specific session or an upcoming event.
Energy availability
The daily energy-availability series Tempo screens low energy availability from — the piece most training data leaves out entirely.
Athlete profile
Body and metabolism, current thresholds, heart-rate zones, and fueling preferences, so an assistant is reasoning about you rather than about a generic rider.
The calendar ahead
Planned workouts already scheduled, your workout template library, races and goal events, and the notes that explain a gap — travel, illness, a week off.
Tempo's plan-building protocols
The rules Tempo itself uses to build a training block, for cycling and for strength. An assistant fetches these before it plans, so what it schedules follows a coherent method instead of whatever it recalls about periodization.
What it can change
Writes are scoped to your plan and your calendar. Measured data — the power file from this morning's ride, your synced wellness history — is read-only through the connector; the one exception is the subjective feedback you would otherwise type in yourself.
Planned workouts
Schedule a session, move it, change its intervals, or delete it. This is a real training plan being written, not a suggestion pasted into chat — and it pushes out to your connected head unit like any workout you built in Tempo.
Races and goal events
Add the event you just signed up for, correct its date or priority, or drop it when plans change. The plan around it moves accordingly.
Calendar notes
Block out a holiday, flag a travel week, record an illness or an injury — the context that explains why a week looks the way it does.
Post-workout feedback
Log RPE, how a session felt, and carbohydrate intake against a completed ride. The only write that touches finished workouts — measured data stays read-only.
Both assistants ask before running a tool unless you have told them to always allow it, and each keeps a per-tool permission list you can narrow. Anything an assistant creates is an ordinary Tempo object afterwards — editable and deletable in the app like anything you made yourself.
Tempo
Privacy Policy•
Cookie Policy•
Terms of Service•
ContactCopyright © 2025–2026 Tempo Training LLC