Author: Vivi Peng | Published for icallin.com | Updated: November 12, 2026
Claude Code Altium PCB design uses a local Model Context Protocol (MCP) server to turn natural-language engineering prompts into scripted edits inside live Altium Designer documents. Rather than exporting dead static graphics, this workflow creates native schematic symbols, footprints, nets, and routed copper directly in .SchDoc and .PcbDoc files—provided an engineer verifies every build gate before moving forward. Treating each MCP call as half of a write-and-read-back loop keeps automated drafting aligned with real component datasheets and PCBA manufacturing rules.
Keeping native CAD projects clean and portable across workstations follows the same principles detailed in our AI PCB handoff and editable file checks. When a coding agent drives Altium through a community bridge, library accuracy, human-led connector placement, polygon refill, and standalone export verification separate a quick bench experiment from a buildable production release.
An Altium MCP server provides structured tool access to Altium Designer's internal DelphiScript automation interface so Claude Code can invoke CAD commands over standard input/output (stdio). In the widely used open-source salitronic/eda-agent bridge (Python 3.11+ on Windows with Altium Designer AD20 or newer recommended), Claude Code sends a tool request to the Python MCP process, which exchanges local request/response files with Altium_API.PrjScr (Dispatcher.pas → StartMCPServer) running inside Altium.
Complete your eda-agent setup on a Git-tracked copy of the Altium project before issuing any design commands:
python -m eda_agent install-scripts to stage the Altium script project.stdio server in Claude Code: Following Anthropic's Claude Code MCP documentation, register the local server with claude mcp add (using --scope user or project scope and placing -- before the Python executable and -m eda_agent arguments), then run /mcp inside Claude Code to confirm an active connection.StartMCPServer in Altium and ask Claude Code to list the open .PrjPcb structure, schematic sheets, and board outline without modifying anything. Confirming read-back proves the bridge points to the intended project and recovers cleanly if a long CAD command times out.Because eda-agent is an independent third-party project, keep proprietary IP policies in mind: while file exchange between Python and Altium stays on the local Windows machine, component descriptions and netlists included in conversation context travel to your configured Claude API or enterprise endpoint.
Reliable schematic netlist verification requires auditing every symbol pin and footprint pad against the component manufacturer's datasheet before synchronizing to the PCB. Even when an agent generates clean-looking symbols for an illustrative handheld component-tester board—combining a USB-C 5 V input with 5.1 kΩ CC1/CC2 pull-down resistors, battery charger/LDO regulation, an MCU with precision probe resistor dividers, an OLED header, and tactile buttons—a single swapped pin number or mirrored SOT-23 land pattern will pass electrical rule checks while failing on the bench.
Structure schematic construction around an explicit pin-connection table and apply the review steps from our PCB schematic handoff checklist:
.SchLib and .PcbLib item to confirm Pin 1 orientation marks, solder-mask expansion, plated hole diameters, and exposed thermal-pad net ties against official mechanical drawings.VBUS, +3V3, VBAT, GND), probe sense nets, and I2C / debug headers resolve with zero unintended single-pin nets or off-grid wire stubs.Effective PCB placement review requires human mechanical judgment before any copper tracks are routed. Left to optimize purely for short Manhattan ratsnest length, an AI client frequently clusters USB receptacles, test probe headers, tactile buttons, and OLED connectors toward the middle of the board or scatters decoupling capacitors several millimeters away from IC supply pins.
Follow the staged floorplanning discipline in our PCB placement and routing review sequence by locking edge-accessible interfaces first, then letting Claude Code assist with secondary grouping and alignment:
100 nF bypass capacitors immediately adjacent to its VDD/VSS pins, keep precision probe divider resistors matched and compact near the ADC inputs, and isolate battery-charging switch loops near the power entry corner.Guiding Claude Code Altium PCB design through routing requires configuring explicit width, clearance, via size, and polygon-connect constraints first, as documented in Altium's design-rule scoping and management guide. On a two-layer board without dedicated internal planes, reserving the bottom layer primarily as a continuous stitched ground pour is critical; an agent-routed 2-layer board that omits ground copper pours or slices the bottom layer with long signal crossovers leaves high-frequency return currents without a low-inductance path.
After routing power trunks, analog sense lines, and digital buses, repour all polygons and run Batch DRC per Altium Designer's DRC verification guide. Inspect which rule categories are enabled in the DRC dialog—verifying unrouted nets, short circuits, silk-to-solder-mask clearances, hole-to-copper spacing, and dead copper islands—rather than accepting a 0 violations summary from a partially disabled rule set.
Generating consistent Altium OutputJob exports requires binding bare-board fabrication files and SMT assembly tables to the exact same verified board revision. Configure a project .OutJob file—following Altium's OutputJob Editor documentation—to bind Gerber X2 or RS-274X layers, NC drill/slot tables, IPC-2581 or ODB++ archives, assembly drawings, BOM, and pick-and-place centroid outputs to the live .PrjPcb variant.
| Build & release stage | What Claude Code + MCP automates well | Mandatory engineering check before sign-off |
|---|---|---|
| 1. MCP bridge & project sync | Querying sheet lists, placing components, applying repetitive net labels | Confirm active .PrjPcb path, Git diff, and zero ECO comparator mismatches |
2. Component libraries (.SchLib / .PcbLib) | Drafting multi-pin symbol tables and standard passive footprints | Verify Pin 1 marks, datasheet pad dimensions, hole tolerances, and MPN orderability |
| 3. Placement & 2-layer routing | Grouping passives, executing net-class track passes, reading DRC counts | Lock edge connectors first, pour stitched ground copper, and audit enabled Batch DRC rules |
4. .OutJob production package | Triggering configured OutputJob containers and formatting BOM tables | Inspect generated Gerbers/drills in a CAM viewer; match BOM MPNs and rotations to centroid data |
Table 1. Division of labor between Claude Code MCP automation and human hardware verification across an Altium PCB build.
Remember that seeing configured output generators inside an .OutJob screen only confirms template setup; run the live export, open the generated Gerbers and drill files in an independent viewer, and cross-check diode/IC 0° rotation angles between the pick-and-place file and BOM before submitting for PCBA quotation.
No. While Claude Code can drive symbol creation, net wiring, component placement, and routing commands through an Altium MCP server, it routinely requires human correction on datasheet pin-to-pad orientation, edge connector ergonomics, continuous two-layer ground pours, and DFM clearances. Stage-by-stage engineering verification remains essential for a working first-spin board.
Altium's Batch DRC only tests rule types marked enabled for batch execution in the current .PcbDoc. If unrouted-net, polygon-clearance, annular-ring, or silkscreen-over-pad checks are disabled in a template, an MCP query accurately reports zero violations while manufacturing defects remain on the board.
Successful Claude Code Altium PCB design uses MCP automation as a fast, scriptable drafting partner inside a strict engineering gate process. By validating your eda-agent setup on a versioned project, auditing datasheet pin maps and schematic netlists, leading placement around real mechanical boundaries, pouring continuous return copper, and inspecting final OutputJob exports independently, hardware teams gain speed without trading away PCBA yield.
Written by Vivi Peng for icallin.com.
Share your PCB manufacturing or PCBA assembly requirements with icallin through our dedicated quotation page.

PCB Price Shock
We help buyers reduce risk, save time, and secure available stock.
Fast quote for global buyers