Setup & Connection

The MCP Server uses OAuth 2.0 with PKCE for authentication. Most AI clients handle this automatically — you just paste the server URL and authorize with your Braking Lab account.

Server URL

https://mcp.brakinglab.com/mcp

Claude Desktop

1. Open Claude Desktop settings
2. Go to MCP Servers
3. Click Add Server and paste the server URL
4. When prompted, authorize with your Braking Lab account
5. Start chatting — Claude now has access to your racing data

Configuration file (claude_desktop_config.json):

{
  "mcpServers": {
    "braking-lab": {
      "url": "https://mcp.brakinglab.com/mcp"
    }
  }
}

Cursor

1. Open Settings → MCP
2. Click Add new MCP server
3. Set type to streamable-http
4. Paste the server URL: https://mcp.brakinglab.com/mcp
5. Authorize when the OAuth window opens

Windsurf

1. Open Settings → MCP Servers
2. Add a new server with the URL: https://mcp.brakinglab.com/mcp
3. Complete the OAuth authorization flow

ChatGPT

ChatGPT supports direct MCP connections via Developer Mode (Pro, Plus, Business, Enterprise, or Education accounts).

1. Open Settings → Apps → Advanced settings
2. Enable Developer mode
3. Go to Settings → Connectors
4. Click Create and paste the server URL: https://mcp.brakinglab.com/mcp
5. Follow the OAuth flow to authorize with your Braking Lab account
6. Start a new conversation — ChatGPT now has access to your racing data

Custom Clients

The server implements standard discovery endpoints:

Endpoint	Purpose
/.well-known/oauth-authorization-server	OAuth metadata (RFC 8414)
/.well-known/oauth-protected-resource	Resource metadata (RFC 9728)
/oauth/register	Dynamic client registration
/oauth/authorize	Authorization endpoint
/oauth/token	Token endpoint

Any MCP client that follows the standard can discover and connect automatically.

Authentication Flow

1. Client registers via /oauth/register (one-time, automatic)
2. Authorization Code + PKCE: client redirects to Braking Lab consent page
3. User approves: grants the AI access to their data
4. Token exchange: client receives access + refresh tokens
5. MCP connection: client calls POST /mcp with Bearer token

Tokens refresh automatically. You only need to authorize once per client.

Troubleshooting

”Unauthorized” or 401 errors

• Re-authorize your AI client — your token may have expired
• Check that you’re using the correct server URL (with /mcp path)

“Connection refused”

• Verify you have an active internet connection
• Check the server status

”No data found”

• Ensure you have telemetry sessions synced via Capture
• The MCP Server only accesses data from your authenticated account

AI can’t find tools

• Some clients cache tool definitions. Try disconnecting and reconnecting
• Ensure the server is listed as active in your client’s MCP settings