# CarMaker [Health: Active]

**Category:** 💻 Developer Tools  
**Repository:** https://github.com/De-Ioannidis/carmaker-mcp  
**GitHub Stars:** 1  
**Views:** 0  
**Installs:** 0  
**Upvotes:** 0  
**Directory Page:** https://allmcps.com/mcp/carmaker

## Description
Drive IPG CarMaker for Simulink: run test runs, read results, edit vehicle data and parameters.

## Tools
Capabilities this server exposes over MCP:

- **cm_session_start** — Start MATLAB, the model and the CarMaker GUI as far as they are missing
- **cm_doctor** — Check the setup and say how to fix what is wrong
- **cm_status** — Simulation state, active model, project folder
- **cm_load_testrun** — Load a test run into the CarMaker GUI
- **cm_wait_end** — Wait for the end of the run; returns end status, simulation time, distance and the result file
- **cm_live** — Read quantities while the simulation runs
- **cm_log** — Read CarMaker's session log, for example after an aborted run
- **cm_results_list** — Newest result files
- **cm_results_summary** — First, last, min, max and mean of quantities in a result file; search for quantity names
- **cm_results_read** — Time series from a result file
- **cm_model_logs_save** — After a run, save what Simulink logged (logged signals, To Workspace blocks) and both workspaces to a MAT file. `save_logs` on `cm_start_sim` and `cm_study_start` does it automatically for every run
- **cm_standalone_launch** — Start an independent CarMaker process and run a test run on it
- **cm_standalone_close** — Stop the process
- **cm_changelog** — What this session changed, with old and new values
- **cm_revert_all** — Undo this session's changes
- **cm_restore** — Restore the files of an earlier session from its backups

## Claude Desktop Quick Installation
Install path detected from listing signals. Uses `uvx` (confidence: high):

```json
"mcpServers": {
  "carmaker": {
    "command": "uvx",
    "args": ["carmaker-mcp"],
    "env": {
      "CM_PROJECT": "",
      "CM_MODEL": "",
      "CM_MATLAB_INIT": ""
    }
  }
}
```

**Requires environment variables:** `CM_PROJECT`, `CM_MODEL`, `CM_MATLAB_INIT` — the values above are empty placeholders; fill in real credentials before running (see the repository for what each one is for).

## Documentation

## What CarMaker MCP server does

The CarMaker MCP server connects an MCP client to IPG CarMaker running on the same Windows computer. It gives an AI agent a way to start or inspect a CarMaker session, load test runs, execute simulations, monitor progress, and examine generated results.

For CarMaker for Simulink projects, the server can work with MATLAB and an active Simulink model. It can change vehicle data and controller parameters, run tests, read logged signals, and save MATLAB or Simulink workspace data after a run. For vehicles using CarMaker's built-in controllers, standalone execution can run without MATLAB or a visible GUI window.

## How it works

A session can start MATLAB, the selected model, and the CarMaker GUI when they are not already available. The agent can then load a test run and wait for completion. During or after execution, it can inspect simulation state, live quantities, session logs, result files, and time-series data.

The server reads CarMaker `.erg` result files and can report summary statistics such as first, last, minimum, maximum, and mean values. It also supports independent CarMaker processes for standalone runs, which can be launched and later stopped separately from a MATLAB-connected session.

Changes made during a session are tracked. An agent can view old and new values, undo all changes from the current session, or restore files from an earlier session backup. Parameter studies are performed by running one test after another rather than through CarMaker's own test-series or batch facilities.

## Setup and configuration

The CarMaker MCP server requires Windows 10 or 11, IPG CarMaker with its Python API, and `uv` or an equivalent Python setup. MATLAB R2022b or newer and CarMaker for Simulink are needed for MATLAB-connected operation. The project must also have valid CarMaker and, where applicable, MATLAB/Simulink files and licenses.

Run `uvx carmaker-mcp doctor` to check detected CarMaker and MATLAB installations and obtain compatible Python and MATLAB Engine arguments. The documented tested setup is CarMaker 14.1.1 with MATLAB R2024b on Windows 11. A `--mock` option is available for inspecting the tools without an installed CarMaker environment.

Configure the MCP client with `CM_PROJECT` for the CarMaker project folder. `CM_MODEL` selects the Simulink model, while `CM_MATLAB_INIT` can identify a MATLAB initialization script that prepares paths and opens the model. The README names Claude Code, Claude Desktop, VS Code with GitHub Copilot, Codex, Antigravity, and Cursor as client options.

## Tools and capabilities

Available operations include:

- Starting and diagnosing a MATLAB/CarMaker session.
- Reporting simulation state, active model, and project folder.
- Loading test runs and waiting for completion details.
- Reading live quantities, logs, result-file lists, summaries, and time series.
- Saving Simulink logs and MATLAB workspaces to a MAT file.
- Launching and closing an independent standalone CarMaker process.
- Viewing session changes, reverting them, and restoring earlier backups.

## Limitations and notes

The CarMaker MCP server is an unofficial alpha project and is not affiliated with IPG Automotive or MathWorks. Development and testing were performed on one Windows setup; other CarMaker and MATLAB versions may work but are not confirmed.

It does not provide tools for Linux, TruckMaker, MotorcycleMaker, HIL, Office Extended, Test Manager, parallel HPC execution, scenario authoring, most visualization features, or remote machines. Result reading is limited to `.erg` files, and the server does not rebuild C-based or Simulink Coder simulation programs. CarMaker and MATLAB must run on the same computer as the server.

_Full upstream README: https://allmcps.com/mcp/carmaker/readme_