Skip to main content

easyeda-agent

259Stars39Forks12Issues1Watchers

Package JLC EDA Professional as MCP toolsets and Skills callable by DSH Agent, enabling the model to drive schematic and PCB automation within Harness.

Evidence3/5methodologySourceInstallMaintenanceDSH versionSecurity scan
Machine-auditedInstall commandRepo verifieddsh-plugin topicLicenseREADMEAI wiki
Language
Go
License
NOASSERTION
Branch
main
agent-skillai-agentclaude-codedsh-plugineasyedaedaelectronicsgolang

Install

cmdweb profile
$ dsh plugin --profile web add github:zhoushoujianwork/easyeda-agent

Run the command above in your terminal to install this plugin via the dsh CLI. You can switch Profile in the top-right corner. New to dsh? Read the beginner tutorial

Install via your agent

Install the DeepSeek Harness plugin zhoushoujianwork/easyeda-agent for me: review the repository at https://github.com/zhoushoujianwork/easyeda-agent first, then run the install command and verify the plugin loads successfully.

Paste this instruction to the DSH Web GUI assistant — it will install and verify for you.

One-Line Positioning

Wraps JLCEDA EDA Professional into an MCP toolkit and workflow Skill callable by DSH Agent, enabling the model to drive schematic/PCB automation within Harness (component placement, routing, PCB layout, copper pour, DRC, BOM export). Note: This plugin only bridges the built-in stdio MCP server to DSH and registers Skills into the global layer; the actual Go CLI/daemon binary and EasyEDA-side .eext connector must be installed separately using the official one-click script.

Core Capabilities

  • Activates an easyeda namespace MCP bridge in the DSH profile, exposing tools like easyeda_health / easyeda_actions / easyeda_schematic / easyeda_pcb / easyeda_board / easyeda_document / easyeda_project / easyeda_artifact / easyeda_system / easyeda_blocks / easyeda_workflow for the model
  • Registers Agent Skills from skills/easyeda-agent/ (including S0–S6 schematic flows, P0–P10 PCB flows, gatekeeper specs, reference data, Python/JS validation scripts), using an isolated instance with providerName: easyeda to avoid conflicts with the official bundle's skill-filesystem
  • Forwards all typed actions from the Go CLI (including schematic component placement/routing/partitioning, PCB auto-placement/copper pour/4-layer power plane, board binding, artifact export, system notify toast) as easyeda_<domain> MCP tools to the model, each action carrying a Mutates tag to indicate read-only/destructive semantics
  • Provides a self-describing easyeda_actions tool: the model can filter the action directory by domain/keyword/mutate-status, replacing the need to read individual READMEs
  • Exposes persistent project design workflow state machine via easyeda_workflow (init/status/advance/confirm/reset), enabling S0–S6 + P0–P10 gatekeeper confirmations to be persisted by the Agent rather than just existing in the conversation
  • Exposes embedded circuit block library via easyeda_blocks (CH340 USB serial, ESP32 auto-download, button debounce, etc.), allowing the Agent to query blocks before placing peripherals and reuse topologies on match

Technical Implementation

  • Languages: TypeScript (MCP server) + Go (CLI/daemon, not in this package) + Shell (cordis.patch.yml declarative injection)
  • Key Dependencies: @deepseek-ai/dsh-mcp-client (host's built-in MCP bridge plugin, this package only declares activation), @deepseek-ai/dsh-skill-filesystem (host's built-in skill-filesystem, this package declares an isolated instance), @modelcontextprotocol/sdk 1.30.0 (stdio server implementation), local easyeda Go binary (MCP server spawns via child_process, path determined by EASYEDA_BIN env var)
  • Architecture Pattern: Pure declarative cordis bundle patch—cordis.patch.yml contains two insert rules that bring up the MCP bridge and isolated skill-filesystem during the apply phase; runtime has no custom JS/TS code, bridging delegates to host in-box plugin, sandbox execution delegates to Go daemon. MCP server uses stdio transport, WebSocket communication with EasyEDA is entirely within the daemon
  • Entry Files: cordis.patch.yml (DSH integration entry), mcp/src/server.mjs (stdio MCP server implementation), mcp/src/core.mjs (CLI invocation + tool definitions); Go CLI entry at cmd/easyeda/, EasyEDA-side .eext at extension/, both outside this DSH plugin loading scope

