proteus-mcp
Provides tools for working with Labcenter Proteus 8 projects: reading schematics and netlists, tracing nets, generating BOMs and design checks, editing component properties/values/reference designators, managing embedded firmware files, searching Proteus device libraries, exporting SDF netlists, running the simulator headless, and opening projects in the Proteus GUI.
This server does not currently have a deployable release on Glama. Follow the repository's setup instructions to install and configure it for your MCP client, including any required credentials and local dependencies.
⚡ proteus-mcp
Give Claude (or any MCP client) hands-on access to your Labcenter Proteus 8 projects.
Read schematics · trace nets · build BOMs · edit parts · manage firmware · search ~500k library parts · run the simulator headless
Proteus has no public automation API, and its project files (.pdsprj) use an
undocumented binary format. proteus-mcp is built on a from-scratch reverse engineering of
that format, so an AI assistant can work with your circuits directly instead of you clicking
through dialogs.
💬 "Which pins of U1 are unconnected?" 💬 "Point the microcontroller at
build/app.hexand set the clock to 16 MHz." 💬 "Give me a BOM as CSV, grouped by value." 💬 "Find me a 16×2 I²C LCD in the Proteus library." 💬 "What is connected to the VCC net?"
📑 Contents
Related MCP server: kicad-forge
✨ Features
🔍 Understand any design | Components, values, packages, positions, properties and the full netlist rebuilt from the file |
🧭 Trace connections | Ask what a pin ( |
✏️ Edit safely | Change properties ( |
🧾 BOM & checks | Bill of materials (JSON/CSV) and design checks: missing firmware files, duplicate refs, dangling nets, unconnected pins |
💾 Firmware | Read and write source files embedded by VSM Studio / Visual Designer (e.g. Arduino |
📚 Library search | Search the ~500,000 devices in your installed Proteus libraries by name, description or category |
▶️ Simulator & GUI | Export SDF netlists, run Proteus' simulator headless as a design check, open projects in the Proteus GUI |
🚀 Quick start
Requirements: Node.js 18.17+. The library search, simulator and GUI tools also need Proteus 8 on Windows; the read and edit tools work on any OS.
1. Install and build
git clone https://github.com/Fretzzz/proteus-mcp.gitcd proteus-mcp && npm install && npm run build2. Connect it to your MCP client
claude mcp add proteus -- node /absolute/path/to/proteus-mcp/dist/index.jsAdd to claude_desktop_config.json:
{
"mcpServers": {
"proteus": {
"command": "node",
"args": ["C:\\absolute\\path\\to\\proteus-mcp\\dist\\index.js"]
}
}
}It is a standard stdio server: run node dist/index.js.
3. Ask away. Point the assistant at a .pdsprj file and ask about it.
If Proteus is installed somewhere unusual, set the environment variable
PROTEUS_HOMEto the folder that containsBIN\PDS.EXE.
🧰 Tools
Example output (get_netlist, text format):
GND: C1.1 C2.1 R2.1 U1.GND(20)*
VCC: C3.+ R1.1 U1.$EA$(31) U1.VCC(40)*
#00001: C2.2 U1.XTAL2(18) X1.1
#00002: C1.2 U1.XTAL1(19) X1.2
#00004: LCD1.RS(4) U1.P3.0/RXD(10)
(* = hidden power pin joined by name)⚙️ How it works
flowchart LR
A["🤖 Claude / MCP client"] <-->|stdio| B["proteus-mcp"]
B --> C["ZIP container<br/>.pdsprj"]
C --> D["ROOT.DSN<br/>schematic (binary)"]
C --> E["ROOT.CDB<br/>pin names & parts"]
C --> F["FIRMWARE/<br/>embedded sources"]
B --> G["DATA\\LIBRARY<br/>device index"]
B -->|SDF netlist| H["PROSPICE.EXE<br/>headless simulator"]
B -->|launch| I["PDS.EXE<br/>Proteus GUI"]The key finding: Proteus stores wiring as absolute file positions. Every component pin holds the byte position of the wire it touches, and junctions list the wires that meet. Following those positions gives an exact netlist.
It also makes editing tricky: any change in text length shifts every later record. The editor
updates all of those positions, proves it has found every one, and re-checks the connectivity
before saving. The full format write-up is in docs/FORMAT.md.
✅ Tested against the real thing
Check | Result |
Sample projects shipped with Proteus that open | 634 / 634 |
Components · wires · terminals · junctions parsed | 9,485 · 43,558 · 23,789 · 8,530 |
Length-changing edits verified by re-parsing | 554 succeeded · 78 safely refused · 0 corrupted |
Edited files opened in Proteus 8.13 itself | ✔ New values shown in Proteus' own Edit Component dialog, wiring intact |
Netlist vs. a hand-checked wiring table | ✔ Exact match |
Generated netlist run through | ✔ Accepted; 8051 model and HEX firmware load |
Reproduce with npm run corpus (needs a local Proteus install).
🚧 Limitations & roadmap
These are things not yet reverse engineered, not hard limits. They're planned for the next development session.
Limitation | Why | Plan | |
⏱️ |
| Run from the command line, Proteus only simulates what a graph or probe requests. Results go to an undocumented binary "LISA partition" file ( | Add probes to the generated netlist and decode the results file |
🚌 | Buses aren't expanded into individual nets | A bus such as | Implement Proteus' bus-member naming rules |
➕ | Can't add new parts or draw wires | Editing existing records is proven safe. Creating new ones needs bytes still undecoded (graphic styles, label layout, embedded library symbols) | Compare files saved before and after placing a part or wire, then generate records |
🛡️ | ~12% of sample files refuse length-changing edits | They contain records not yet decoded (generator scripts, some instruments). The editor refuses rather than guesses | Decode the remaining record types ( |
🧩 | PCB layouts ( | A separate binary format, used by only 23 of the 634 samples | Reverse engineer the layout format |
🏷️ | Tested on Proteus 8.13 only | Only version available for testing. Older files seen in the 8.13 samples are handled | Test files from other 8.x releases |
Roadmap
Simulation results: probes plus a decoder for LISA partition files
Bus member expansion
Place components and draw wires
Decode the remaining record types so every edit can go through
PCB layout (
ROOT.LYT) readingWider Proteus version coverage
Compatibility: built and verified with Proteus 8.13 (build 31525) on Windows 10, Node.js 18+.
🔒 Editing safely
Close the project in Proteus before editing it. Proteus overwrites the file when it saves.
💾 Automatic backup. Every write first copies the original to
<project>.pdsprj.bak. PassoutputPathto write to a new file instead.🧮 Proof before writing. Edits that change length only go ahead once every file position in the file is accounted for. Otherwise the tool returns an error and leaves the file alone.
🔁 Verified after writing. The result is re-parsed and its connectivity compared with the original before saving.
📐 Exact text layout. Property text keeps its original line structure byte-for-byte. (Padding it makes Proteus hang on load; that was found in testing and fixed.)
🛠️ Development
npm testUnit tests, plus integration tests against a local Proteus sample if one is installed.
npm run corpusParses and edit-tests every sample project that ships with Proteus.
node tools/unexplained-pointers.mjs "C:/Program Files (x86)/Labcenter Electronics/Proteus 8 Professional/DATA/SAMPLES"Lists the record types still to reverse engineer, a good place to start contributing.
src/
├── index.ts MCP server and tool definitions
├── format/
│ ├── archive.ts .pdsprj ZIP container
│ ├── dsn.ts ROOT.DSN parser (labels, components, wires, terminals, junctions)
│ ├── cdb.ts ROOT.CDB pin lists and part records
│ ├── netlist.ts connectivity reconstruction
│ ├── edit.ts edits that update file positions, with verification
│ └── bytes.ts binary and property-text helpers
└── proteus/
├── project.ts high-level project API
├── install.ts locate the Proteus installation
├── library.ts device library index and search
├── firmware.ts embedded firmware projects
├── sdf.ts SDF netlist writer
├── simulate.ts PROSPICE.EXE runner
└── gui.ts PDS.EXE launcher
docs/FORMAT.md the reverse-engineered file format
tools/ reverse-engineering helpers
test/ unit, corpus and end-to-end tests🔬 How it was reverse engineered
Container. A
.pdsprjturned out to be a ZIP file. Inside,ROOT.DSNis a custom binary format that starts with the textISIS SCHEMATIC FILE.Diffing. Proteus' own automatic backups of a design, saved after each editing step, were compared byte by byte to see what every change touched.
The breakthrough. Numbers in each component's pin table matched the byte positions of wire records exactly. That gave both the netlist and a way to edit safely.
Generalising. All 634 bundled samples were parsed over and over. Each unexplained file position or unparsed record was classified until only rare ones remained. This found an older component header layout, probe and generator records, junction nodes and three ways property text is stored.
Ground truth. The rebuilt netlist was compared against a hand-checked wiring table. Edited files were opened in Proteus 8.13 and checked in its own dialogs. That is how the newline-padding hang was caught.
Binaries. Static analysis of
PDS.EXE,PROSPICE.DLLand related programs found the command-line and INI interfaces, the headless simulator and the SDF netlist format.
Details and the evidence behind each claim are in docs/FORMAT.md.
📄 License
MIT © Fretzzz
Proteus is a trademark of Labcenter Electronics Ltd. This project is independent and not affiliated with or endorsed by Labcenter. It reads and writes files you own, for interoperability, and contains no Labcenter code, libraries or sample designs.
Tool Schema Changelog
Recent tool additions, removals, and schema changes observed during successful MCP inspections.
Loading tool schema changelog…
This server cannot be deployed
Maintenance
Related MCP Connectors
Headless CAD engine & MCP server for 2D/3D drafting, solids, DXF/SVG export, and automation.
Render, verify, describe, and safely edit Mermaid diagrams through MCP.
Manage SysML2 projects; check, evaluate, verify, query, document and diagram models.
Read and edit the Revit 2024–2027 model on your PC. Needs the free Revit MCP add-in.
Related MCP Servers
- AlicenseAqualityAmaintenanceMCP servers for KiCad schematic, PCB, symbol, footprint, and project automation, enabling AI-assisted electronic design via tools for read/write, analysis, and exports.109349 PyPI16GPL 3.0
- AlicenseBqualityDmaintenanceProvides schematic/PCB analysis, authoring, and SPICE simulation through MCP, enabling direct KiCad file manipulation and verification without requiring KiCad for reading.18MIT
- AlicenseBqualityCmaintenanceRead-only MCP server that lets AI assistants (Claude Code, Claude Desktop, VS Code, ...) inspect Altium Designer projects — schematics, netlist, BOM and PCB — on Linux, macOS or Windows, without Altium Designer installed.133AGPL 3.0
- AlicenseAqualityCmaintenanceEnables inspection and controlled modification of EasyEDA/LCEDA Pro designs through domain interfaces for schematics, PCBs, pins, netlists, DRC, auto-layout/routing, and Gerber/BOM/pick-and-place export.11Apache 2.0