Universal Netlist MCP Server

What it does

This server turns schematics on your disk into a netlist an assistant can question. Ask which parts sit on a net. Ask what is wired to pin U2.10, or have it trace the circuit outward from a net, search parts by refdes or part number, and run a set of electrical rule checks. It is built for design reviews done as a conversation.

It reads OrCAD/CIS .DSN files and Altium .PrjPcb projects directly, without a Cadence or Altium install. KiCad works too: a committed .net export is used when present, otherwise it parses the KiCad 6 to 10 schematics itself, and kicad-cli is just the fallback. Its open .netlist.json format is the fourth input. Variants such as Do Not Stuff parts or Altium alternates are chosen per query through design_variant. Password-protected OrCAD files take their password from environment variables, never from a tool argument.

In the code (src/tools/index.ts) there are 11 tools, all annotated read-only, and their schemas are strict: an unknown argument gets refused instead of silently dropped. A twelfth, export_cadence_netlist, sits in the source but a build flag in src/features.ts removes it, and nothing at runtime brings it back. A few defaults matter. list_designs walks folders to any depth unless you pass max_depth, and stops at 50 results unless max_results is raised. Searches include Do Not Stuff parts by default. The two trace tools and run_erc skip them unless include_dns is true.

Each tool doubles as a shell command of the same binary, which also has export_design for writing one build of a design to .netlist.json.

What it needs

Use one of the two: the standalone binary from the project's install script (macOS arm64 and x64, Linux x64 and ARM64, Windows x64, no Node.js needed) or the npm package, which needs Node.js 22.15 or later. The docs warn to install it one way only, since the plugin runs the first universal-netlist on PATH. Design files must be on the local disk.

Limits

• Not covered Works on connectivity only. Voltage ratings, tolerances and other electrical specs are not in its data model and are left to datasheets
• Read only Cannot edit schematics. Every offered tool only reads, and the one disk-writing tool in the source is disabled at build time
• Size cap list_designs returns 50 designs by default, more with max_results, and scans folders to any depth unless max_depth is set
• Limit Power and ground detection and where traces stop depend on net names, so results rely on the schematic following its net naming conventions
• Limit OrCAD designs saved in an old Capture format (Library stream version below 3) are refused and must be re-saved in a newer Capture
• Limit A design that records named variants must be queried with design_variant set to one of them
• Limit Started by hand in a terminal with no command, the binary prints setup help instead of serving. MCP clients start it normally

It analyses connectivity only: voltage ratings, tolerances and other electrical specifications are not in its data model and are left to datasheets. It does not edit schematics. Net naming drives power/ground detection and where circuit traces stop, so results depend on the schematic following the project's net naming conventions. list_designs returns 50 designs by default. Run by hand in a terminal with no command, the binary prints setup help instead of serving; MCP clients start it normally.

Who it suits

Hardware engineers with OrCAD, Altium or KiCad schematics on their own machine who want to ask about parts, nets and connectivity, or run a rule check, without opening the EDA tool or holding a licence. All offered tools only read, so it is a reasonable fit for reviewing designs you do not want touched. Look elsewhere for PCB layout, simulation, schematic editing or component specifications, none of which it covers.