CarMaker MCP server

carmaker-mcp

<!-- mcp-name: io.github.dimitr-io/carmaker-mcp -->

An MCP server that lets an AI agent drive IPG CarMaker on your computer: start a session, run test runs, read the results, change vehicle data and Simulink controller parameters, and undo what it changed.

Unofficial community project, not affiliated with or endorsed by IPG Automotive or MathWorks. You need your

own CarMaker and MATLAB/Simulink licences. This repository contains no IPG or MathWorks code or data.

Status: alpha. Developed and tested on one setup (CarMaker 14.1.1, MATLAB R2024b, Windows 11). docs/verification.md lists what has been checked against real software and what has not.

Contents: What it does · What it does not cover · Requirements · Setup · With the MATLAB MCP server · Settings · Tools · Safety and privacy · Troubleshooting · How it works

What it does

Things you can ask an agent once the server is connected:

• "Run the braking test run and tell me the stopping distance."
• "Set Kp_yaw to 1.5 in the controller model, run the slalom again and compare the yaw rate."
• "Try the lane change with a vehicle mass of 280, 300 and 320 kg and tabulate the lateral acceleration."
• "The last run aborted. Why?"
• "Undo everything you changed."

It works in two ways, and the agent picks the one that fits the vehicle:

More worked examples: docs/examples.md.

What it does not cover

The server was written for vehicle-dynamics and controller work in a Formula Student team, where every run was either a standalone run or a CarMaker for Simulink run. CarMaker can do much more than that, and the rest is outside what this server does or has been tried with.

Not supported (there are no tools for it):

Extended (real-time hardware, Fail Safe Tester, bus interfaces such as CAN, FlexRay, SOME/IP, XCP).

• Other platforms and products: Linux; TruckMaker and MotorcycleMaker; CarMaker HIL and CarMaker Office

batch mode with start-up files. The server runs its own parameter studies instead, one run after another.

• CarMaker's own test automation: Test Manager and test series, test reports, parallel (HPC) execution,

cm_edit changes keys in files that exist; it does not author these things.

• Building scenarios: the Scenario Editor and roads, traffic, sensors, the environment, OpenSCENARIO import.

pictures.

• Most visualisation: Movie NX, IPGControl, Instruments, video export, Model Check. Of IPGMovie, only single

• Other result formats: only .erg files are read, not MDF or ASCII.
• Rebuilding the simulation program: models in C code or generated with Simulink Coder.
• Remote machines: CarMaker and MATLAB must run on the computer the server runs on.

May work, never tested:

at a time.

• FMUs, CarMaker exported as an FMU, third-party tyre models and other co-simulation tools.
• Encrypted or protected data files.
• CarMaker and MATLAB versions other than the ones named above; more than one MATLAB session or CarMaker GUI

runs.

• Several standalone runs in parallel, pausing and resuming a standalone run, parameter studies on standalone

so far used vehicle-dynamics runs without them.

• Test runs with traffic, sensors or driver-assistance functions. Nothing stands in their way, but every check

Shortened. The full README is on GitHub.