Name: EasyEDA
Author: zzvllvzz

EasyEDA MCP

Read and draw EasyEDA Pro schematics and PCBs through a bridge extension, with guarded edits.

Grade A Local · stdio No auth needed 12 tools v0.1.0 MIT

No reviews yet by zzvllvzznpm Runs on your machine, nothing hosted

93/100

trust score

tools declared

local

runs on your machine

—

downloads a day

What it does

Read and draw EasyEDA Pro schematics and PCBs through a bridge extension, with guarded edits.

Quickstart

# 1 — add it to Claude Code
claude mcp add --scope user zzvllvzz-easyeda-mcp '--' npx -y easyeda-pro-mcp

# 2 — ask your agent for something these tools do
#   eda_status, eda_exec, eda_call and 9 more

EasyEDA costs nothing on mcprush: there is no plan to choose here, no cap to set and nothing mcprush can bill you for.

Publishernot claimed

zzvllvzz1 server

1 category

All 1 server

Collected from a public index. Nobody has claimed this account, so nothing here was written by its author — claim it if it is yours.

Installation

Where are you running it?

Every route below installs the same thing and ends at the same approval screen. This one runs on your machine: your client starts EasyEDA as a process under your own user, with your files and your network, so the tool surface below is what it can do to your computer rather than to a server somewhere else. Its scan result is on the Security tab — read the surface before you approve it.

Claude Codedeclared by this listing

This is a public server: you run it yourself and this marketplace is not in the path. You need Node.js — the current LTS (24) is the safe choice; npx comes with it. Claude Code registers it in one command; --scope user makes it available in every project. The '--' is in quotes so that PowerShell passes it on.

claude mcp add --scope user zzvllvzz-easyeda-mcp '--' npx -y easyeda-pro-mcp

Reconnect, or start a new session, and the tools appear in the model’s tool list.

Free on mcprush, and it runs from its publisher’s own package: this marketplace is not in the path, so there is no key of ours to hold and no card to add.

What it asks of you

Nothing is required, but it can take EASYEDA_MCP_PORT (Local port of the bridge extension. Defaults to 49731; the extension has to use the same port.), EASYEDA_MCP_OUT (Folder for exported files. Defaults to ~/.easyeda-mcp/out.), EASYEDA_MCP_ORIGINS (Extra browser origins allowed to connect, comma separated.) if you want to set them.

What it writes

One config entry your client uses to start the process locally. A local server runs with your file system and your network, which is why it is priced without metering.

What you approve

12 tools, with what each one reads, writes and reaches shown before you agree — the same list on every route above. Read the tool surface.

Tool surface

What the model actually sees. Descriptions are diffed on every release — see version history.

Only tools that write or reach the network

Read from its source code. A server that builds its tool list when it starts can list more tools than this.

Check the bridge: is EasyEDA Pro connected, which editor/extension version, and what project/document/page is active.

Parameter	Type	Required	Notes
waitMs	integer	no	How long to wait for EasyEDA to connect before giving up (default 8000).

Run JavaScript inside EasyEDA Pro and get the returned value. The code is the body of an async function with eda (the EasyEDA extension API), h (helpers), args (your JSON), console (captured) and store (object that persists between calls). Use return for the result. Do many operations…

Parameter	Type	Required	Notes
code	string	yes	Body of an async function. Example: const w = await h.wires('GND'); return w.length;
args		no	Any JSON value, available in the code as args.
timeoutMs	integer	no	Time limit in ms (default 30000). Code that times out keeps running in EasyEDA.
maxChars	integer	no	Inline result limit (default …); larger results are saved to a file and previewed.
saveTo	string	no	Absolute path: save the result (or the returned File) there instead of returning it inline.

Call one EasyEDA API method by path, e.g. method 'sch_PrimitiveWire.getAll' with args ['GND']. Shortcut for simple reads and single writes; for anything with loops use eda_exec. Look up signatures with eda_api.

Parameter	Type	Required	Notes
method	string	yes	Path under eda, e.g. dmt_Schematic.getCurrentSchematicPageInfo
args	array	no	Positional arguments (default none).
timeoutMs	integer	no	—
maxChars	integer	no	—
saveTo	string	no	—

Look up the EasyEDA Pro extension API (offline, from the official typings; doc comments are in Chinese). query: keyword search over method names and docs. name: full listing of a class/eda object (sch_PrimitiveWire), an interface, enum or type, or one method with remarks and example…

