About this integration
MCP server for EasyEDA Pro: PCB inspection, BOM, exports, and hardware review.
- Transport
- stdio
- Authentication
- unknown
- Initial setup
- user-authorization
- Runtime
- unattended
- Evidence
- documented
- Version
- 1.0.1
- Package
- easyeda-mcp-pro
- Last compatibility test
- Not independently tested
Connect your agent
easyeda-mcp-proPublisher README and npm manifest were reviewed without installing or executing the package. The documented default MCP transport is stdio, but useful EasyEDA access additionally requires the bundled bridge extension, enabling external interaction, and a manual Connect action. Authentication varies by mode: the local bridge token defaults empty, supplier features may require vendor credentials, and remote non-loopback HTTP requires OAuth. The package and integration endpoints were not runtime tested or security-audited.
Capabilities: Inspect and edit EasyEDA Pro schematics through a local bridge, Review PCB layers, stackups, dimensions, and design-rule results, Generate BOM and fabrication export artifacts, Query optional supplier integrations when separately configured
Connected profiles
Additional details
io.github.oaslananka/easyeda-mcp-pro
Source ↗ · Checked 2026-09-171.0.1
Source ↗ · Checked 2026-09-17CC0-1.0; package licenses are separate
Source ↗ · Checked 2026-09-17npm
Source ↗ · Checked 2026-09-17easyeda-mcp-pro
Source ↗ · Checked 2026-09-191.1.0-rc.1
Source ↗ · Checked 2026-09-19Publisher documentation says supported MCP clients can be configured to run the server automatically; live EasyEDA workflows still require the separately installed bridge extension and its connection setup.
Source ↗ · Checked 2026-09-19Authentication is mode-dependent and does not fit one native method: the documented local bridge token defaults to an empty value, while optional suppliers use vendor credentials and remote HTTP uses OAuth.
Source ↗ · Checked 2026-09-19The existing catalog connection remains local stdio; the server then connects to EasyEDA Pro through its separately installed local WebSocket bridge extension.
Source ↗ · Checked 2026-09-19Publisher documentation reviewed; package and integration endpoint not executed or independently security-audited.
Source ↗ · Checked 2026-09-19