Introduction to the Race Engineer
Learn what the Braking Lab Race Engineer is and how AI can help you improve on track.
The Braking Lab Race Engineer connects your AI assistant to your telemetry, race calendar, track notes, and setups, subject to your account permissions and plan. It can analyze your driving, prepare races, generate coaching reports, and answer questions about your performance — all through natural conversation.
Nine public skills guide common Race Engineer tasks. They are optional: your connected assistant can still use other MCP actions.
What Can the Race Engineer Do?
| Capability | Description |
|---|---|
| Telemetry analysis | Explore sessions, compare laps, identify weak corners |
| Coaching reports | Generate detailed feedback based on your actual data |
| Race preparation | Build strategies with fuel calculations, stint plans, and pit timing (Ultra) |
| Track notes | Access and update your corner notes and track observations |
| Calendar management | Create race events, link practice sessions, track your schedule |
| Custom analysis | Write code to perform advanced analysis on your data |
How It Works
The Race Engineer connects to Braking Lab through the Model Context Protocol (MCP) — an open standard that lets AI assistants access external tools and data.
You ← AI Assistant (Claude, etc.) ← MCP → Braking Lab Race Engineer → Your Data- You chat with an AI assistant (like Claude Desktop)
- The assistant calls Braking Lab tools through MCP
- The Race Engineer queries your data and returns results
- The assistant interprets the results and responds to you
The assistant receives the results of the MCP actions it calls. Those actions follow your Braking Lab account permissions and plan.
Requirements
To use the Race Engineer, you need:
- A Braking Lab account; sync telemetry through Capture for lap analysis
- An MCP-compatible assistant such as Claude Code, Codex, or another client that supports Streamable HTTP and OAuth
- An active internet connection
What Data Does It Access?
The Race Engineer can read and write data in your Braking Lab account:
- Read-only: Sessions, laps, braking zones, scoreboard, leaderboard, hardware vault
- Creative: Coaching reports (generates new analysis)
- Mutating: Race events, track notepads, preparations (creates/updates your data)
All data access requires authentication and is scoped to your account. The Race Engineer cannot see other users’ data.
Getting Started
Ready to connect? Follow the MCP Setup guide to install the skills and connect your AI assistant to Braking Lab.