Back to blog
mcpopen-sourceiracinglmu

Open-source simulator MCP servers: telemetry and control for any client

What the Rust simulator MCP servers do, how to run them on a Rig, how Director uses them, and how to contribute a tool or a new simulator adapter.

·Sim RaceCenter Team·3 min read
On this page

Every automated broadcast starts with two questions: what is happening on track, and can we point a camera at it? In Sim RaceCenter both answers come from the simulator MCP servers, a GPL-3.0 Rust workspace that anyone can use.

What is in the repository

CrateWhat it does
iracing-mcpiRacing telemetry and session data, camera focus and replay control through the iRacing SDK. The reference adapter.
lmu-mcpLe Mans Ultimate through its local REST API, with the same tool names.
publisher-mcpRuns on a driving Rig and sends race events to a paired Director over TLS.
launchersimracecenter-launcher.exe: CLI, singleton runner and settings web UI. Hosts one role at a time.
mcp-coreShared JSON-RPC layer, transports and verification helpers.

Running one

Download simracecenter-launcher.exe from the releases page and run it on the Rig next to the simulator. By default it serves MCP over Streamable HTTP on 0.0.0.0:8765, so any client on the LAN can connect to http://<rig-ip>:8765/mcp. Use --bind 127.0.0.1:8765 to keep it on the Rig, or --transport stdio when a local MCP client spawns it.

Simulator roles are unauthenticated by design: anything that can reach the port can call any tool. Run them on a trusted network and never port-forward them to the internet. The publisher role is the exception. It requires pairing and scoped bearer credentials.

The tool surface

Read tools cover the session (get_session_overview, get_roster, get_standings, get_relatives, resolve_driver) and the camera list (get_camera_groups). Control tools focus cameras (camera_focus) and drive the replay (replay_seek_session_time, replay_search_event, and the composite replay_show_window that cues up and plays a clip in one call).

Every mutating tool follows command → poll → verify. It sends the command, polls telemetry and only reports success once the simulator shows the change. If it does not, the caller gets a structured error such as timeout, no_movement or wrong_mode and can fall back to another shot. get_capabilities lists which tools an adapter supports, so a client can check once instead of learning gaps from errors.

How Director uses them

Director connects to the simulator server on the spectator host for cameras and replays, and receives race events from the publisher on each driving Rig. Its shot packs are written against these tool names, which is why the same pack can run on iRacing today and on Le Mans Ultimate as its adapter matures.

Contributing

The project welcomes contributions. The workflow is short:

  1. Open an issue first for anything non-trivial, and reference it from your PR.
  2. Read the ADRs in docs/adr before changing the workspace shape, the launcher process model or an adapter contract. One simulator server runs at a time by design.
  3. Keep the verification loop for any new mutating tool.
  4. Pass the gates: cargo fmt --all, cargo clippy --workspace --all-targets -- -D warnings, cargo test --workspace.
  5. Sign off commits with git commit -s (DCO) and add the SPDX header to new files.

The full guide is in CONTRIBUTING.md, and security reports go through SECURITY.md.