Parameter	Type	Required	Notes
query	string	no	Keywords, e.g. 'netlist' or 'pin modify'.
name	string	no	Class, eda property, interface, enum, type, or Class.method.
limit	integer	no	Max search results (default 20).
examples	boolean	no	With name of a class: include remarks and examples for every method (long).

Read the active schematic page compactly. what: 'summary' (counts, designators, net names of wires), 'parts' (components with pin coordinates), 'wires', 'snapshot' (parts+flags+wires), 'nets' (whole-schematic netlist {net: pins}), 'net' (one net by name or by pin like 'U1.3', needs net), 'check'…

Parameter	Type	Required	Notes
what	string	no	—
des	array	no	Only these designators (parts).
net	string	no	Net name (wires, net) or a pin like U1.3 (net).
region	array	no	[x1,y1,x2,y2]
pins	boolean	no	Include pins for parts/snapshot (default true).
size	array	no	what:'free': [width, height] of the block to fit.
count	integer	no	what:'free': how many places to return (default 1).
maxChars	integer	no	—
saveTo	string	no	—

Apply a list of drawing operations to the active schematic page as ONE change: afterwards either all of it is on the page or none of it. The netlist is read before and after (guard): nets with different names that became one net are a short, and a short takes the whole change back, as does a…

Parameter	Type	Required	Notes
ops	array	yes	—
trial	boolean	no	Do it, report what it does to the nets, then take everything back.
expect	object	no	{NET: ['U1.3','R2.1']}: these nets must consist of exactly these pins afterwards, else the change is taken back. A key starting with '?' checks an unnamed net.
allowShorts		no	true, or a list of net names that may be joined on purpose.
rollback	boolean	no	Default true: take everything back on a failed op, a short or a failed expect. false keeps what was done.
guard	boolean	no	Default true. false skips the two netlists (faster, no short detection).
keepGoing	boolean	no	Continue after a failed op (turns rollback off unless it is set).
verbose	boolean	no	Return an entry for every op, not only parts and problems.
timeoutMs	integer	no	Default 180000.

Export from the active schematic to a file and return its path: pdf (look at the real drawing; open the path with the Read tool), png, svg, netlist (PADS text), bom (csv), view (image of what the canvas currently shows; may be stale).

Parameter	Type	Required	Notes
format	string	yes	—
path	string	no	Absolute file path or directory. Default: ~/.easyeda-mcp/out/
options	object	no	Passed to h.exportFile: {name?, params?, resolution?, type?, tabId?, object?, objectParams?}. pdf exports the current page by default; object: 'Current Schematic' or 'All Schematic' for more.
timeoutMs	integer	no	Default 90000.

Search the EasyEDA/LCSC device library by words ('100nF 0402 X7R', 'STM32F103C8T6') or look up LCSC numbers. Returns name, LCSC number, footprint, JLCPCB class (Basic/Extended) and the uuid pair that {op:'part', device:{uuid, libraryUuid}} takes.

Parameter	Type	Required	Notes
query	string	no	Words to search for.
lcsc	array	no	Instead of query: LCSC numbers like C25804.
limit	integer	no	Default 10.
page	integer	no	—
datasheet	boolean	no	Include datasheet links.

