Use TriPaced from Claude.
Strava knows what you did. TriPaced knows what to do next.
Plug TriPaced into Claude (or any MCP client). Ask in plain English. Claude reads your real training state and prescribes the next move.
What you can ask
Six concrete questions Claude can answer once it's plugged into your plan, your thresholds, and your real history.
How it works
- Connect TriPaced MCP in Claude. Add TriPaced as a connector in claude.ai. One URL, one token. TriPaced account required (beta open).
- Ask in plain English. No command, no syntax to learn. Claude picks the right tools on its own.
- TriPaced reads your training state and prescribes the next move. Glass-box methodology: Banister load (CTL/ATL/TSB) explained, physio guard-rails hardcoded, long-course specific (70.3 and full Ironman).
What's exposed
Five read tools, no athlete identifier to pass — the server is bound to your account on the server side.
get_week · get_zones · get_progression · get_athlete_state · get_adaptation_history
Your planned week, derived thresholds (FTP, run threshold pace, swim CSS), progression toward the race, your Banister state (CTL / ATL / TSB), and the adaptation history.
Write tools (move_session, swap_sessions, etc.) are gated behind a separate token for now — internal dogfood only. Public wave 2 in Q3 2026.
FAQ
Do I need a TriPaced account?
Yes. The beta is open — apply in two minutes, we review every application by hand, and you'll hear back within 7 days.
Do I need Claude Max?
Any Claude plan that supports connectors works (Pro, Team, Enterprise, Max).
Can ChatGPT, Cursor, or Codex use it?
Yes. TriPaced exposes a standard MCP server — any MCP-compatible client (ChatGPT desktop, Cursor, Codex, Claude Code, etc.) can connect.
Is my data shared with Anthropic?
No. Your data stays in TriPaced. Claude only sees the tool outputs you trigger — no export, no caching on Anthropic's side.
Apply for beta access.
Free during the test phase. We review every application by hand. Reply within 7 days.
Apply for beta →