Open source · GPL-3.0-or-later · Rust

Simulator MCP servers

The layer between the racing simulator and everything that wants to understand or control it. Each server runs on a Windows PC next to the simulator, reads it locally, and exposes telemetry, camera and replay control as tools over the Model Context Protocol. Director uses them to produce broadcasts. You can use them for your own agents, overlays and tools.

Purpose

Why MCP

One contract per simulator. iRacing and Le Mans Ultimate expose the same tool names and response envelope. A client written against one works against the other, andget_capabilitiessays what is missing.

Verified control. Camera and replay tools follow command → poll → verify. A call only succeeds once telemetry shows the simulator did it, so an automated director never cuts to a shot that did not happen.

Any client. Director, an AI agent, a Stream Deck plugin or a script: anything that speaks MCP over Streamable HTTP or stdio can use the same tools.

Workspace

What is in the repository

iracing-mcpSimulator

iRacing session data, roster, standings, relatives, camera groups, camera focus and replay control through the iRacing SDK shared memory and broadcast messages. The reference adapter.

Tool reference →

lmu-mcpSimulator

Le Mans Ultimate over its local REST API, with the same tool names. get_capabilities reports which tools are supported, degraded or unsupported for LMU.

Tool reference →

publisher-mcpPublisher

Runs on a driving Rig and sends race events (incidents, overtakes, pit stops, Focus Me presses) straight to a paired Director over TLS. Protected by pairing codes and scoped bearer credentials.

launcherWindows app

simracecenter-launcher.exe: CLI, singleton runner and settings web UI. Hosts exactly one active simulator or publisher role at a time.

mcp-coreLibrary

Shared JSON-RPC layer, Streamable HTTP and stdio transports, config load/merge and the command → poll → verify helpers every adapter uses.

Usage

Run it on the Rig

  1. Download simracecenter-launcher.exe from the latest release and run it on the Windows Rig next to iRacing or Le Mans Ultimate.
  2. Pick the simulator role in the settings page. By default the server listens on 0.0.0.0:8765 using MCP Streamable HTTP.
  3. Point any MCP client at http://<rig-ip>:8765/mcp. Use --bind 127.0.0.1:8765 to keep it on the Rig, or --transport stdio when a local client spawns it.

Session

get_session_overviewget_weekend_infoget_rosterget_standingsget_relativesresolve_driver

Camera

get_camera_groupscamera_focuscamera_set_state

Replay

replay_get_statereplay_set_playbackreplay_seek_session_timereplay_search_eventreplay_show_window

Introspection

get_capabilitiesget_runtime_provenance
Trusted network only. Simulator roles are unauthenticated by design: anything that can reach the port can call any tool. Keep them on your private LAN and never port-forward them to the internet. The publisher role requires pairing and scoped bearer credentials. See SECURITY.md.

Try it

Use them with Claude, ChatGPT or your own agent

Director is one client of these servers. Your AI assistant can be another. Give it the race and see what it does with it.

Claude Desktop on the Rig

Add the launcher to claude_desktop_config.json and Claude starts it over stdio, on the same machine as the simulator.

{
  "mcpServers": {
    "simracecenter-iracing": {
      "command": "C:\\SimRaceCenter\\simracecenter-launcher.exe",
      "args": ["--sim", "iracing", "--transport", "stdio", "--headless"]
    }
  }
}

Use lmu instead of iracing for Le Mans Ultimate.

ChatGPT and other MCP clients

Clients on your LAN can connect over Streamable HTTP at http://<rig-ip>:8765/mcp. ChatGPT connectors run in the cloud and need a public HTTPS URL; the simulator roles are unauthenticated, so do not open them to the internet to make that work.

Things to ask

  • “Who is leading, and what is the gap to P2?”
  • “Point the camera at the closest battle in the top ten.”
  • “Find the last incident and replay it.”
Tell us what you built. Drop a comment in the chat of our next live stream, or on any video, with what your assistant did. We read them on air. Sim RaceCenter on YouTube →

Contribute

How to contribute

Bug reports, new tools and new simulator adapters are all welcome. New adapters follow the shape of iracing-mcp, the reference implementation.

  1. 01

    Open an issue first

    Every non-trivial change starts as a GitHub issue so the design can be agreed before code is written. Typo and doc fixes can go straight to a PR.

  2. 02

    Read the ADRs

    Architecture decisions live in docs/adr. Read the relevant record before changing workspace shape, the launcher process model or an adapter contract. One simulator server runs at a time by design (ADR 0003).

  3. 03

    Verify, don’t fire and forget

    Mutating tools send the command, poll telemetry and only report success once the simulator reflects it. New tools follow the same loop and return structured error codes.

  4. 04

    Pass the gates

    cargo fmt --all, cargo clippy --workspace --all-targets -- -D warnings and cargo test --workspace must be clean. A dev container cross-compiles to Windows.

  5. 05

    Sign off your commits

    The project is GPL-3.0-or-later. Commits carry a DCO sign-off (git commit -s) and new source files carry an SPDX header.

See them in a real broadcast

Director uses these servers to read the race and drive iRacing's cameras and replays.