Read the active PCB (open one with pcb_do action:'open'). what: 'info' (layers, rule set, outline size, counts), 'parts' (components; pads:true adds pad coordinates and nets), 'tracks', 'vias', 'shapes' (polylines, pours, regions, fills, texts), 'nets' (pads, track length, tracks and vias per net;…

Parameter	Type	Required	Notes
what	string	no	—
des	array	no	parts: only these designators.
pads	boolean	no	parts: include pad coordinates.
net	string	no	tracks, vias, nets: only this net.
layer		no	tracks: layer number or name (top, bottom, topsilk, outline, inner1...).
unit	string	no	—
max	integer	no	drc: how many errors to list (default 60).
maxChars	integer	no	—
saveTo	string	no	—

Apply a list of operations to the active PCB as ONE change. The design rule check runs before and after (guard): a new error other than a not-yet-routed connection (clearance, short, overlap with a keep-out) takes the whole change back, as does a failed op; pours are refilled before judging.…

Parameter	Type	Required	Notes
ops	array	yes	—
unit	string	no	—
trial	boolean	no	Do it, report the rule check, then take everything back.
rollback	boolean	no	Default true: take everything back on a failed op or a new rule error.
allowErrors	boolean	no	Keep the change even if it adds rule errors (they are still reported).
guard	boolean	no	Default true. false skips the rule checks.
rebuild	boolean	no	Default true: refill pours before the rule check.
keepGoing	boolean	no	—
verbose	boolean	no	—
timeoutMs	integer	no	Default 300000.

Whole-board actions. action: 'open' (open a PCB of the project by name or uuid, the first one by default), 'import' (bring the schematic's changes onto the board; lists the changes and applies them, apply:false only lists), 'rebuild' (refill all pours), 'autoroute' (EasyEDA's own router; props…

Parameter	Type	Required	Notes
action	string	yes	—
name	string	no	open: PCB name or uuid.
apply	boolean	no	import: default true.
props	object	no	autoroute: IPCB_AutoRoutingProps.
net	string	no	unroute: only this net.
timeoutMs	integer	no	Default 300000.

Export from the active PCB to a file and return its path: gerber (zip for fabrication), pnp (pick and place csv), bom, netlist, step, obj (3D), dxf, dsn (for external routers), ipc356, ipc2581, odb, testpoints, info, altium, pads, view (picture of what the canvas shows). Nothing is ordered:…

Parameter	Type	Required	Notes
format	string	yes	—
path	string	no	Absolute file path or directory. Default: ~/.easyeda-mcp/out/
options	object	no	Passed to h.pcb.exportFile: {name?, type?, unit?, layers?, objects?, ...}.
timeoutMs	integer	no	Default 180000.

Free

$0 forever

Every tool, no call limit
No card, and mcprush charges nothing for it
Source published under MIT
Runs on your machine — nothing of it reaches our gateway
Nothing to cap, because mcprush bills nothing

Nothing here is billable: mcprush charges nothing to install EasyEDA or to call it, at any volume.

ATrust score 93 / 100

Release 0.1.0 · scanned 15 Nov 2026

Two independent axes, because powerful and malicious are different questions. The grade is threat only. The capability level is blast radius, and it is never a penalty on the grade — it is priced as one subtract-only term in the score, where you can see it.

Threat score100

Client score93

Findings0 threat · 3 capability

Capabilityhigh

Coveragesource

Verificationrepo

Surface digest1e9421a8b6696e0c5ace7d369130827e4da99528f0d01dfe226497aa7bcdb09b

Score vectorthreat 100 → client 93

Term	Level	What it prices	Points
capability-exposure	high	capability blast radius (high) — client exposure if the model is manipulated	−6
verification-discount	repo	publisher verification (public source) — no provenance, but the source is public and inspectable	−1
coverage-honesty	source	inspection depth (source) — how much of the target the scan could see	−0

score = clamp(round(threatScore − E_cap − E_ver − E_cov), 0, 100). No model, no opinion, no network call at scoring time: the same methodology version against the same bytes always produces this number, and every line above is a field of the report rather than a summary of it.

What the scan could actually read

A grade is only as meaningful as its coverage, so the scanner publishes its own depth before it publishes its result.

Tool surfaceread

Implementation sourceread

Package metadataread

Live transportnot available

Tools were statically extracted from the published source (12 recovered), not enumerated from a running server. Tool-poisoning, Unicode-smuggling, capability and toxic-flow analysis ran on this inferred surface, but a mis-parsed registration could be missed or mis-attributed, so tool-derived findings are capped below “confirmed”. To grade the real runtime surface, scan the running server: --command "npx -y <package>".

Capability — what it could do if the model were manipulated

Tags derived from each tool’s schema and the implementation, not from what the tool calls itself. high is the level these add up to.

Tool	Capability tags	Why the tag was assigned
eda_status	no tags
eda_exec	code-exec	code-exec: keyword "exec" in tool name
eda_call	no tags
eda_api	no tags
sch_read	no tags
sch_draw	no tags
sch_export	no tags
lib_search	no tags
pcb_read	no tags
pcb_draw	no tags
pcb_do	no tags
pcb_export	no tags

Toxic-flow graph

The lethal trifecta, checked as a graph rather than as a checklist: untrusted input, a sensitive source and an external sink have to meet before there is a path worth worrying about.

The public result for this release does not print the flow graph, so there is nothing to show here. That is not the same as "no paths were found": what the scan did read is above, under coverage.

Supply chain and provenance

Integrityfirst-seen

Surface digest1e9421a8b6696e0c

Scanned2026-11-15

This is the first scan of this surface here, so there is nothing yet to compare it against.

Every result on this tab comes from one deterministic pass over the published package — offline, rule by rule, and auditable line by line above. Same methodology version, same bytes, same score.