Use Cases

Use when the user asks DSH model to do "EasyEDA Pro-based circuit board design automation"—typical scenarios include generating schematics from a single requirement sentence, syncing routed schematics to PCB, running DRC checks and exporting BOM/netlist, or when EasyEDA is already open, having the model directly place components/route/pour copper in it. This plugin targets hardware owners, EDA engineers, and automation integrators; not suitable for "zero EasyEDA experience just want to run a hello world" pure DSH users, since there are many prerequisites (CLI binary + .eext + EasyEDA-side toggle).

Prerequisites & Compatibility

DependencyMinimum VersionNotes
DSH HostNot declared in this packageThis package references @deepseek-ai/dsh-mcp-client and @deepseek-ai/dsh-skill-filesystem in cordis.patch.yml, depending on host DSH to bundle these two in-box plugins into the installation directory; version determined by host build time, this package has no peerDependencies
Node.js>= 20.17.0Both package.json#engines and mcp/package.json#engines are >=20.17.0; below this version the MCP server will fail to start due to Node self-rejection
easyeda Go CLI/daemonSame major/minor version as this plugin (e.g., this package 0.25.x with CLI 0.25.x)Installed via official one-click script (`curl -fsSL https://raw.githubusercontent.com/zhoushoujianwork/easyeda-agent/main/install.sh
EasyEDA Agent Connector .eextStrictly same version as CLIMust import .eext in EasyEDA Pro's extension center (script prints download URL or search "EDA Agent Connector" in LCSC plugin market for one-click install); sideloaded version has no in-place auto-upgrade, requires manual uninstall of old version then install new; version mismatch shows connector as stale in daemon health
EasyEDA Proeda ~3.0 (extension.json#engines)Must enable "Allow External Interaction" in an open project, otherwise the connector's WebSocket can never connect to the local daemon
Platform—Makefile cross-compiles darwin/amd64+arm64, linux/amd64+arm64, windows/amd64; this DSH plugin itself is platform-independent pure JS/JSON/YAML with no native module dependencies

Installation

dsh plugin --profile web add github:zhoushoujianwork/easyeda-agent

Configuration Options

ConfigTypeDescriptionDefault
EASYEDA_BIN (env var)stringOverrides the easyeda binary path spawned by MCP server; empty means search in PATHeasyeda (PATH lookup)
easyeda-mcp serverNamestring (declarative)MCP tool namespace prefix; tool names seen by model are like mcp__easyeda__easyeda_schematiceasyeda
easyeda-skill-fs providerNamestring (declarative)Isolated instance namespace identifier, avoids conflict with official bundle's skill-filesystemeasyeda
easyeda-skill-fs customSkillDirsstring array (declarative)Only scans skills/easyeda-agent/ within this package, doesn't mix in host's default skill directorynode_modules/easyeda-agent-dsh/skills/easyeda-agent (relative to profile directory)
includeDefaultRootsboolean (declarative)Whether to also scan host's default skill directory; this package sets to false to avoid conflict with official presetsfalse

This package has no runtime schema that users can directly modify in profile config files—all adjustments are done via the above declarative fields or EASYEDA_BIN env var. To enable more toggles (like custom MCP tool whitelist), you need to fork mcp/src/server.mjs or modify the in-box @deepseek-ai/dsh-mcp-client behavior in the host.

FAQ

Q: Installation command succeeded but mcp__easyeda__easyeda_* tool list is empty?

A: Check three things—whether easyeda daemon is running (easyeda health should return status: found), whether EasyEDA has a project open with "Allow External Interaction" enabled, and whether the connector .eext is actually loaded into EasyEDA (menu bar showing "EDA Agent" group means it's loaded). MCP depends on bidirectional connectivity between local daemon and EasyEDA window; missing either will cause all typed actions to receive NO_CONNECTOR.

Q: Getting "STALE_READ" / "action can't read latest data after PCB mutation" errors?

A: This is a hard constraint of the daemon: any pcb.* mutation must first run easyeda doc reload before reading/judging/DRC; reading directly without reload causes the daemon to refuse and tell you what to run next. Connection error spikes on the same network usually require pour-rebuild first, not a real disconnection.

Q: easyeda update --check reports connector is behind but update doesn't upgrade it?

A: Sideloaded .eext is not in the auto-upgrade scope. easyeda update will print the lagging connector version and re-import address; manual uninstall old version and import new version in EasyEDA extension center is required; if installed from LCSC plugin market, the market will auto-upgrade in-place but version may lag CLI by a few minors.

Q: Skill conflict/load failure prompts under DSH web profile?

A: cordis.patch.yml intentionally declares an isolated skill-filesystem instance with includeDefaultRoots: false to avoid conflicts; if still conflicting, someone likely manually added a second easyeda-skill-fs row in the same profile's cordis.patch.yml or changed providerName causing name collision. Dump config and delete the extra row.

Q: Which tools can run offline/without external network?

A: easyeda_blocks (query built-in circuit block library), easyeda_actions (read offline JSON of action directory), easyeda_health (check local daemon status) don't depend on EasyEDA online or external network; the rest like easyeda_schematic / easyeda_pcb require EasyEDA window open, some actions also query LCSC library on demand.

Learning Curve

Advanced — Users need to understand DSH profile/cordis layering (installing this plugin is only the first step), plus manually install Go CLI binary, import .eext connector, enable EasyEDA "Allow External Interaction" toggle; missing any step will result in MCP tool list "installed but not callable". The advantage is that once all four pieces are in place, the model can drive EasyEDA with a full set of typed actions and run gatekeeper flows with the persistent workflow state machine.

Known Issues & Limitations

  • internal/daemon/connect.go:19-21 marks a TODO: daemon temporarily skips origin verification when accepting WebSocket (InsecureSkipVerify: true), waiting for JLC official public extension origin to add precise whitelist; current daemon only binds 127.0.0.1, risk surface is limited
  • MCP bridge in cordis.patch.yml uses dsh-mcp-client, skill registration uses dsh-skill-filesystem, both are DSH host's in-box plugins—if host version is too old/trimmed these, this package activation will fail
  • This package writes no user files, creates no persistent state; uninstalling this package won't clean up Go CLI, .eext, or EasyEDA-side toggles
  • MCP server deliberately doesn't expose debug.exec_js domain to the model, limiting the "arbitrary JavaScript execution" escape hatch; this also means some experimental actions not yet typed (bare JS calls) can only be manually run in terminal via easyeda call debug.exec_js
  • EASYEDA_BIN env var is shared across multiple processes (e.g., multiple agents in same profile) causing race conditions; usually resolved by having all agents share the same daemon
  • Three-party versions (CLI / Skill / Connector) must be aligned; otherwise easyeda daemon health marks connector as stale; sideloaded .eext has no in-place auto-upgrade, requires manual maintenance
  • easyeda update --check --exit-code exits with code 10 in CI which can be gated, but only reflects CLI/skill/connector version alignment status, doesn't verify EasyEDA side is truly enabled or daemon is running
  • This package's current package.json#version is 0.25.1 while extension/extension.json#version in the repo is 1.1.0—CLAUDE.md notes make release process will unify both, but current commit state is not yet synced; when encountering "easyeda health marks stale" prioritize CLI-side version
  • Subject to JLC official eda.* API limitations: auto-router for maze files, interactive routing UX, controlled impedance Z0, teardrop, programmatic undo, incremental import_changes and other capabilities cannot be expressed via typed actions, must use external Freerouting (DSN round-trip) or manual UI fallback

Read the usage guide →

Install steps, key points, FAQ and compatibility for this plugin — auto-derived from indexed fields.

Listing badge

Listed on deepseek-plugin.org
[![Listed on deepseek-plugin.org](https://img.shields.io/badge/listed_on-deepseek--plugin.org-007EC6)](https://deepseek-plugin.org/plugins/zhoushoujianwork/easyeda-agent)

Paste this markdown into your GitHub README to link back to this listing. The badge only states the listing — not a security endorsement.

← Back to plugin directory