Skip to main content
Glama
EasyEDA Pro MCP

EasyEDA Pro MCP

Related Servers

Alternatives to EasyEDA Pro MCP

No user-submitted related servers found.

    Related Servers

    • F
      license
      B
      quality
      C
      maintenance
      Connects Jia Li Chuang EDA / EasyEDA Pro schematics to MCP clients, enabling AI-driven schematic editing, reading, and analysis.
      19
      -
    • A
      license
      B
      quality
      C
      maintenance
      Enables MCP clients to control EasyEDA Pro for schematic and PCB design through natural language, bridging the EasyEDA API without external AI or API keys.
      49
      MIT
    • A
      license
      Not graded
      quality
      D
      maintenance
      Local 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
    • A
      license
      Not graded
      quality
      A
      maintenance
      Enables 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.
      216
      MIT
    • A
      license
      Not graded
      quality
      D
      maintenance
      Enables 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.
      47 npm
      MIT

    TDQS

    C2.9/5.0

    Scored across 76 tools

    Disambiguation3/5

    Most tools have descriptive names and clear domain/action boundaries, but the 76-tool surface creates real overlap among status/context tools (doctor/live_status/get_context), schematic net queries (find_net/get_schematic_nets/trace_net/schematic_snapshot), and PCB analysis tools (routing_status/get_pcb_net_report/get_pcb_airwires). An agent can usually distinguish them, but several read-only diagnostics require careful selection.

    Naming Consistency4/5

    Nearly all tools use the easyeda_ prefix and snake_case with clear verb-first patterns such as get_*, list_*, prepare_*, export_*, and run_*. A few exceptions (easyeda_doctor, easyeda_live_status, easyeda_schematic_snapshot, easyeda_confirmed_action) break the verb_noun pattern but remain readable.

    Tool Count1/5

    76 tools is far beyond a well-scoped MCP surface and includes many granular read-only, export, and prepare tools. Even for a broad EDA domain, this count creates a large selection burden and should be consolidated or grouped.

    Completeness4/5

    The surface covers schematic capture, PCB layout, DRC/ERC, library lookup, BOM/CPL/Gerber/netlist/3D exports, SPICE netlist generation, and mutation confirmation workflows. Remaining gaps are minor, such as no direct SPICE simulation execution and no obvious project save/versioning, but the core EDA lifecycle is well covered.

    Maintenance

    ActivityMaintained
    ResponsivenessLimited data