EasyEDA Copilot

English | 简体中文 | Русский | Español

[图片] EasyEDA Copilot

MCP-based engineering automation for native EasyEDA Pro and JLCEDA documents.

EasyEDA Copilot connects MCP-capable AI agents to real schematic and PCB data. It supports schematic generation and reorganization, component resolution, constraint-driven PCB placement, checkpoint-backed routing transactions, structured design inspection, recovery, and native EasyEDA DRC.

[Build status] [Latest release] [License] [Discord] [Support EasyEDA Copilot development]

[EasyEDA Copilot creating and assembling an LDO schematic from a text specification]

_{Creating and assembling an LDO schematic from a text specification.}

Featured demonstration: BGA2869 2 GHz RF amplifier

A complete RF design workflow inside EasyEDA Pro: schematic organization, pin-level signal-path constraints, compact component placement, PCB routing, ground planes, and via stitching.

The RF ports are positioned on opposite board edges, the amplifier chain is kept ordered, and the bias network is placed close to the MMIC. The resulting components, tracks, vias, and copper zones remain editable as native EasyEDA objects.

Open video separately

More demonstrations

These examples cover larger controller boards and existing-document workflows. Every result remains editable as a normal EasyEDA project rather than being exported as a rendered mockup.

ESP32-C3 controller

A complete ESP32-C3 controller with power conversion, USB, CAN, RS-485, protected field I/O, external connectors, and antenna placement constraints.

The workflow demonstrates multi-page schematic generation, functional placement, board-edge and antenna constraints, power and signal routing, copper planes, via stitching, inspection, and DRC-driven repair.

MIMXRT1011 controller

A dense four-layer microcontroller design demonstrating placement and routing around a high-pin-count MCU, multiple interfaces, decoupling groups, board-edge connectors, mounting holes, and mechanical access constraints.

Schematic beautification

EasyEDA Copilot reads an existing schematic, identifies functional groups, saves a document checkpoint, and reassembles the page into named blocks while retaining its electrical connectivity and component identities.

More editable examples are available on OSHWLab.

Quick start

Requirements

• EasyEDA Pro Desktop;
• Node.js >=20.19;
• an MCP-capable client such as Codex or Claude Code.

1. Install the EasyEDA extension

Download the latest .eext package from GitHub Releases.

In EasyEDA Pro:

1. Open Settings -> Extensions -> Extensions Manager.
2. Select Import Extensions.
3. Choose the downloaded .eext file.
4. Enable External Interactions.

[Enable External Interactions for EasyEDA Copilot]

2. Add the MCP server

Codex:

codex mcp add easyeda-copilot -- npx -y easyeda-copilot-mcp

Claude Code:

claude mcp add easyeda-copilot -- npx -y easyeda-copilot-mcp

For generic MCP configuration and local builds, see the MCP package documentation.

To use the standalone skill instead of MCP client configuration, build it from this repository. Skill archives are not published in Releases:

npm cinpm run build:skillcd skill/scripts/runtimenpm install --omit=dev

Then install the generated skill/ directory as described in the skill installation guide.

3. Open a project

1. Start the MCP client with EasyEDA Copilot enabled.
2. Open EasyEDA Pro and the target schematic or PCB document.
3. Ask the agent to inspect the currently opened EasyEDA project and begin the design workflow.

The extension discovers the local MCP bridge automatically. Copilot -> MCP pauses or resumes the connection.

Capabilities

Checkpoints, transactions, and recovery

EasyEDA Copilot uses full-document checkpoints and explicit application boundaries to protect existing engineering work. Changes are previewed, applied to native EasyEDA documents, inspected, and then kept, repaired, or restored.

Checkpoints contain the complete EasyEDA document source, not only a list of agent actions. Existing tracks, vias, and copper zones are preserved by default and treated as fixed routing obstacles. Copper is replaced only when a routing program explicitly selects the affected nets and object types through clearRouting(...).

A successfully applied partial routing result remains available for inspection and focused repair. An application exception restores the pre-routing checkpoint. Recovery protects the document from failed mutations; electrical and manufacturability review remains part of the normal engineering workflow.

Schematic workflow

The schematic integration works with structured EasyEDA component, pin, net, and page data.

