Ask your AI about every lap.
Connect ChatGPT, Claude or your terminal agent to Apex Racing. Your assistant reads your sessions with 38 analysis tools and answers with your own numbers.
The URL needs an Apex Racing account. Your assistant asks you to sign in once. No account yet? Start your free trial first.
-
1
Add a custom MCP server
Open the plugins page of ChatGPT, select the plus button, then Add custom MCP server.
-
2
Paste the server URL
Give it a name, paste the URL and select Create as a plugin.
-
3
Sign in once
ChatGPT opens Apex Racing. Sign in with your account and approve.
-
4
Ask in a chat
Type @ in a new chat and select the plugin. Then ask about your laps.
-
1
Add a custom connector
In Claude, open Customize, then Connectors. Select Add, then Add custom connector.
-
2
Paste the server URL
Give it a name, paste the URL and select Add.
-
3
Sign in once
Claude opens Apex Racing. Sign in with your account and approve.
-
4
Ask in a chat
Turn on the connector in the + menu of a chat. Then ask about your laps.
-
Claude Code
$ claude mcp add --transport http apexracing https://apexracing.io/api/v1/mcpThen type /mcp in Claude Code, select apexracing and sign in.
-
Codex CLI
$ codex mcp add apexracing --url https://apexracing.io/api/v1/mcp$ codex mcp login apexracingThe login command opens your browser.
-
opencode
"mcp": { "apexracing": { "type": "remote", "url": "https://apexracing.io/api/v1/mcp" } }$ opencode mcp auth apexracingAdd the first line to opencode.json, then run the auth command.
Your question. Your numbers.
Ask in your own words, as you ask an engineer. Here is one real question about a practice on the old Südschleife, as you see it in your assistant.
Lap 4 on the old Südschleife was 3.6 s faster than lap 2. Where did I find the time?
- list_sessions 4 laps, 2 Nov track Nurb_1971, last 7 days
- list_laps best 2:57.480, lap 4 session b3f76963
- get_time_delta_trace +3.617 s laps 2 and 4, every 100 m
- compare_lap_segments +1.038 s 900 to 1,100 m
- compare_lap_segments +2.157 s 5,150 to 5,650 m
- analyze_braking_zone 146 / 186 km/h 5,150 to 5,700 m
3.2 of the 3.6 s come from two places.
At 5.3 km you lift early on lap 2 and coast from 195 to 145 km/h before you brake. On lap 4 you stay flat to 5,301 m and brake from 186 km/h. That is 2.16 s.
At 1 km lap 2 has a big correction, steering 0.84 against 0.21, and slows to 85 km/h. Lap 4 holds 110 km/h. That is 1.04 s.
Name the track and the laps. You need no ids and no tool names.
list_sessions found the session from the track nameYour assistant selects the tools and their order. It shows each call, so you can check each number.
3.2 of the 3.6 s found in 6 callsThe tools read the sessions of the account that signs in, and nothing else.
Every tool reads one accountYou ask. It picks the tools.
You never name a tool. Your assistant reads your question, calls the tools that answer it and shows each call.
“Practice is done. What is the best strategy for Sunday’s one hour race?”
- list_sessions Monza practice55 laps
- analyze_fuel_consumption practice3.23 L per lap
- simulate_race_strategy 60 min, 4 plans1 stop
After lap 16, with new tyres. Start with 55 L and add 55 L at the stop. Two stops is the same within 1.4 s.
Times come from recorded timestamps. Each answer carries its warnings and a confidence.
Südschleife question: time_source recorded, confidence highget_game_knowledge gives curated facts per game, car class and track. Only public entries leave Apex Racing.
128 public entries match the Südschleife sessionTwo tools draw: a telemetry chart and the racing lines of a corner. Your assistant shows the image.
render_telemetry_chart, render_racing_lineYour laps for you.
The server for its admins.
Every person with full access gets 45 tools: 38 for their laps and 7 that read a game server. The 18 tools that change a game server show only for the owner and the admins of its league.
| Your laps 38 tools | Server, read 7 tools | Server, control 18 tools | |
|---|---|---|---|
| Without full access The trial ended and no plan is active. |
Each call answers with a link to your billing page. p0 still records your laps.
|
||
| With full access Trial or plan, no league with a server. |
Your sessions, laps and telemetry
|
The list is empty
|
Not in the tool list
|
| Member of a league The league has a game server. |
Your sessions, laps and telemetry
|
Schedule, settings, live timing
|
Not in the list. A call names whom to ask
|
| Owner or admin Of the league that owns the server. |
Your sessions, laps and telemetry
|
Schedule, settings, live timing
|
18 more tools in the list
|
“Only M. Keller and the admins J. Brandt and L. Varga of Thursday Night GT3 can change this server. Ask one of them.”
The answer names the owner and the admins. A person outside the league only reads “Server not found, or not visible to you.”[email protected] via MCP
Each change through MCP writes a line in the Log of the Server tab, like a change on the web.Apex Racing checks your role at each call, also when a client keeps an old tool list.
The same rule as the Server tabkick_driver and block_driver are marked as destructive, so your assistant asks you first.
9 of 18 control toolsRace results, handicaps, the race director and the cars of an official round stay on the web.
Official sessions follow the seasonBefore your first question
The free trial or a plan. Without it, each call answers with a link to billing.
An assistant that adds a remote MCP server by URL, for example ChatGPT, Claude or Codex CLI.
The tools read what p0 recorded. Drive one session first, then ask.
For each assistant that you connect. A long question with many tool calls fits easily.
More ways to get faster
Ask about your next lap.
Install p0, drive one session, then connect your assistant. 30 days free, no card.