MCP Servers for Automotive, Embedded, Reverse Engineering and Model-Based Engineering
A visual field guide to 105 entries: what each one does, why it matters for your work, and a direct GitHub link.
How MCP fits together
The Model Context Protocol lets an AI client call tools exposed by a small server. The server wraps a real system such as a CAN bus, a decompiler, MATLAB or a debugger.
Start here: priority picks
For automotive reverse engineering, ECU diagnostics, embedded work and model-based engineering, these offer the most promising starting points.
| Pick | Best for | Fit |
|---|---|---|
| Reverse Engineer Anything | AI-assisted RE | |
| Ghidra MCP | Decompiling ECU firmware | |
| MCP-CAN | CAN, DBC, UDS, OBD-II, J1939 | |
| AutoSimX | Multi-ECU simulation | |
| MathWorks MATLAB MCP | MATLAB runs and analysis | |
| GitHub MCP Server | Repos, issues, PRs | |
| Hardware debugging servers | OpenOCD, GDB, probe-rs |
Reading the badges
| Badge | Meaning |
|---|---|
| Repository | Link goes straight to a GitHub repository or folder. |
| GitHub search | Link opens a GitHub repository search for the capability. Pick a maintained result yourself. |
Quick tips for choosing a server
| Check | Why |
|---|---|
| Last commit date | Stale servers break with new client versions. |
| Licence | Noncommercial terms block employer use. |
| Safety on real buses | Use read-only or simulated vehicles before touching hardware. |
| Permissions | Limit file, shell and network access to what the task needs. |
