TEMPO

MCP & BYOK

TEMPO exposes a Model Context Protocol (MCP) server that lets you connect your own AI assistant (including Claude) directly to your training data.

What is BYOK?

BYOK (Bring Your Own Key) means you supply your Anthropic or OpenAI API key. TEMPO never stores it beyond your session; it passes the key at request time so your key, your billing, your data.

Setting up MCP

  1. Go to Settings → Integrations → MCP.
  2. Paste your Anthropic API key and click Save.
  3. Copy the generated MCP server URL.
  4. In Claude Desktop, add the server URL under Claude → Settings → MCP Servers.

TEMPO will appear as a connected data source. You can then ask Claude questions like:

  • "How has my running economy trended over the past 8 weeks?"
  • "Show me my best 20-minute power efforts this year."
  • "What does my week look like and am I recovered enough for tomorrow's long ride?"

What the MCP server exposes

  • Activity history with metrics (HR, power, pace, TSS)
  • Current fitness and readiness scores
  • Season plan structure and upcoming workouts
  • Per-sport zones and threshold values

Security

The MCP connection is read-only by default. Write operations (scheduling, notes) require explicit opt-in in Settings. Your data never leaves TEMPO's servers. The AI assistant queries the MCP endpoint the same way a web browser would.