Logo Transition
Quay lại Blog

Cập nhật sản phẩmĐọc 4 phút

Transition × Claude: Your AI Coach, Now Inside Claude

Connect Transition to Claude as a custom connector. Bring your training plan, workouts, and fitness metrics into your conversations with 28 explicit tools and secure OAuth.

Alex Wormuth

Alex Wormuth

Transition's Model Context Protocol (MCP) server lets you connect Transition to Claude as a custom connector and bring your training plan, performance metrics, and recovery data into your conversations. It now exposes 28 individually defined tools with OAuth sign-in.

This post is for athletes who use Claude for other stuff — research, writing, planning their week — and have thought "wouldn't it be nice if it knew my training context too." It does now.

Why this matters

Coaching conversations don't happen in a vacuum. When you ask "should I push this weekend?", the answer depends on: what's on your calendar, how your fitness has trended the last 12 weeks, your TSB today, whether you slept, whether your knee's been bugging you, and what your A-race is. Those lives in Transition. Until now, if you wanted Claude's help making that call, you had to paste data in manually.

MCP changes that. Claude can now fetch any of those signals directly from Transition, on demand, scoped to your account, securely. You stop being a copy-paste proxy between two tools.

What you can actually do

Ask what's on the plan — and whether you should do it

Claude shows today's workout alongside a CTL/ATL/TSB fatigue check

Ask Claude "what's my workout today? Am I fatigued?" and it pulls both the session from your plan and your PMC numbers in one turn. You get the same fatigue-aware answer your coach would give — grounded in real data, not a guess.

See your week

Claude renders the weekly training plan in a clean table

get_week_plan returns the next seven days formatted. You can follow up with "tell me more about Wednesday's intervals" and Claude drills into the specific workout for segments, pace targets, and notes.

Track whether you're actually getting fitter

Claude explains 12-week CTL trajectory with real numbers

get_fitness_trends returns a fused 4-week training breakdown plus a 12-week CTL trajectory. No more "I think I'm getting fitter?" — Claude shows you the numbers: CTL delta, volume changes, threshold drift, FTP maintenance. Same signal your coach would use for a build-vs-plateau call.

Adapt the plan mid-block

Claude adapts the training plan after an injury, showing what changed

"I'm traveling this weekend — adapt my plan." When you explicitly request a plan change, Claude can trigger an adaptation, check when it finishes, and fetch the updated week. It's the same adaptation engine that runs in the Transition app.

Generate a workout on demand

Claude generates a 45-minute Zone 2 bike workout

Need a quick one-off without involving your plan? After connecting your account, ask "Generate a 45-minute Zone 2 bike workout I can do right now." This creates a standalone session without changing your training plan.

The full tool set

The connector exposes these 28 MCP tools, each with its own description and input schema:

  • Plan: get_todays_workout, get_week_plan, get_workout_details, adapt_plan, check_adaptation_status
  • Performance: get_fitness_metrics, get_fitness_trends, get_zones, propose_thresholds_from_test
  • Training history: get_training_history, get_activity_details, get_activity_streams, get_past_workout_analysis
  • Health & body: get_health_summary, get_recovery_status, get_body_metrics, get_nutrition_summary
  • Races: get_race_context, get_race_prediction
  • Docs: search_transition_docs
  • Workout sync: push_workout_to_garmin, push_workout_to_zwift, push_workout_to_wahoo, push_workout_to_suunto, push_workout_to_coros, push_workout_to_rouvy, push_workout_to_opencycle
  • Standalone workout: generate_workout

Claude picks the tool for your request. Workout sync requires the corresponding provider to be connected in Transition. Plan adaptation and workout sync change data; the other tools read information or generate a standalone workout. Threshold proposals do not change your saved settings.

How to connect

  1. Open Claude → Settings → Connectors → Add custom connector.
  2. URL: https://mcp.transition.fun/mcp
  3. Sign in with your Transition account on the consent page.
  4. Click Approve and connect.

Once connected, enable Transition in a Claude conversation to use its 28 tools. Available data depends on your Transition account and connected services. Revoke anytime from Settings → API Keys in the Transition app.

How it's built (for the curious)

The MCP server is a small Go service that proxies tool calls to the existing Transition API with the user's OAuth-issued access token. No new databases, no shared session state, no user data stored on the MCP side — every call flows through the same auth, rate limits, and subscription gating the mobile app uses.

OAuth runs stateless: authorization codes are signed JWTs with a 60-second expiry, DCR client secrets are deterministic HMACs of the client ID, PKCE is enforced at the token endpoint. Your access token is a scoped Transition API key with a 90-day lifetime — rotate it anytime.

Everything is open-ish: the MCP server source and SKILL.md are on GitHub if you want to see the tool definitions or self-host a variant.

Feedback

This is v1. If you connect Transition in Claude and hit a rough edge — a tool that doesn't return what you expected, a missing capability, a latency spike — tell us at alex@transition.fun. We'll ship fixes fast.

More integrations coming.

Alex Wormuth

Tác giả

Alex Wormuth

Triathlete Ironman, kỹ sư phần mềm và nhà sáng lập Transition.

Về Transition

Bắt đầu dùng thử miễn phí.

Tải app. Tập thông minh hơn. Thi nhanh hơn.

Bắt đầu dùng thử miễn phí