pads-mcp
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.
pads-mcp
An MCP server that lets an AI assistant (Claude Code, Codex, GitHub Copilot) drive PADS Logic (schematics) and PADS Layout (PCB) 9.x through COM automation.
Schematics: place parts, draw wires, attach power/GND symbols and net labels.
Agent PCB routing: the AI agent plans each trace (layer, corners, vias, width) from pad and obstacle data; the server writes it into the design exactly as planned. All routing happens in PADS Layout; there is no autorouter. Every routing call is followed by pads-mcp's own clearance check of the new traces (no PADS Router, no license).
Rules and impedance: net classes, width/clearance/high-speed rules, layer stack-up, and trace width for a target impedance.
How it works
AI client ⇄ pads-mcp (Python, stdio) ⇄ COM ⇄ PADS Logic / PADS LayoutTask | Method |
Queries (parts, pins, pads, nets, rules, stack-up) | COM API ( |
Placing library parts, moving, rotating, attributes | COM API |
Schematic wires, power/GND symbols, net labels, copying parts | No COM API → ASCII round trip (export → edit → import into a blank design → save) |
PCB traces and vias, net classes, rules, stack-up | No COM API → the same ASCII round trip for PADS Layout |
Clearance / width check of routed copper | pads-mcp's own geometry check on the exported ASCII ( |
Visual check | Window capture ( |
Related MCP server: KiCAD MCP Server
Agent routing workflow (PCB)
layout_overview→ board outline, layers, stack-up, via types, net classes/rules, unrouted connections per net.layout_get_net/layout_region→ pins with pad layer and size, existing tracks and vias around the path.The model plans the path and calls
layout_routewith several connections at once:{"routes": [ {"from": "J1.3", "to": "R3.1", "layer": "bottom", "path": [[31.0, 144.8], [31.0, 139.8], [35.8, 139.8]]}, {"from": "J1.2", "to": "R2.1", "layer": "top", "path": [[33.6, 146.8], [33.6, 142.8, "bottom"]]} ]}mm, y up.
The pad centres are added automatically.
[x, y, "bottom"]places a via there and continues on that layer.widthdefaults to the net classREC_TRACK_WIDTH.
The
layout_routeresult has acheckwith the clearance / width findings of the new traces (gap, required value, position, the other object). The model re-routes those, checks visually withpads_screenshot(app="layout", region=[x1, y1, x2, y2]), then routes the next batch.When routing is done, run
layout_checkfor the whole board, then Tools > Verify Design in PADS Layout as the final check (it also covers pours, planes, text and drill holes).
Each PCB edit re-imports the whole design. That takes about 30–60 s on a 160-part board, so batch your routes.
Safety
logic_opencopies the schematic intowork\and opens the copy (the original is never touched).PCB edits are made on the PCB that is open in PADS Layout.
Every edit (schematic or PCB) is an atomic transaction.
The file is backed up to
work\history\first.If PADS rejects or changes anything (for example, the part or net count changes), nothing is saved and the original is reopened.
logic_undo/layout_undorestore the last backup.
The
Font Replacementdialog during ASCII import is answered automatically. Other dialogs can be handled withpads_dialogs/pads_click_dialog.Only one AI client should drive PADS at a time (COM attaches to the running PADS instance).
Tools
Common: pads_guide (design rules of this version + company rules), pads_status, pads_screenshot, pads_dialogs, pads_click_dialog
PADS Logic (schematic, mils)
Files:
logic_open,logic_new,logic_save,logic_export(ascii/netlist),logic_import_ascii,logic_undoQueries:
logic_status,logic_list_parts,logic_get_part,logic_list_nets,logic_get_net,logic_search_libraryParts:
logic_add_sheet,logic_add_part,logic_move_part,logic_delete_part,logic_rename_part,logic_set_attributeDrawing:
logic_draw(parts + nets in one call),logic_wire(connect / power / label / disconnect / net)
PADS Layout (PCB, mm)
Files:
layout_status,layout_open,layout_save,layout_export(ascii/netlist/rules),layout_undoQueries:
layout_overview,layout_list_components,layout_get_component,layout_list_nets,layout_get_net,layout_regionRouting:
layout_route,layout_unroute,layout_check(clearance / width check, no PADS Router)Rules:
layout_get_rules,layout_set_rules,layout_stackup,layout_set_stackup,layout_impedancePlacement:
layout_move_component,layout_select
logic_draw example
{
"sheet": "POWER2",
"parts": [
{"refdes": "U100", "clone_from": "U6", "x": 3000, "y": 6000},
{"refdes": "C100", "clone_from": "C3", "x": 1900, "y": 5900, "rotate": 270,
"attributes": {"Value": "CC2012/10u/K"}}
],
"nets": [
{"name": "5V", "pins": ["U100.VIN", "C100.1"], "style": "wire"},
{"name": "GND", "pins": ["U100.GND", "C100.2"], "style": "power"}
]
}clone_from: copies a part that is already in the design. No library is needed, and attributes can be overridden.Without
clone_from: placespart_typefrom the PADS library.style:wire|label|power|auto.
layout_set_rules example
{
"net_classes": {"USB": ["USB_DP", "USB_DM"]},
"rules": [
{"target": "DEFAULT", "auto_route": true, "width": {"min": 0.2, "rec": 0.25, "max": 1.0}, "clearance": 0.2},
{"target": "USB", "width": 0.3, "clearance": 0.2, "match_tolerance": 0.5, "impedance_min": 81, "impedance_max": 99}
]
}Installation (team members)
0. Prerequisites (once per PC)
PADS 9.x, with PADS Logic / PADS Layout launched once (this registers COM).
uv (Python launcher; it also installs Python):
winget install --id=astral-sh.uv -eGit. For a private repository, sign in once so Git can read it:
gh auth login gh auth setup-gitCheck the installation. The first run downloads the dependencies and takes 10–30 s:
uvx --from git+https://github.com/BlessingQ/pads-mcp@latest pads-mcp --checkYou should see
OKfor PADS Logic / Layout, thenready.
uvx runs the server from an isolated environment in the uv cache (%LOCALAPPDATA%\uv\cache) that holds Python and all dependencies.
Nothing is installed, and there is no venv or pip step. uv cache clean deletes the environment, and the next start rebuilds it.
Versions. @latest is a branch that always points at the newest release.
uvx checks GitHub every time the client starts the server, so a new release is used after the next client restart, with no change to the configuration.
To stay on one release, use its tag instead of latest, e.g. @v0.2.0.
Either way, the server can only start when GitHub is reachable.
To see the version in use, run the check command with --version instead of --check.
Claude Code
Option A (recommended): plugin. Installs the MCP server together with the PCB design-rule skill (skills/).
/plugin marketplace add BlessingQ/pads-mcp
/plugin install pads@pads-mcpFrom a shell, use claude plugin marketplace add BlessingQ/pads-mcp then claude plugin install pads@pads-mcp.
The repository is itself the marketplace (.claude-plugin/marketplace.json), so nothing has to be published separately.
Option B: MCP server only.
claude mcp add --scope user --transport stdio pads -- uvx --from git+https://github.com/BlessingQ/pads-mcp@latest pads-mcpNo skill copy is needed: the server serves the same design rules with pads_guide.
Check with claude mcp list (pads ... ✔ Connected) or /mcp in a session.
OpenAI Codex (CLI / IDE extension / app)
Add the server to %USERPROFILE%\.codex\config.toml:
[mcp_servers.pads]
command = "uvx"
args = ["--from", "git+https://github.com/BlessingQ/pads-mcp@latest", "pads-mcp"]
startup_timeout_sec = 120 # default 10 s is too short for the first uvx download
tool_timeout_sec = 600 # default 60 s; a PCB edit can take a minute or morecodex mcp add pads -- uvx --from git+https://github.com/BlessingQ/pads-mcp@latest pads-mcp also works.
It has no timeout options, so add the two timeout lines to config.toml afterwards.
Design rules: served by the server (
pads_guide), so there is no skill to copy.Check with
codex mcp listor/mcpin a session.
VS Code + GitHub Copilot
Use either of these configuration files.
Portable Copilot config (current default of the "Add Server" flow):
%USERPROFILE%\.copilot\mcp-config.json{ "mcpServers": { "pads": { "command": "uvx", "args": ["--from", "git+https://github.com/BlessingQ/pads-mcp@latest", "pads-mcp"] } } }VS Code format: Command Palette → MCP: Open User Configuration, or the workspace
.vscode/mcp.json:{ "servers": { "pads": { "type": "stdio", "command": "uvx", "args": ["--from", "git+https://github.com/BlessingQ/pads-mcp@latest", "pads-mcp"] } } }
Then:
Use the tools from Copilot Chat with the Agent agent, and check that
padsis enabled under Tools.Design rules: served by the server (
pads_guide), so there is no skill to copy.Copilot Business/Enterprise: an organization admin must enable the MCP servers in Copilot policy. It is disabled by default.
Settings
Environment variable | Meaning |
| Work folder for schematic copies, temporary ASCII files and backups. Default: |
| Company rules file appended by |
Company rules
Write your company's or product's rules into %USERPROFILE%\Documents\pads-mcp\rules.md (Markdown, any structure).
pads_guide appends the file to the design guide on every call, so edits apply at once, and updates never overwrite it.
To share one file across the team, point PADS_MCP_RULES at it (e.g. on a network drive).
pads-mcp --check and pads_status show which file is used. Example:
- Fab minimum track/space: 0.15 / 0.15 mm
- Default via: drill 0.3 mm / pad 0.6 mm
- Stack-up: 4 layers, 1.6 mm, 1 oz outer / 0.5 oz inner
- Isolation: at least 4 mm between GND and SGNDUninstall
Remove the entry for each client you set up, then restart that client.
Client | Remove the server | Remove a skill copied by hand (setups before 0.5.0) |
Claude Code (plugin) |
| Removed with the plugin |
Claude Code (MCP server only) |
| Delete |
OpenAI Codex |
| Delete |
VS Code + Copilot | Delete the | Delete |
Optional cleanup:
uv cache clean pads-mcpdeletes the cached builds. They only take disk space, anduvxrebuilds them when needed.No command above deletes the work folder (
%USERPROFILE%\Documents\pads-mcp\work, orPADS_MCP_WORKDIR) or the company rules file. The work folder holds schematic copies and edit backups, so delete it yourself once you no longer need them.
Where design knowledge lives (MCP vs skill)
Content | Location | Why |
How to operate PADS, and PADS rules that must hold (one wire per pin, SMD pads on their own layer, …) | MCP code + server instructions | Needed for correct behavior; changes together with the tools |
Placement/routing rules, routing workflow, cautions |
| Same release as the tools, so the guide never describes tools the server does not have; read only when needed |
Company standards (fab limits, stack-up, isolation distances) | Local | Differs per company and product; updates never overwrite it |
Every client gets the guide through pads_guide. The Claude Code plugin also installs the same file as a skill, which
Claude Code loads by itself when a PCB task comes up.
Releasing (maintainers)
Bump the version in
pyproject.toml,src/pads_mcp/__init__.py,.claude-plugin/plugin.jsonand.claude-plugin/marketplace.json.Commit, then
git tag vX.Y.Z && git push && git push --tags.Move
latestto the release withgit push origin main:latest. Users on@latestget it at their next client restart. Do not push unreleased commits tolatest; the install snippets never need editing.
work\(design copies, backups) and design files (*.sch,*.pcb,*.asc) are excluded by.gitignore.
Development
git clone https://github.com/BlessingQ/pads-mcp; cd pads-mcp
uv venv .venv
uv pip install --python .venv\Scripts\python.exe -e .
claude mcp add --scope user pads -- "$PWD\.venv\Scripts\python.exe" -m pads_mcp.serverTest a uvx install from the local source with
uvx --from . pads-mcp --check.Test the plugin without installing it with
claude --plugin-dir . mcp list.
| Purpose |
| Call tools over the real MCP stdio protocol (end-to-end tests) |
| List a COM server's methods without starting it ( |
| Schematic parser / geometry / routing tests |
| Diagnostics |
PADS facts this relies on (verified on PADS 9.3)
Schematic (PADS Logic ASCII)
A pin takes only one wire; branches go through a tie dot (3 wires).
Pin decals must be defined before the CAE decals that use them.
An empty
*PART*section starts with 3 blank lines.
PCB (PADS Layout ASCII)
*ROUTE*stores each net as 2-pin connections (PINA PINB+ pointsX Y LAYER WIDTH FLAGS [VIA]).Layer 0 means unrouted and 65 marks the end point.
A via point carries the layer after the via.
A net's connections must be listed in tree order. Otherwise PADS reports "Connection not physically tied to the signal tree" and stops reading.
Importing a route-only ASCII into an open design is rejected ("duplicate connection"), so edits re-import the whole design into a blank one.
Rules live in
*MISC*→RULES_SECTION.NET_CLASS DATARULE_SETwithCLEARANCE_RULE/ROUTE_RULE/HIGH_SPEED_RULEAn absent
AUTO_ROUTEmeans N.
PADS Layout COM cannot create traces or vias.
PADS Layout COM has no Verify Design (DRC) method either. PADS Router COM can route and check, but needs a PADS Router license (
blzshell), so pads-mcp does not use it at all.layout_checkcomputes clearances from the ASCII instead: pads from*PART*+*PARTDECAL*(bottom-side parts: rotate, then mirror x), tracks and vias from*ROUTE*, rules fromRULES_SECTION.
Known limitations
PCB edits take 30–60 s each (whole-design re-import), so batch connections in one
layout_routecall.Routes are point-to-point between pins. T-junctions in the middle of a trace and copper pours are not supported yet.
layout_checkis a simple check: tracks and vias against pads, tracks, vias and the board outline, plus track width. It skips pours / planes / free copper, text, drill holes, same-net and layer-specific rules and pad-to-pad spacing, and counts rounded pad corners as square. Finish with Tools > Verify Design.Impedance uses closed-form formulas (±5–10 %). Confirm with the fab.
Schematic: net label text can sit slightly off the symbol, and
logic_move_partdoes not reroute attached wires.
License
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
EasyGerber brings AI printed circuit board (PCB) design, layout, and routing to MCP-compatible assistants. Describe a circuit or start from firmware pin assignments, search published electronic components, and build schematics using catalog parts with their footprints and available 3D models. Create and revise boards, generate layouts with automatic component placement and routing, inspect previews, and check saved layouts for blocking design issues. Export manufacturing ZIPs containing Gerber and drill files, a bill of materials, and component placement data, or download an editable EasyGerber (.egb) file. Start without signing up. Your agent uses one private board reference to create and continue a board, including catalog access, edits, layout, checks, previews, and exports, without a separate guest setup step or token to manage. To keep the board in your account or work with permitted saved personal or organization boards, complete EasyGerber sign-in and OAuth consent, then resume the same task. Account permissions, plan limits, and generation billing apply; support depends on your MCP client and installed integration.
Design, route, check, review and export manufacturable PCBs from plain language; KiCad import.
Design circuits, simulate and verify embedded firmware, and lay out PCBs with AI agents.
Autonomous 0-DRC PCB Routing, RF/DFM Pre-Flight & KiCad MCP Server (calligraphyeda.com).
Related MCP Servers
- AlicenseNot gradedqualityDmaintenanceEnables AI assistants to interact with KiCAD for PCB design automation. Users can design PCBs using natural language, including component placement, routing, checks, and export.1MIT
- AlicenseBqualityCmaintenanceEnables AI assistants to interact with KiCAD for PCB design automation, including schematic editing, component placement, routing, DRC/ERC, and export.10038 npm2MIT
- AlicenseAqualityBmaintenanceExposes Cadence EDA tools such as OrCAD Capture, Allegro PCB Designer, and PSpice to AI assistants, enabling them to browse PCB files, generate schematics and netlists, and run circuit simulations through a license-free, cross-platform interface.132MIT
- AlicenseNot gradedqualityCmaintenanceEnables AI agents to read and modify Pulsonix 10.x schematics and PCB layouts through the CAD tool's ActiveX scripting API on Windows. Supports inspecting and editing components, nets, netlists, BOMs and attributes, running ERC/DRC and CAM/plot outputs, and executing arbitrary scripts in headless or live mode.2MIT