EasyEDA MCP
Provides live, end-to-end PCB design inside EasyEDA Pro: schematic capture and readable wiring (orthogonal wire routing, power/ground symbols), multi-page schematics and framed sections, PCB placement, manual and automatic track routing, ground fan-out and copper pours, design-rule/layer configuration, silkscreen editing, DRC, and fab exports (Gerber, BOM, CPL, PDF, STEP, DXF, iBOM, JLCPCB bundle). Also renders design-data snapshots and exposes the full EasyEDA scripting API through a generic script tool and API search.
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.
EasyEDA MCP
Live, end-to-end PCB design in EasyEDA Pro for AI agents — schematic capture, readable wiring, live JLCPCB stock & part class, PCB placement, autorouting, copper pours, DRC and fab exports — through the Model Context Protocol.
Works with Claude Code, Claude Desktop, Codex, Cursor and any MCP client. Several agents can be connected to the same EasyEDA window at the same time.
Claude Code ─┐ ┌───────────────────────────┐
Codex ───────┼─ stdio ─ easyeda-mcp ─┐ │ EasyEDA Pro (desktop/web) │
Cursor ──────┘ (tools, routers, │ │ ┌─────────────────────┐ │
JLC live data) ├──┼─▶│ EasyEDA MCP runtime │ │
hub (ws://127.0.0.1:18765)│ (thin extension) │ │
│ └─────────────────────┘ │
└───────────────────────────┘Why this exists
Earlier EasyEDA bridges made an agent fight the tooling more than design the board. This project fixes every problem we hit in real projects:
Problem with older bridges | What EasyEDA MCP does |
Every edit needed a separate "prepare" + "confirm" round trip (hundreds of calls to wire one sheet) | Batch tools: place 80 parts or connect every net in one call |
Schematics were a wall of net labels |
|
Agent could not see the design, and screenshots kept pulling EasyEDA to the front |
|
Outputs of 100k–800k characters | Compact, filterable outputs; huge results spill to a file automatically |
"Extension is not connected" / Codex and Claude kicking each other off | Standalone hub: many agents + many EasyEDA windows at once, infinite auto-reconnect, heartbeat watchdog, version hand-over |
Via / track / outline creation "broken", silkscreen not movable | All working: correct API arguments, units, layer ids, plus the hidden EasyEDA rules below |
Updating a part wiped all its attributes and LCSC number | Attribute-safe modify: merges, re-sends, verifies |
| Exact LCSC matching everywhere |
Stock / Basic vs Extended had to be looked up by hand |
|
Power routing / copper areas were not controllable | Manual-first routing: tracks snap to pad refs ( |
Design rules, layers, copper settings out of reach |
|
One giant schematic page |
|
Work lost / user yanked to another tab | Every modifying tool saves the document it changed; |
Any API not wrapped by a tool was unreachable |
|
Extension updates needed manual re-import | The runtime self-updates from the MCP server ( |
Hidden EasyEDA behaviours this server handles for you
PCB API units are mil, schematic units are 0.01 inch, both Y-up. Tools take mm on the PCB.
A track only connects to objects that already exist when it is created → vias are always placed before tracks.
A track ending in the middle of another track is not connected → T-junctions are split automatically.
modify()on a component replacesotherPropertywholesale and resets the supplier part → always merged.Pours are only filled after
rebuildCopperRegion(); islands are removed (preserveSilos=false).EasyEDA stops rendering when its window is hidden → snapshots are rendered from design data inside the page instead (no focus stealing).
Rule-configuration writes need the inner
configobject; schematic rectangles read back with inverted Y; page renames only apply to an open page; API vias needdesignRuleBlindViaName: null— all handled."Update PCB from schematic" opens a confirmation dialog → confirmed automatically.
Related MCP server: jlc-mcp
Install
1. MCP server
# Claude Code
claude mcp add easyeda -s user -- npx -y easyeda-live-mcp
# Codex (~/.codex/config.toml)
[mcp_servers.easyeda]
command = "npx"
args = ["-y", "easyeda-live-mcp"]Claude Desktop / Cursor (mcpServers JSON):
{ "mcpServers": { "easyeda": { "command": "npx", "args": ["-y", "easyeda-live-mcp"] } } }Requires Node.js 20+.
2. EasyEDA Pro extension (once)
Get
easyeda-mcp.eextfrom the latest release (ordist/easyeda-mcp.eextafternpm run build;easyeda_statusprints the path of the bundled copy).EasyEDA Pro → Settings → Extensions → Extension Manager → Import → choose the file.
In the extension's entry enable Allow External Interaction (and Display in top menu).
It connects by itself within seconds (top menu MCP → Status). Later runtime updates are pushed by the server — no re-import.
Tools (41)
Area | Tools |
Connection & power tools |
|
Parts (live JLCPCB) |
|
Schematic |
|
PCB |
|
Manufacturing |
|
A full board, start to finish
easyeda_status
easyeda_project {action:"create", name:"USB 555 Blinker"}
jlc_search {keyword:"NE555", noFeeOnly:true}
sch_place {parts:[{lcsc:"C7593", designator:"U2", x:750, y:330}, {lcsc:"C25819", designator:"R5", value:"47kΩ", x:620, y:310, rotation:90}, …]}
sch_connect {nets:[{name:"VBUS", pins:["J1.A9","U2.VCC",…]}, {name:"GND", pins:[…]}, {name:"THR", pins:["R5.1","U2.THRES","U2.TRIG","C4.2"]}, …]}
sch_section {title:"555 LED BLINKER", designators:["U2","R4","R5","C4"]}
sch_snapshot {full:true} · sch_check · bom_check {boards:5}
pcb_sync
pcb_rules {action:"set", clearance:0.15, track:{default:0.25}, via:{diameter:0.6, hole:0.3}}
pcb_outline {width:40, height:30, cornerRadius:2}
pcb_holes {size:"M3"}
pcb_place {items:[{ref:"J1", x:4.2, y:15, rotation:270, lock:true}]} · pcb_auto_place
pcb_tracks {tracks:[{points:["U1.4","C2.2"], width:0.6}, {points:["U1.4",[17.2,11.3],"R3.1"], width:0.5}]} # power by hand
pcb_fanout {net:"GND"}
pcb_autoroute # leftover signals only; ground skipped
pcb_pour {net:"GND", layers:"both", stitchPitch:6}
pcb_silkscreen {action:"tidy"} · pcb_silkscreen {action:"text", text:"BLINKER v1.0", x:24, y:3}
pcb_drc # → 0 violations
export_files {kinds:["jlcpcb"]}See docs/agent-guide.md for the recommended workflow and layout conventions.
Configuration (environment variables)
Variable | Default | Meaning |
|
| hub port (set the same port in the extension: MCP → Set Hub Port) |
|
|
|
| – |
|
| – |
|
|
| max characters per tool result before spilling to a file |
|
| output/export directory |
Development
npm install
npm run build # builds dist/ (server, hub, cli) and dist/easyeda-mcp.eext
npm test # unit tests (routers, connectivity)
node dist/index.js cli status
node dist/index.js cli exec "return eda.sys_Environment.getEditorCurrentVersion()"Layout: extension/ in-editor runtime · src/hub.ts router · src/client.ts hub client · src/eda/lib.edajs helper library hot-installed into EasyEDA · src/sch/* schematic connectivity + router · src/pcb/* placer, router, connectivity · src/tools/* MCP tools.
License
MIT
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.
Turn datasheets into source-backed JSON contracts, pinout matrices, and KiCad CAD for AI agents.
Related MCP Servers
- AlicenseCqualityDmaintenanceEnables AI coding assistants to control JLCPCB EDA for PCB automation, exposing 39 tools for component manipulation, routing, copper pour, DRC, and more. Includes a built-in PCB agent for orchestrating multi-step tasks.59282MIT
- AlicenseNot gradedqualityDmaintenanceLocal Model Context Protocol server that exposes EasyEDA Pro design capabilities as MCP tools, enabling project inspection, schematic editing, PCB design, validation, and manufacturing exports through natural language.MIT
- FlicenseNot gradedqualityCmaintenanceEnables AI agents to automate 嘉立创 EDA Professional through MCP, including schematic and PCB editing, component search and placement, net routing, DRC, and design capture.-
- AlicenseNot gradedqualityAmaintenanceEnables MCP-capable AI agents to generate and reorganize schematics, resolve LCSC components, place and route PCBs with custom DRC constraints, inspect design data, and safely apply, repair, or restore changes in native EasyEDA Pro and JLCEDA documents.219MIT