EasyEDA MCP
Related Servers
Alternatives to EasyEDA MCP
No user-submitted related servers found.
Related Servers
- AlicenseNot gradedqualityAmaintenanceEnables MCP-capable AI agents to generate and reorganize schematics, resolve LCSC components, place and route PCBs with custom DRC constraints, inspect design data, and safely apply, repair, or restore changes in native EasyEDA Pro and JLCEDA documents.178MIT
- AlicenseNot gradedqualityCmaintenanceEnables an AI assistant to drive a live EasyEDA Pro editor for end-to-end PCB design: searching the LCSC library for parts, placing and wiring schematic symbols, transferring the design to the board, placing footprints, routing tracks and vias, drawing outlines and silkscreen, pouring copper, running DRC, and exporting BOM, pick-and-place, netlist, DXF and Gerber fabrication files.Apache 2.0
- FlicenseNot gradedqualityDmaintenanceEnables AI agents to interact with 嘉立创 EDA for PCB design tasks including project management, component libraries, rule checking, and manufacturing constraints.17 npm-
- FlicenseNot gradedqualityFmaintenanceEnables AI assistants to interact with JLCEDA EDA for schematic/PCB design operations like component placement, wiring, and circuit analysis through natural language.-
- AlicenseBqualityCmaintenanceEnables MCP clients to control EasyEDA Pro for schematic and PCB design through natural language, bridging the EasyEDA API without external AI or API keys.49MIT
- AlicenseBqualityBmaintenanceEnables AI assistants to interact with KiCAD for PCB design automation, including schematic editing, component placement, routing, DRC/ERC, and export.10012 npm1MIT
TDQS
Scored across 11 tools
Most tools target clearly distinct operations: list_components (read parts), read_netlist (file text), check_drc (validation), auto_layout/auto_route (PCB automation), export_manufacturing (output), and diagnostic tools (doctor, list_sessions, inspect_project). The main soft spot is easyeda_call_api, a generic write escape hatch that conceptually overlaps with auto_layout/auto_route/export since those could technically be invoked through it, though its description frames it as a distinct advanced path.
Every tool uses the same easyeda_ prefix followed by a consistent snake_case verb_noun pattern (list_components, inspect_project, check_drc, auto_route, export_manufacturing). No mixing of camelCase or alternative verb styles.
11 tools is well-scoped for an EDA bridge: read/introspect, validate, automate, export, plus a low-level API escape hatch. Each tool covers a concrete, non-redundant capability.
The surface covers the full lifecycle reasonably: project/session introspection, component and netlist reads, DRC validation, PCB auto-layout/auto-route, manufacturing export, and an arbitrary-write path via call_api. Explicit higher-level schematic edit or project save tools are absent, but call_api provides an escape hatch, so gaps are minor.