jlceda-mcp-server
Related Servers
Alternatives to jlceda-mcp-server
No user-submitted related servers found.
Related Servers
- AlicenseCqualityCmaintenanceEnables AI coding assistants to control JLCPCB EDA for PCB automation, exposing 39 tools for component manipulation, routing, copper pour, DRC, and more. Includes a built-in PCB agent for orchestrating multi-step tasks.59223MIT
- AlicenseAqualityDmaintenanceMCP server for AI-assisted PCB design with EasyEDA Pro, enabling inspection, review, and automation of schematics, PCBs, and manufacturing export.14Apache 2.0
- 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.-
- AlicenseNot gradedqualityCmaintenanceAn MCP server that gives AI agents end-to-end control of KiCad 9+ for rule checks, manufacturing exports, production-readiness certification, and live PCB editor control.MIT
- AlicenseBqualityAmaintenanceAI-powered MCP server for KiCad that enables creating and modifying schematics, searching components, managing hierarchical projects, generating PCB placement, routing boards locally, and creating copper pours through natural language.2246 npm13MIT
- AlicenseBqualityBmaintenanceAn MCP server that enables AI assistants to analyze schematics, inspect PCBs, trace connections, validate designs, and generate embedded code for KiCad projects.39131MIT
TDQS
Scored across 43 tools
Most tools are separated by domain prefixes and resource types, but pcb_relocate_component, pcb_move_component, and pcb_batch_move are easily confused; read operations also mix get/list/query with overlapping scopes. Descriptions are often terse, so an agent may pick the wrong movement or query tool.
Tool names consistently use snake_case and domain prefixes (pcb_, sch_, calc_), with mostly verb_noun structure. Minor inconsistencies exist: delete_tracks is plural while delete_via is singular, and read operations alternate between get_, list_, and query_.
43 tools is a large surface for an agent to navigate; while EDA automation is broad, many operations overlap in purpose and the count exceeds what is needed for a coherent tool set. It feels more like a full API dump than a curated MCP surface.
The set covers the main PCB workflow: components, routing, vias, pours, keepouts, silkscreen, diff pairs, equal-length tuning, DRC, schematic entry, netlist export, and calculators. Gaps include no dedicated schematic object deletion (only clear-all) and no component editing beyond placement/movement, but these are workable.