Easyeda

MCP server that controls a running EasyEDA Pro instance from Claude Code (or any MCP client), via JLCEDA's easyeda-api-skill bridge and the run-api-gateway extension.

Version 0.2.0

How it works

MCP client ⇄ (stdio) ⇄ easyeda-mcp ⇄ (HTTP, port 49620-49629) ⇄ bridge server ⇄ (WebSocket) ⇄ EasyEDA Pro

The bridge server and the EasyEDA-side extension are JLCEDA's published artifacts — this server wraps them with fast discovery (cached port, parallel scan, single round trip per call) and high-level tools so common actions are one tool call instead of hand-written scripts.

Tools

The last three distill hard-won behavioral traps from real board work (mixed 1-mil/10-mil getters, the getNetlist "i is not iterable" trap when a PCB tab is active, and importChanges silently no-op'ing on Unique-ID mismatches) into tools that handle them for you.

Setup

1. Install the easyeda-api-skill bridge and the run-api-gateway.eext extension in EasyEDA Pro (enable its External Interactions permission).
2. Point this server at the bridge script if it's not at the default path: EASYEDA_BRIDGE_SCRIPT=/path/to/bridge-server.mjs
3. Register with your MCP client, e.g. for Claude Code:

{
  "mcpServers": {
    "easyeda": { "command": "node", "args": ["/path/to/easyeda-mcp/index.mjs"] }
  }
}

Known limitation: global DRC rule writes

EasyEDA Pro v2.2.47.x has an engine bug: the BETA overwriteCurrentRuleConfiguration() API deadlocks and saveRuleConfiguration() is non-functional. easyeda_drc_set_rules therefore fast-fails global config writes (~5s) with guidance, while per-net, region, and net-by-net rule writes work fully. If a newer EasyEDA build fixes the API, the fast-fail can be removed.

Development

npm run smoke                        # spawns the server, checks tool registration + health
node --test test/deep-merge.test.mjs # unit tests