1. Inspect the current project and schematic page.
2. Resolve exact components.
3. Save a document checkpoint.
4. Create a circuit, complete an existing fragment, replace selected components, or reorganize the page into named functional blocks.
5. Apply the result to the native EasyEDA document.
6. Save and inspect the result, then keep, revise, or restore it.

Schematic beautification covers the complete current page and preserves component identities through destructive reassembly. Multi-page annotation supports two modes: preserve repairs only duplicate or unnumbered designators, while resequence recalculates trailing numbers in page and position order. Multi-part components are renamed together.

PCB workflow

PCB placement, routing, inspection, and DRC are provided through the MCP interface.

1. Synchronize the schematic with its linked PCB document.
2. Inspect schematic groups and complete connectivity to identify provisional functional blocks and local passive ownership.
3. Inspect the current board outline, footprints, placement, copper layers, and DRC rules.
4. Describe mechanical, functional, and electrical intent in the placement DSL.
5. Review the mechanical preview and the final placement preview.
6. Assemble the approved placement in the opened EasyEDA PCB document.
7. Define stack, routing rules, net classes, planes, special nets, fanout, and via stitching in the routing DSL.
8. Apply the routing program as one checkpoint-backed transaction.
9. Inspect critical nets, remaining connections, copper, and native DRC results.
10. Keep the result, apply a focused repair, or restore the previous checkpoint.

Existing placement can be retained with preserve(...). Placement assembly preserves existing copper and unrelated board objects. Existing routing is preserved unless the routing DSL explicitly calls clearRouting(...) for a selected scope.

Long placement and routing operations return an operation ID. The MCP client can wait for completion, cancel the work, or retry application of an already prepared result without running the operation again.

Detailed placement and routing references:

• PCB placement instructions
• PCB placement DSL
• Mechanical validation
• PCB routing instructions
• PCB routing DSL
• Verification and recovery

Compatibility

PCB assembly, routing integration, inspection, and native DRC are verified primarily against EasyEDA Pro Desktop V3.2.149.

MCP and the legacy built-in interface

MCP is the primary and actively developed EasyEDA Copilot interface. The original built-in interface remains available for its integrated chat and SPICE workflow.

New workflows and bug reports should use MCP unless the issue is specific to the legacy interface.

Architecture and data processing

Codex / Claude Code / another MCP client                    |                    | stdio                    v          easyeda-copilot-mcp                    |                    | WebSocket on 127.0.0.1:8787                    v        EasyEDA Copilot extension                    |                    v          Open EasyEDA document

The EasyEDA extension, MCP bridge, document application logic, checkpoint system, inspection tools, and PCB routing package are open source. The MCP bridge communicates with the EasyEDA extension locally through 127.0.0.1.

The standalone eda-copilot-backend npm library resolves components through public EasyEDA APIs and generates schematic and PCB placement plans locally. Plans are applied, checkpointed, inspected, and DRC-checked through the EasyEDA extension. The legacy built-in chat uses its own service configuration. PCB routing is based on the open-source eda-copilot-router package.

Documentation

• MCP package and client configuration
• Complete MCP workflow
• Schematic workflow
• Schematic circuit modifications
• Project and page management
• Settings and permissions
• Attaching circuits to an AI agent
• Assembling circuits from an AI agent

Development

Extension sources, UI, resources and build configuration live in extension/; mcp/ and shared/ are sibling workspaces. Root build and development commands remain the entry point. The .eext output is written to build/dist/. See extension development.

Build the extension and MCP package from source:

git clone https://github.com/biosshot/easyeda-copilot.gitcd easyeda-copilotnpm cinpm run buildnpm run check --workspace=mcp

Published backend/router packages are installed by default. For joint development, dependency switching, and platform limits, see local development. Building the extension requires Node ^20.19.0 or >=22.12.0.

The standalone PCB routing package is developed in biosshot/eda-copilot-router.

Support

If EasyEDA Copilot saves you engineering time, you can support its continued development through Tribute. Contributions help maintain the extension, MCP integration, routing tools, documentation, and new design workflows.

Community

Questions, bug reports, design examples, and contributions are welcome through GitHub Issues and Discord.

License

EasyEDA Copilot is distributed under the MIT License.