Your AI tools.
Your WinOLS workflow.

1. Build and check the mock backend

git clone https://github.com/amirdauti/redline-autohaus-winols-mcp.git
cd redline-autohaus-winols-mcp
cargo build --release --locked
.\target\release\winols-mcp.exe --backend mock --doctor

--doctor prints diagnostic JSON and exits. On Linux, use ./target/release/winols-mcp. Source installation is available independently of downloadable release bundles.

2. Register a local stdio server in your MCP client

Use an absolute executable path and the arguments below. Add these launch settings using your client's configuration format.

{
  "command": "C:\\path\\to\\winols-mcp.exe",
  "args": ["--backend", "mock"]
}

Without --doctor, the executable serves MCP over standard input and output. Diagnostic messages go to standard error. The repository also includes client configuration and synthetic examples.

3. Ask your client to inspect and create

Your client needs access to the example file, or you can paste its contents into your request. The example describes synthetic data and has no vehicle-specific meaning.

Read Original and current bytes

Pass the current project ID to winols_read_bytes, with a zero-based byte address and count from 1 to 4096. The result contains equally sized original_bytes and current_bytes arrays, plus project_id, address, window_id, and version_name. Window and version checks describe the observed context; they do not provide a unique version identity or a revision lock.

MCP client  -- stdio -->  Rust MCP server
                                |
                         local mailbox files
                                |
                         Lua bridge in WinOLS

1. Copy the complete bridge folder to a stable location. Create a private local mailbox directory writable by your Windows user. Use one server and one bridge per mailbox.
2. Open a saved synthetic test project. The adapter requires one contiguous project element starting at byte zero, a current element offset of zero, the original SHA-256 in project properties, and permission to read map structure.
3. Export the map list as CSV with all maps and columns. Set SCRIPT_DIRECTORY, BRIDGE_DIRECTORY, CSV_ADDRESS_COLUMN, and CSV_DELIMITER in winols_bridge.lua using your paths and the exact exported address column header. The adapter accepts strict decimal offsets and explicitly $-prefixed hexadecimal offsets.
4. Drag winols_bridge.lua onto the target project window. Run the connection check below using the same mailbox path.
5. Register the executable in your MCP client with --backend winols --bridge-dir C:\winols-mcp-mailbox. Compare the project identity and complete map inventory with WinOLS before creating a definition.

& "C:\path\to\winols-mcp.exe" --backend winols --bridge-dir "C:\winols-mcp-mailbox" --doctor

Follow the complete bridge setup and live acceptance procedure for installation-specific export settings. Project metadata returned through MCP is available to your client; its handling depends on the client you choose.

Inspect and save in WinOLS

The polling script occupies WinOLS while it runs. Create a stop file in the mailbox to end the loop before using WinOLS interactively:

New-Item -ItemType File -Path C:\winols-mcp-mailbox\stop

Inspect the definition and save the project manually. Before a new session, stop the MCP client, remove the stop file, then restart the bridge and client. Obtain a fresh project ID before creating another definition.

{
  "name": "Synthetic demonstration map",
  "address": 256,
  "columns": 4,
  "rows": 2,
  "data_type": "u16_le",
  "factor": 0.1,
  "offset": 0.0,
  "unit": "demo"
}

Pass this object as definition to validation and creation. Creation also requires expected_project_id from winols_get_project. Supported storage types are u8, i8, and signed or unsigned 16- and 32-bit integers in little- or big-endian order. Optional x_axis and y_axis objects specify their own address, storage type, scaling, and unit.

Each dimension is limited to 4,096, with at most 1,048,576 map cells. Floating-point, bitfield, noncontiguous, reversed, and other unsupported native layouts return errors. See the native API mapping and layout boundaries.