easyeda-mcp
Provides tools for inspecting, reviewing, and automating parts of the PCB design workflow in EasyEDA Pro, including schematic and PCB inspection, component search, ERC/DRC checks, manufacturing export, and JLCPCB order preparation.
Click on "Deploy Server".
Wait a few minutes for the server to deploy. Once ready, it will show a "Started" state.
In the chat, type
@followed by the MCP server name and your instructions, e.g., "@easyeda-mcp run DRC on the current PCB design"
That's it! The server will respond to your query, and you can continue using it as needed.
Here is a step-by-step guide with screenshots.
easyeda-mcp
Open-source MCP tooling for AI-assisted work with EasyEDA Pro.
The goal is to let an AI coding agent inspect, review, and carefully automate parts of the PCB design workflow without turning the EDA editor into a blind screen-clicking exercise.
This project is maintained by Spectoda and is designed to be useful outside Spectoda as well.
What This Project Is
easyeda-mcp is intended to become a Model Context Protocol server plus an
EasyEDA Pro bridge extension. Together they should let an MCP-compatible agent:
inspect the currently open EasyEDA Pro project, schematic, PCB, and panel;
review schematics and PCB data against explicit engineering rules;
search and evaluate LCSC/JLCPCB component options;
run ERC/DRC-style checks exposed by EasyEDA Pro APIs;
export manufacturing packages such as Gerber, BOM, CPL, PDFs, and reports;
support panel preparation and validation;
prepare a JLCPCB order flow for human review.
The first production target is Spectoda controller development, but the public tooling should stay generic enough for other EasyEDA Pro users.
Related MCP server: KiCad MCP Server
What This Project Is Not
This repository must not contain:
EasyEDA, JLCPCB, LCSC, GitHub, or Spectoda credentials;
private EasyEDA account exports;
proprietary Spectoda controller source designs;
customer data, pricing secrets, or supply-chain agreements;
browser profiles, cookies, OAuth sessions, or local
.envfiles.
Private Spectoda EasyEDA account inventory and controller design mirrors will
live in Spectoda's internal workspace, primarily under the datasheets module.
This public repository only contains the generic tools and documentation needed
to build that workflow safely.
Current Status
Early implementation. The repository currently defines the project scope, architecture, operating rules, contribution model, and a minimal MCP server skeleton with a mocked Level 0 protocol smoke test.
Quick Start
npm install
npm run build
npm run smoke:protocolRun the MCP server over stdio:
npm run build
npm startPlanned Architecture
The intended runtime chain is:
MCP client / AI agent
|
| stdio or streamable HTTP
v
easyeda-mcp server
|
| localhost WebSocket bridge
v
EasyEDA Pro extension
|
| EasyEDA Pro Extension API
v
Open EasyEDA Pro editor sessionBrowser automation is reserved for flows that do not have a stable API, especially extension installation/debugging and JLCPCB quote/order preparation.
Initial Tooling Scope
The first useful slice should expose tools in these groups:
session.*- bridge status, connected editor windows, selected workspace.project.*- current project metadata and document tree.schematic.*- components, nets, pins, wires, selected primitives, review.library.*- LCSC/JLCPCB/EasyEDA device search and component metadata.pcb.*- board outline, components, nets, DRC, layers, export.panel.*- panel metadata, panelization parameters, validation.manufacturing.*- Gerber/BOM/CPL/PDF/3D export helpers.order.*- JLCPCB quote preparation and human-confirmed browser handoff.
Write operations must stay narrow, explicit, and reversible where possible.
The project should prefer typed domain tools over an unrestricted
execute_javascript interface.
Development Smoke Testing
Smoke testing will use two lanes:
Protocol lane - run the MCP server locally and call deterministic tools against mocked EasyEDA bridge responses.
Browser lane - use Codex Browser Use / browser automation to open the EasyEDA Pro editor, import the bridge extension, collect console logs, and verify that a real editor session connects.
See docs/browser-use-smoke-testing.md for the intended workflow.
Pull requests should include the smoke report block from docs/pull-request-smoke-checklist.md.
The first implemented smoke command is:
npm run smoke:protocolIt validates the Level 0 mocked bridge path and the initial session.status
tool registry.
Repository Map
ARCHITECTURE.md - system model and boundaries.
AGENTS.md - operating rules for AI agents working here.
TODO.tasks.json - active work and next steps.
CHANGELOG.md - notable project changes.
CONTRIBUTING.md - contribution rules.
SECURITY.md - vulnerability and secret-handling policy.
NOTICE.md - upstream inspiration and credits.
docs/ - focused design notes and workflow documentation.
License
Apache License 2.0. See LICENSE.
Available Tools
1 toolsession.statusA
Return the local EasyEDA MCP bridge status and connected editor windows.
Inputs: no named parameters.
Tool Schema Changelog
Recent tool additions, removals, and schema changes observed during successful MCP inspections.
Loading tool schema changelog…
TDQS
Scored across 1 tool
With only one tool, there is no possibility of confusing it with another. The name 'session.status' clearly indicates it provides status information about the EasyEDA bridge session.
The single tool name 'session.status' is clear and follows a namespace-like convention. While it doesn't follow the typical verb_noun pattern, consistency is trivially satisfied with only one tool, and there is no internal inconsistency.
The server name 'easyeda-mcp' suggests a broader purpose, but with only one status-checking tool, it is far too minimal for the apparent scope. One tool is insufficient to interact with EasyEDA in any meaningful way.
The server provides only a status endpoint with no tools to perform actual operations on EasyEDA projects, files, or editor windows. It is severely incomplete for its intended domain.
Maintenance
Related MCP Connectors
MCP server for building and testing AI agents with multi-model experimentation and insights.
MCP server that lets your AI assistant build and deploy apps, hosting each one at a live URL.
Hosted MCP server for AI photo editing: nothing to install, no desktop photo editor needed.
MCP server for Qwen Image 3 AI image generation
Related MCP Servers
- AlicenseCqualityBmaintenanceProduction-grade MCP server for EasyEDA Pro that enables AI-assisted hardware design review, PCB inspection, BOM sourcing, and manufacturing export through 41 profile-gated tools.843,681 npm73AGPL 3.0
- AlicenseBqualityBmaintenanceAn MCP server that enables AI assistants to analyze schematics, inspect PCBs, trace connections, validate designs, and generate embedded code for KiCad projects.39188MIT
- AlicenseNot gradedqualityBmaintenanceKiCad MCP Pro is an MCP server for KiCad EDA workflows. It lets AI agents automate schematic and PCB tasks, ERC/DRC validation, DFM review, and manufacturing export.12,892 PyPI229AGPL 3.0
- AlicenseCqualityDmaintenanceAn MCP server that enables AI programming assistants to directly control JLCPCB EDA for PCB design automation, offering 39 tools for component placement, routing, copper pour, DRC, and a PCB Agent for autonomous complex tasks.43MIT