Skip to main content
Glama
gfgf2023

EasyEDA MCP

by gfgf2023
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

Related Servers

Alternatives to EasyEDA MCP

No user-submitted related servers found.

    Related Servers

    • jlceda-mcp

      qcz2943
      F
      license
      Not graded
      quality
      D
      maintenance
      Enables AI agents to interact with 嘉立创 EDA for PCB design tasks including project management, component libraries, rule checking, and manufacturing constraints.
      18 npm
      -

    • 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.
      164
      MIT

    • jlceda-mcp-server

      hyl64
      A
      license
      C
      quality
      C
      maintenance
      Enables 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.
      59
      237
      MIT

    • jlceda-ai-agent

      jiangyiqi99
      F
      license
      Not graded
      quality
      B
      maintenance
      Enables AI agents to automate 嘉立创 EDA Professional through MCP, including schematic and PCB editing, component search and placement, net routing, DRC, and design capture.
      -

    • fusion-electronics-mcp

      groundplane-studio
      A
      license
      B
      quality
      A
      maintenance
      Lets AI agents read, review, and edit PCB designs in Autodesk Fusion Electronics, covering schematic capture, placement, impedance-controlled routing, pours and stitching, design checks, and JLCPCB manufacturing outputs. Every change is verified by reading the design back from Fusion and rolled back if it does not match, with each tool call acting as a single undo step until the user saves.
      77
      MIT
    Deploy Server
    One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

    TDQS

    B3.4/5.0

    Scored across 14 tools

    Disambiguation4/5

    Most tools target clearly distinct actions: session/workflow, state reads, routing, DRC, screenshots, library search, and tool discovery. A couple of pairs could be confused, notably pcb_get_state vs pcb_get_routing_context and pcb_apply_route's DRC step vs eda_run_drc, but the descriptions are specific enough to separate them.

    Naming Consistency3/5

    Names are consistently snake_case and mostly readable, but they mix verb_noun forms (eda_open_document, pcb_check_route, eda_find_tools) with noun-only forms (eda_session, eda_workflow, eda_screenshot, eda_tool_schema). The domain prefixes are also inconsistent across eda_, sch_, pcb_, and lib_, creating a mixed convention.

    Tool Count4/5

    14 tools is within the typical well-scoped range and covers session management, schematic/PCB reads, routing, DRC, visualization, library search, and dynamic tool discovery. The meta-tool triad of eda_find_tools, eda_tool_schema, and eda_invoke adds some apparent overlap with direct calls, but each still has a distinct role.

    Completeness3/5

    The set covers reading design state, routing, DRC, and image feedback well, but it lacks obvious design-editing operations such as component placement, schematic/PCB edits, and route removal or rework. The workflow and screenshot tools help guide an agent, but full edit cycles are not supported by the static tool surface.

    Maintenance

    ActivityMaintained
    ResponsivenessNo issues

    Resources