.md

MCP Setup

Install Race Engineer skills and connect the Braking Lab MCP in your AI assistant.

The Race Engineer connects to your Braking Lab account through the Model Context Protocol (MCP). The nine Race Engineer skills guide common tasks such as comparing laps, evaluating setups, and managing race events. You can still use the other actions available through the MCP without a matching skill.

For page-specific browser tools that need no server configuration, see WebMCP in the browser.

Claude Code plugin

Install the native plugin with Claude Code’s plugin manager:

claude plugin marketplace add r-bart/braking-lab-agent-skills
claude plugin install braking-lab-race-engineer@braking-lab

Open a new Claude Code session, run /mcp, and connect your Braking Lab account. The plugin contains all nine skills and the MCP connection. A clean installation from the public marketplace has been verified; a data-backed answer in Claude Code still needs validation.

Claude chat

If your Claude account offers plugin uploads, download the Claude plugin ZIP. In Claude, open Customize → Plugins → Add plugin → Upload plugin and import the ZIP. Then connect your Braking Lab account from Connectors. The plugin import and OAuth were verified on one account; the first data-backed answer remains unverified.

ChatGPT

The public ChatGPT directory listing is still being prepared. If your account offers custom MCP connectors in Developer Mode, you can add https://mcp.brakinglab.com/mcp and authorize your Braking Lab account. See the current ChatGPT status.

Codex, Cursor, and other local agents

Use the existing Skills CLI to choose your agent, install location, and skills:

npx skills add r-bart/braking-lab-agent-skills

The Skills CLI installs the skills but does not configure the MCP. In Codex, run codex mcp add braking-lab --url https://mcp.brakinglab.com/mcp, then codex mcp login braking-lab. In Cursor or another agent, add https://mcp.brakinglab.com/mcp as a Streamable HTTP MCP server and complete OAuth there. The Skills CLI works on Windows, macOS, and Linux with Node.js and npm. It does not install anything in ChatGPT web.

On macOS or Linux, an optional installer without Node.js can also install the skills and configure the MCP in Codex or Claude Code when their CLIs are available. Neither installation route asks for your Braking Lab password or token.

Connect another MCP client manually

Use this server URL in a client that supports MCP Streamable HTTP and OAuth 2.0 with PKCE:

https://mcp.brakinglab.com/mcp

Follow that client’s connection flow to authorize your account. Skills can be installed separately where the client supports them. The server publishes standard discovery endpoints:

  • /.well-known/oauth-protected-resource — Resource metadata (RFC 9728)
  • /.well-known/oauth-authorization-server — Authorization server metadata (RFC 8414)

Your client should handle the OAuth flow automatically if it supports these standards.

OAuth Flow (Technical Reference)

For developers building custom clients, here’s the full authentication flow:

1. Client → POST /mcp (no token)
   ← 401 + WWW-Authenticate header with resource_metadata URL

2. Client → GET /.well-known/oauth-protected-resource
   ← Returns authorization_servers URL

3. Client → GET /.well-known/oauth-authorization-server
   ← Returns authorization_endpoint, token_endpoint, registration_endpoint

4. Client → POST /oauth/register (dynamic client registration)
   ← Returns client_id and client_secret

5. Client → GET /oauth/authorize (with PKCE code_challenge)
   → Opens browser: user logs in via Supabase auth
   ← Returns authorization code

6. Client → POST /oauth/token (code + code_verifier exchange)
   ← Returns access_token + refresh_token

7. Client → POST /mcp (with Bearer access_token)
   ← MCP response with tool results

The access token is a JWT that identifies the user. The refresh token allows silent re-authentication when the access token expires.

Troubleshooting

”Connection Failed” or Timeout

  • Verify the URL is exactly https://mcp.brakinglab.com/mcp
  • Check your internet connection
  • Restart the MCP client

Authentication Keeps Asking to Log In

  • Clear the client’s stored tokens and authenticate again
  • Verify your Braking Lab account is active
  • Check that browser pop-ups are not blocked

Tools Not Appearing

  • Restart the MCP client after saving the configuration
  • Check the client’s MCP logs for connection errors
  • Verify the server URL doesn’t have a trailing slash

Next Steps