Skip to main content
Glama
sheares

easyeda-mcp-fix

by sheares
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

Related Servers

Alternatives to easyeda-mcp-fix

No user-submitted related servers found.

    Related Servers

    • easyeda-mcp-pro

      oaslananka
      A
      license
      B
      quality
      A
      maintenance
      Production-grade MCP server for EasyEDA Pro that enables AI-assisted hardware design review, PCB inspection, BOM sourcing, and manufacturing export through 41 profile-gated tools.
      73
      1,394 npm
      52
      PolyForm Noncommercial 1.0.0

    • easyeda-copilot-mcp

      biosshot
      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.
      169
      MIT

    • JLC_EDA-MCP

      mayjack0312
      A
      license
      C
      quality
      B
      maintenance
      Enables interaction with EasyEDA Pro by exposing 760 official API methods as MCP tools, along with plugin import and browser console debugging capabilities.
      500
      Apache 2.0

    • a2n-easyeda-mcp

      anwarminarso
      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
    Deploy Server
    Shareable, User-Owned Context BackendPeople, applications, and agents read, write, and coordinate together in one context lake. Reach it over MCP, a CLI, a Python SDK, or REST.fulcradynamics.comAd

    TDQS

    B3.4/5.0

    Scored across 103 tools

    Disambiguation3/5

    The PCB and schematic domains are cleanly separated and most tools have distinct purposes, but there is notable overlap in export tools (pcb_export vs pcb_export_to_file), file-transfer tools (document_set_source vs document_load_from_file vs project_import_file), and multiple primitive read tools (pcb_get_all_primitives vs pcb_get_primitives_by_id vs pcb_get_primitives_in_region vs pcb_get_primitive_at_point). The extremely long descriptions further obscure boundaries.

    Naming Consistency4/5

    There is a highly consistent domain_prefix_action_noun convention (pcb_create_track, sch_get_component, lib_symbol_copy, document_save_to_file), which makes tools very greppable. Minor deviations are the multi-action manager tools (pcb_manage_rule_config, pcb_manage_layers) that take an action parameter instead of exposing one tool per verb.

    Tool Count2/5

    103 tools is far too many for a single MCP server; it far exceeds what an agent can reliably reason about or choose among. The surface should be split into sub-servers (PCB, schematic, library, document/IO) or the 8+ pcb_manage_* action-based tools should be consolidated further.

    Completeness5/5

    Coverage is exceptionally thorough: CRUD for PCB and schematic primitives, full project/document file I/O, library symbol/footprint/device lifecycle, DRC, net-class/diff-pair management, and layout/export for nearly every fabrication format. No obvious gaps for the EDA-automation domain.

    Maintenance

    ActivityMaintained
    ResponsivenessNo issues

    Resources