a2n-easyeda-mcp
Related Servers
Alternatives to a2n-easyeda-mcp
No user-submitted related servers found.
Related Servers
- AlicenseAqualityDmaintenanceConnects MCP clients to live EasyEDA Pro projects, enabling schematic and PCB inspection and editing through natural language.2140 npm17MIT
- FlicenseBqualityBmaintenanceConnects Jia Li Chuang EDA / EasyEDA Pro schematics to MCP clients, enabling AI-driven schematic editing, reading, and analysis.19-
- AlicenseNot gradedqualityBmaintenanceLocal Model Context Protocol server that exposes EasyEDA Pro design capabilities as MCP tools, enabling project inspection, schematic editing, PCB design, validation, and manufacturing exports through natural language.MIT
- AlicenseNot gradedqualityBmaintenanceEnables MCP clients like Claude Code to control a running EasyEDA Pro instance for PCB design automation, including DRC checks, project management, and script execution via a bridge server.7 npmMIT
- FlicenseNot gradedqualityBmaintenanceEnables AI agents to automate 嘉立创 EDA Professional through MCP, including schematic and PCB editing, component search and placement, net routing, DRC, and design capture.-
- AlicenseBqualityCmaintenanceEnables MCP clients to control JLCPCB EDA (嘉立创 EDA) for PCB and schematic design operations through a bridge and plugin architecture.38MIT
TDQS
Scored across 49 tools
Tools are clearly grouped by domain prefixes (eda, pcb, sch) and have distinct verb-noun patterns. Each tool targets a unique action and resource; no two tools appear to do the same thing, even for similar operations like reading circuit vs. validating netlist.
All tools follow a consistent 'domain_verb_noun' pattern in snake_case. Verbs like create, get, delete, export, save, run are used predictably across domains, making the set easy to navigate.
With 49 tools, the count is high but somewhat justified by the broad scope covering schematic, PCB, and general operations. However, it exceeds the 25-tool threshold considered heavy, which may overwhelm agents.
The tool set covers most core workflows for schematic and PCB design: CRUD, exports, DRC, netlist ops, and high-level assembly. Minor gaps exist (e.g., no separate delete for schematic wires, no sch_move_component) but can be worked around via low-level tools.