# AC Coach MCP

Windows-native Assetto Corsa telemetry bridge for Codex.

What it does:

- attaches to AC's named shared-memory pages (`acpmf_physics`, `acpmf_graphics`, `acpmf_static`);
- records live player telemetry to disk;
- segments completed laps and compares them against the session best by spline position;
- exposes the workflow through a local MCP server and a CLI.

What it does not do yet:

- parse AC's `.act` telemetry dump file;
- depend on MOZA Pit House telemetry internals;
- control the sim or the wheel.

MOZA note:

The current implementation treats MOZA as optional environment context. AC already exposes the driver and force-feedback signals needed for first-pass coaching, so the bridge uses AC shared memory as the authoritative source and only reports MOZA presence/config in health output.

## Setup

```powershell
Set-Location C:\ars2\ac-coach-mcp
uv sync
```

## CLI

```powershell
uv run ac-coach-mcp health
uv run ac-coach-mcp snapshot
uv run ac-coach-mcp capture-laps --laps 3 --label evening-run
uv run ac-coach-mcp analyze
uv run ac-coach-mcp recommend-training
uv run ac-coach-mcp start-live-coach --mode consistency
uv run ac-coach-mcp live-coach-status
uv run ac-coach-mcp stop-live-coach
```

## Training workflow

1. Generate the current curriculum and setup files:

```powershell
uv run ac-coach-mcp recommend-training
```

2. Load one of the generated setup files in Content Manager / AC.

3. Arm the live coach before you drive:

```powershell
uv run ac-coach-mcp start-live-coach --mode consistency
```

4. Check status or stop it later:

```powershell
uv run ac-coach-mcp live-coach-status
uv run ac-coach-mcp stop-live-coach
```

## MCP

The server entrypoint is:

```powershell
uv run ac-coach-mcp-server
```

Useful tools:

- `health`
- `snapshot`
- `capture_run`
- `capture_laps`
- `list_sessions`
- `analyze_session`
- `compare_laps`