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.
      74
      2,650 npm
      64
      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.
      200
      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

    A3.6/5.0

    Scored across 104 tools

    Disambiguation4/5

    Most tools target distinct resource+action pairs and the descriptions carefully carve out boundaries (e.g. pcb_export vs pcb_export_to_file, pcb_create_track vs pcb_create_polyline_track). A few overlaps remain, notably sch_get_selected vs sch_get_selected_ids, and the cluster of read tools (pcb_get_all_primitives, pcb_get_primitives_by_id, pcb_get_primitives_in_region, pcb_get_net_primitives, pcb_get_primitive_at_point) that require the agent to reason about which query shape fits. These are resolvable from descriptions but not trivially distinct.

    Naming Consistency4/5

    A predictable prefix + verb_noun convention dominates: pcb_*, sch_*, lib_*, document_*, project_*, editor_*, with action-style managers like pcb_manage_*. A handful of outliers (server_info, list_instances, bridge_restart, pcb_canvas_origin) deviate from the prefix_action pattern, but the overall convention is readable and stable.

    Tool Count2/5

    104 tools is far beyond a comfortable agent-selectable surface, even accounting for the genuinely large EDA domain (PCB fabrication, schematic capture, library management, projects, DRC/rules). While several tools already bundle actions (pcb_manage_*), the sheer volume forces the agent to wade through a very long list to find the right call, increasing misselection risk.

    Completeness5/5

    The surface covers the full lifecycle: read/create/modify/delete for PCB primitives, schematic components/wires/nets, library symbols/footprints/devices, plus DRC, design rules, net classes, diff pairs, equal-length groups, import/export across many formats, project structure, and git-backed backup/restore. No obvious dead ends for the stated EDA-automation purpose.

    Maintenance

    ActivityMaintained
    ResponsivenessNo issues

    Resources