How to Connect Claude to TrainingDojo MCP: Endurance Coaching Tutorial

TrainingDojo MCP turns Claude on the web or desktop into an endurance workflow that can read your real training history, inspect wellness and upcoming workouts, build structured sessions, and publish reviewed changes to TrainingPeaks or Intervals.icu. Claude opens TrainingDojo in your browser for a normal sign-in and permission screen, so no code or developer key is required.

Before You Connect

• An active TrainingDojo Pro subscription.
• At least one platform connected in Settings.
• The TrainingDojo MCP endpoint: https://trainingdojo.app/api/mcp.

Your TrainingPeaks, Intervals.icu, and Strava credentials stay encrypted in TrainingDojo and are never sent to the AI app. The normal browser flow does not require you to create or handle a developer key. The AI app and provider you choose handle all conversation inference and generation under your provider account. TrainingDojo MCP never calls TrainingDojo's AI models or uses TrainingDojo AI credits. TrainingDojo receives authenticated tool inputs and returns data or action results, not the rest of your provider conversation. TrainingDojo's separate web AI features remain TrainingDojo-hosted.

Connect TrainingDojo to Claude Web or Desktop

1. Open Customize → Connectors.
2. Choose +, then Add custom connector.
3. Paste https://trainingdojo.app/api/mcp and choose Add.
4. Sign in to TrainingDojo, review access, and choose Connect.

The connector is shared with your Claude account, so it works in Claude web and Claude Desktop. Enable TrainingDojo for a conversation from the + menu, then Connectors.

Advanced: Connect TrainingDojo to Claude Code

Claude Code also supports remote HTTP MCP servers with custom headers. Generate a developer key in the Advanced section of MCP setup, then run:

claude mcp add --transport http --scope user trainingdojo https://trainingdojo.app/api/mcp \
  --header "Authorization: Bearer <your-trainingdojo-key>"

In PowerShell, use the same command on one line:

claude mcp add --transport http --scope user trainingdojo https://trainingdojo.app/api/mcp --header "Authorization: Bearer <your-trainingdojo-key>"

User scope makes the connection available across your Claude Code projects. Use local scope if you only want it in the current project. Avoid pasting a real key into a shared project configuration.

Verify the Connection

claude mcp list

Start Claude Code and run /mcp. TrainingDojo should appear as connected with 26 tools. If it reports an authentication error, revoke the key in TrainingDojo, create a replacement, and re-add the server.

A Useful First Coaching Session

Start with a read-only check before asking the AI to write anything:

Use TrainingDojo to list my connected platforms. Then review my last
six weeks of training and my next 14 days. Summarize volume, intensity,
recovery signals, and the three biggest risks in my current schedule.
Do not change or publish anything yet.

Once the summary looks right, ask for a draft plan, review its dates and workload, and only then approve a publish tool. TrainingDojo labels read, write, and destructive tools; the AI client controls whether and when it asks for approval, so review that client's permission settings before enabling writes.

Why Claude Works Well for This

• Long conversations can combine history, constraints, event goals, and plan review.
• Claude can draft structured workout JSON, validate it, and let you review it before requesting a publish tool.
• The same conversation can compare completed work with the upcoming calendar and adapt the week.
• Workout Vault tools let Claude find and reuse sessions that already work for you.

Next Step

Open TrainingDojo MCP setup, connect your training platforms, and keep the first session read-only until you have reviewed what Claude found.