Prototype · Preview: every server in the official registry, synced every 30 minutes. Reviews and accounts come in a later step.
PopNx MCPMCP servers for people who use AI · explained in plain words

EasyEDA Copilot

by biosshotversion 1.3.2i★ –iRuns on your computer
Registry nameio.github.biosshot/easyeda-copilot

Install

Overview

Description from the maker (original English)

AI tools for EasyEDA Pro schematics, PCB placement and routing, SPICE simulation, and DRC.

PopNx MCP’s three pillars

These three are never merged into one score: opinions, measurements and popularity are different things.

What you can do with it

We have not written a plain-language summary for this one yet. Below are the facts we read from the registry.

  • Connection: Runs on your computer
  • Transport: stdio
  • Category: Other

Install

Pick the AI app you use, then copy the settings.

Before you install

  • Basic checks: 1 of 1 passed
  • Runs on your computer with your user’s permissions (files, network, apps).
  • The registry lists no key to fill in.

You need

  • npmNode.js installed (for the npx command)

Which app do you use?

Pick your app above. We remember it, so next time the button says “Install in …”.

Open Claude Desktop → Settings → Developer → Edit Config, and paste this into claude_desktop_config.json

{
  "mcpServers": {
    "easyeda-copilot": {
      "command": "npx",
      "args": [
        "-y",
        "easyeda-copilot-mcp"
      ]
    }
  }
}

Run this in your terminal

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

Open in Cursor

Or copy the settings yourself

Paste into .cursor/mcp.json in your project, or ~/.cursor/mcp.json

{
  "mcpServers": {
    "easyeda-copilot": {
      "command": "npx",
      "args": [
        "-y",
        "easyeda-copilot-mcp"
      ]
    }
  }
}

Your browser asks to open the app, then the app shows the settings and asks you to confirm. Key values are left empty for you to fill in.

Open in VS Code

Or copy the settings yourself

Paste into .vscode/mcp.json in your project

{
  "servers": {
    "easyeda-copilot": {
      "type": "stdio",
      "command": "npx",
      "args": [
        "-y",
        "easyeda-copilot-mcp"
      ]
    }
  }
}

Your browser asks to open the app, then the app shows the settings and asks you to confirm. Key values are left empty for you to fill in.

This one runs on your computer, and ChatGPT can only connect to servers on the internet. Pick another app.

Your choice stays on this device in a cookie; no account needed.

These settings are generated from the maker’s registry entry. If the README says otherwise, follow the README.

What it can do

Runs on your computer; the tool list appears in your AI app after you install it.

Basic checksi

We check information anyone can see; we have not read the code. Checks that do not apply are left out of the count. · Checked Nov 7, 2026

  • ✓ Pass

    Maker matches the repo

    The registry name was verified with the GitHub account biosshot, which owns the repo

  • … Not checked yet

    Still maintained

    We have not read this repo from GitHub yet

  • … Not checked yet

    Has a licence

    We have not read this repo from GitHub yet

  • – Not applicable

    Endpoint responds

    This one runs on your computer; there is no internet endpoint

  • – Not applicable

    Sign-in with OAuth

    Runs on your computer and uses local settings instead

  • … Not checked yet

    No hidden instructions in tool descriptions

    Runs on your computer; we can only read tool lists from internet endpoints

Compared with others in Otheri

  • More stars than 0% of the other 32678 servers in this category
  • Published to the registry more recently than 63% of the other 32678 servers in this category
  • Basic checks equal to or better than 100% of the other 32678 servers in this category

Compared with every active server in this category in the registry. Stars count only when the publisher owns the repo.

Common questions

Is EasyEDA Copilot safe?

It passed 1 of 1 applicable basic checks. We have not read the code. Before adding a key or token, see what access the server asks for and use a key with only the permissions you need.

What keys or codes does it need?

The registry does not list a required key, though some servers ask you to sign in on first use.

Does it run on my computer or in the cloud?

It runs on your computer. Your AI app starts it when needed, and data does not pass through the maker’s servers (unless it calls an online service itself).

Is it still maintained?

The GitHub repo last changed –, and the latest version (1.3.2) reached the registry 22 days ago.

Which apps can use it?

Apps that support MCP, such as Claude Desktop, Claude Code, Cursor and VS Code. You also need Node.js on your computer.

What can I use instead?

In the same category: Spec Driven Development, Remote Desktop Commander, Starreel

Alternatives

Servers in the same category from other makers, sorted by stars.

Reading a card:★ GitHub starsiThree pillars: reviews · checks · usageiUpdated = latest version published to the registryi

Spec Driven Development

by formulahendry

MCP Server that facilitates spec-driven development workflows, not just Vibe Coding.

Runs on your computer★ 440MITUpdated 14 months ago
Install

Remote Desktop Commander

by desktop-commander

Remote Desktop Commander: use files, terminal and processes on your own computers from any AI app.

Runs in the cloud★ 211Updated 2 days ago
Install

Starreel

by starreel

Turn a script into a finished, downloadable short-drama episode — via MCP or REST.

Runs on your computerUpdated today
Install

README from the maker

Open the README

Copied from the maker’s repo as written. PopNx MCP has not reviewed or endorsed it. HTML, images and scripts are removed. Links lead off this site.

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.

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.

Watch this video

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.

Watch the ESP32-C3 workflow (69 seconds)

Watch this video

Open video separately

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.

Watch the MIMXRT1011 workflow (128 seconds)

Watch this video

Open video separately

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.

Watch schematic beautification (13 seconds)

Watch this video

Open video separately

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.
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 ci

npm run build:skill cd skill/scripts/runtime npm 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

AreaCapabilities
SchematicsInspect the current page, create and complete circuits, reorganize existing schematics into functional blocks, and annotate designators across multiple pages
ComponentsResolve EasyEDA components by manufacturer MPN or part UUID
PCB placementGenerate board geometry and constraint-driven placement using functional blocks, modules, pin proximity, ordered signal paths, edge placement, keepouts, mounting holes, thermal pads, and preserved objects
PCB routingDefine net classes, signal and power nets, copper planes, differential pairs, matched groups, fanout, impedance intent, selective rerouting, and via stitching
InspectionRender layer-aware PCB previews, highlight nets and components, and inspect routed length, track widths, layers, vias, pads, polygons, nearby components, and unrouted connections
VerificationRead current DRC rules, run native EasyEDA DRC, inspect violations, and choose whether to keep, repair, or restore an applied result
Project controlInspect project trees, create and open projects or documents, synchronize editors, and select between multiple connected EasyEDA instances
Long operationsMonitor, continue, reapply prepared results, or cancel long PCB placement and routing operations

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.

WorkflowProtection and recovery behavior
Source-based schematic assemblySaves a full document checkpoint before modification and restores it automatically if assembly fails
Schematic beautificationSaves a checkpoint before page replacement and restores it automatically if replacement fails
Multi-page annotationSaves a checkpoint for every affected page and rolls modified pages back if the annotation transaction fails
PCB placementProduces mechanical and final previews, preserves existing board work, and saves a checkpoint before assembly
PCB routingApplies DRC rules, selected copper replacement, new tracks, vias, zones, synchronization, and native DRC inside one checkpoint-backed transaction
Routing application failureRestores the pre-routing checkpoint automatically
Manual recoveryLists, saves, and restores checkpoints explicitly for the current EasyEDA document

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

Only the beginning is shown; read the rest in the repo

Ask PopNx