Logo
Contact Us
Cookies Policy
Terms of Use
Privacy Policy
phone
Vivi (Sales)
phone
Lucy (Sales)
phone
Ban (Sales)
phone
+86 755-2845-3125

  • EN
  • RU
RFQ List
    • Logo
    • RFQ List
      • Manufacturers
      • Hot Products
      • RFQ
      • Blog
      • Tools
      • Sourcing Solutions
      • PCB/SMT
      • About Us
    RFQ
    Certification badge
    Certification badge
    Certification badge
    Certification badge
    Certification badge
    Certification badge
    Certification badge
    Certification badge
    Certification badge
    Certification badge
    Certification badge
    Certification badge
    CONTACT US
    +86 755-2845-3125
    [email protected][email protected][email protected]
    Room 2709B, 5A Office Building, Longguang Jiuzuan, Hongshan, Longhua District, Shenzhen, China
    Company
    • Blog
    • About Us
    • Contact Us
    Resources
    • Categories
    • Manufacturers
    • Tools
    • RFQ
    Quick link
    • Privacy Policy
    • Terms of Use
    • Cookies Policy
    • Refund & Return Policy
    • Shipping & Delivery Policy
    Payment
    • Payment method
    • Payment method
    • Payment method
    • Payment method
    Logistics
    • Logistics partner
    • Logistics partner
    • Logistics partner
    • Logistics partner

    © 2026 Copyright. All Rights Reserved. Made by ICAllIn

    Part number
    Part number
    1. Home/
    2. Blog Home/
    3. PCB Solution/
    4. Claude Code Altium PCB Design: MCP Setup & Release Checks
    PCB Solution2026-11-22

    Claude Code Altium PCB Design: MCP Setup & Release Checks

    Claude Code Altium PCB Design: Build and Verification Gates

    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.

    Configure the Altium MCP server and eda-agent setup safely

    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:

    1. Install and inspect the bridge locally: Clone the repository, review the pinned source commit and license, install the Python package into a dedicated virtual environment, and run python -m eda_agent install-scripts to stage the Altium script project.
    2. Register the 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.
    3. Verify live document read-back first: Start 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.

    illustration

    *Figure 1. Every Claude Code edit through the Altium MCP server requires live CAD read-back and four engineering sign-off gates before releasing fabrication and assembly files.*

    Audit custom libraries and schematic netlist verification

    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:

    • Pin-to-pad correspondence: Open each project .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.
    • Compiled netlist read-back: Run project compilation and inspect the Engineering Change Order (ECO) comparator described in Altium Designer's pre-layout synchronization guide. Verify that power ports (VBUS, +3V3, VBAT, GND), probe sense nets, and I2C / debug headers resolve with zero unintended single-pin nets or off-grid wire stubs.

    Lead PCB placement review around physical board ergonomics

    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:

    • Board-edge mechanical anchors: Lock the USB-C receptacle flush with the enclosure cutout edge, place user pushbuttons and three-wire test probe terminals along unobstructed perimeter edges, and verify OLED display mounting standoff clearances.
    • Functional analog and digital grouping: Place the MCU centrally with 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.

    Enforce routing rules, polygon pours, and batch DRC scope

    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.

    Reconcile Altium OutputJob exports before manufacturing handoff

    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 stageWhat Claude Code + MCP automates wellMandatory engineering check before sign-off
    1. MCP bridge & project syncQuerying sheet lists, placing components, applying repetitive net labelsConfirm active .PrjPcb path, Git diff, and zero ECO comparator mismatches
    2. Component libraries (.SchLib / .PcbLib)Drafting multi-pin symbol tables and standard passive footprintsVerify Pin 1 marks, datasheet pad dimensions, hole tolerances, and MPN orderability
    3. Placement & 2-layer routingGrouping passives, executing net-class track passes, reading DRC countsLock edge connectors first, pour stitched ground copper, and audit enabled Batch DRC rules
    4. .OutJob production packageTriggering configured OutputJob containers and formatting BOM tablesInspect 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.

    Frequently Asked Questions

    Q1: Can Claude Code design and release a production Altium PCB autonomously from one prompt?

    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.

    Q2: Why must engineers check enabled DRC rules instead of trusting a zero-violation MCP reply?

    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.

    Conclusion

    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.

    Need Help With PCB Manufacturing or PCBA Assembly?

    Share your PCB manufacturing or PCBA assembly requirements with icallin through our dedicated quotation page.

    Submit Your PCB/SMT Requirements

    Vivi Peng
    Vivi Peng
    Facebook
    LinkedIn
    Reddit

    Related Blogs

    View All Blogs
    PCB Signal and Power Integrity for USB-C Mixed-Signal PCBs
    PCB Solution
    2026-11-22

    PCB Signal and Power Integrity for USB-C Mixed-Signal PCBs

    Protect PCB signal and power integrity on USB-C mixed-signal boards: check continuous ground return paths, 5V input protection, PDN loops, and 90 Ω routing.

    Read More
    Popular Blogs
    PCB Solution
    PCB Solution2026-06-24

    PCB Market Outlook 2026-2027

    PCB Solution
    PCB Solution2026-06-24

    PCB Capacity Expansion

    4
    Codex Altium MCP: Bridge Setup, Layout & PCB Release Checks
    PCB Solution
    2026-11-21

    Codex Altium MCP: Bridge Setup, Layout & PCB Release Checks

    Run a Codex Altium MCP workflow safely: configure eda-agent, verify mains isolation and Kelvin routing, and audit DRC and Gerber files before PCB release.

    Read More
    4
    Relay Pinout Check: 4-Pin, 5-Pin, 8-Pin & PCB Footprints
    PCB Solution
    2026-11-21

    Relay Pinout Check: 4-Pin, 5-Pin, 8-Pin & PCB Footprints

    Verify any relay pinout before PCB layout: map coil and COM/NO/NC terminals across 5-pin, 8-pin octal, and 30/85/86/87 relays, and confirm bottom-view pads.

    Read More
    6
    Relay Flyback Diode: Polarity, VRRM & Zener Clamp Guide
    PCB Solution
    2026-11-20

    Relay Flyback Diode: Polarity, VRRM & Zener Clamp Guide

    Select a relay flyback diode with verified cathode polarity, coil-current and VRRM margins, and compare standard vs. Zener or TVS clamps for fast release.

    Read More
    7
    Op-Amp Math Circuits: Sum, Difference, Integrator & PCB Tips
    PCB Solution
    2026-11-10

    Op-Amp Math Circuits: Sum, Difference, Integrator & PCB Tips

    Design op-amp math circuits—summing, difference, integrator, and differentiator—with matched resistor ratios, bounded RC frequency bands, and PCB layout checks.

    Read More
    8
    Breakout Boards: Pinout, Logic Levels & Prototyping Checks
    PCB Solution
    2026-11-10

    Breakout Boards: Pinout, Logic Levels & Prototyping Checks

    Use a breakout board safely in breadboard prototyping: verify component pinout, regulator rails, logic level compatibility, and I2C pull-up resistors first.

    Read More
    12
    PCB Solution
    PCB Solution2026-06-24

    PCB Price Shock

    PCB Solution
    PCB Solution2026-06-24

    PCB Allocation Market

    PCB Solution
    PCB Solution2026-08-31

    PCB Thickness for Connector and Enclosure

    PCB Solution
    PCB Solution2026-08-24

    Common PCB Thicknesses

    Hot Products
    ACPL-P343-500E

    ACPL-P343-500E

    Broadcom

    MIMX8MQ6DVAJZAB

    MIMX8MQ6DVAJZAB

    NXP

    MT29F16G08ABACAWP-ITZ:C

    MT29F16G08ABACAWP-ITZ:C

    Micron

    MT53E2G32D4DE-046 AAT:C

    MT53E2G32D4DE-046 AAT:C

    Micron

    MT60B2G8HB-48B:A

    MT60B2G8HB-48B:A

    Micron

    PCI1003

    PCI1003

    Microchip

    Need Reliable IC Sourcing?

    We help buyers reduce risk, save time, and secure available stock.

    1. We inspect parts before shipment to help reduce quality risk.
    2. We verify supplier sources to support safer component purchasing.
    3. We provide traceability support when available, including labels, date codes, and origin information.
    4. We check packaging condition to help avoid handling, storage, or delivery issues.
    5. We support global shipping to help buyers receive parts across regions.
    6. We respond quickly to BOMs, part numbers, stock checks, and urgent RFQs.
    7. We provide clear quotations with price, stock, lead time, and key purchase details.
    8. We help you source available stock and select discounted parts to reduce procurement costs.
    Submit RFQ or BOM List

    Fast quote for global buyers