Train Ultra coach MCP

What this gives you

The MCP server exposes one tool: ask_train_ultra_coach. It asks your Train Ultra coach a question and returns the same kind of answer you would expect in the Train Ultra chat interface.

The tool uses your existing Train Ultra context, including workouts, goals, coach memory, wellness context when connected, and the same safety and confirmation behavior as coach chat.

It does not expose raw Strava, Garmin, Oura, GPS, stream, billing, or account tools to external clients.

Access

MCP access is available on Trial and Pro accounts, including comped or grandfathered Pro-equivalent accounts. Free accounts can read this guide but cannot create MCP tokens.

Tokens are personal. Treat them like passwords, and revoke any token you no longer use from Settings.

Create a token

Open Train Ultra Settings.
Select External AI on the web, iOS, or Android.
Create a labeled token, such as Claude Code on MacBook or Codex laptop.
Copy the token when it appears. Train Ultra only shows it once.
Paste it into your MCP client configuration.

Claude.ai / Claude chat

Claude custom connectors are the right surface for using Train Ultra inside Claude chat. Train Ultra V1 uses personal bearer tokens, while Claude chat custom connectors expect a cloud-reachable remote MCP server with OAuth for protected user data.

This means Claude.ai setup is OAuth next, not bearer-token ready today. Once Train Ultra ships OAuth for MCP, add it from Customize > Connectors > Add custom connector, name it Train Ultra, and use the server URL below.

Server URL: https://trainultra.app/mcp

Claude Work

Claude Work, Team, and Enterprise deployments use the organization connector flow. An owner adds Train Ultra under Organization settings > Connectors, and members connect their own Train Ultra account.

Like Claude chat, this requires OAuth for MCP before it can use private athlete data. The Train Ultra bearer token flow below works today in clients that can send a custom Authorization header.

Claude Code

Use the HTTP transport and pass your token as a bearer header.

claude mcp add --transport http train-ultra https://trainultra.app/mcp \
  --header "Authorization: Bearer tu_mcp_your_token_here"

ChatGPT

ChatGPT Apps and custom connectors are the right surface for using Train Ultra in ChatGPT. OpenAI requires OAuth-compatible MCP auth for protected resources, so Train Ultra V1 bearer tokens are not yet enough for ChatGPT web/chat.

Once OAuth is live, create a connector in ChatGPT from Settings > Connectors, use the Train Ultra MCP URL, complete the Train Ultra authorization flow, and confirm ChatGPT lists the ask_train_ultra_coach tool.

Server URL: https://trainultra.app/mcp

Codex

Codex supports Streamable HTTP MCP servers with bearer-token auth. Store your Train Ultra token in an environment variable so it does not land in source control.

export TRAIN_ULTRA_MCP_TOKEN=tu_mcp_your_token_here

[mcp_servers.train_ultra]
url = "https://trainultra.app/mcp"
bearer_token_env_var = "TRAIN_ULTRA_MCP_TOKEN"

VS Code

Add Train Ultra to your user or workspace mcp.json. Use an input variable so the token is prompted and stored by VS Code instead of committed to a project file.

{
  "inputs": [
    {
      "type": "promptString",
      "id": "train-ultra-mcp-token",
      "description": "Train Ultra MCP token",
      "password": true
    }
  ],
  "servers": {
    "trainUltra": {
      "type": "http",
      "url": "https://trainultra.app/mcp",
      "headers": {
        "Authorization": "Bearer ${input:train-ultra-mcp-token}"
      }
    }
  }
}

Cursor

Create or edit ~/.cursor/mcp.json for global access, or .cursor/mcp.json inside a project. Use environment interpolation so raw tokens do not end up in source control.

{
  "mcpServers": {
    "train-ultra": {
      "url": "https://trainultra.app/mcp",
      "headers": {
        "Authorization": "Bearer ${env:TRAIN_ULTRA_MCP_TOKEN}"
      }
    }
  }
}

Other MCP clients

Use Streamable HTTP with the server URL below and an Authorization bearer header. Clients that cannot send custom headers need OAuth support, which is the next Train Ultra MCP auth phase.

URL: https://trainultra.app/mcp
Header: Authorization: Bearer tu_mcp_your_token_here

Example questions

Ask my Train Ultra coach what to do with tomorrow’s planned workout after today’s hard run.
Ask my Train Ultra coach whether this week looks too aggressive.
Ask my Train Ultra coach to continue conversation conv_123 and help adjust my long run.

Troubleshooting

401 Unauthorized: check that the token was copied correctly and is still active.
403 Subscription required: the account no longer has Trial or Pro access.
429 Rate limited: wait a minute or reduce repeated tool calls.
No tools listed: restart the client or reset its MCP tool cache.
Wrong conversation: conversation IDs are user-scoped, so a token cannot continue another athlete’s thread.