Skip to main content
Glama
Sign In
eda-agent

eda-agent

by Nivakaran-S
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

Related Servers

Alternatives to eda-agent

No user-submitted related servers found.

    Related Servers

    • EasyEDA Pro MCP Server

      teileelektronik
      F
      license
      Not graded
      quality
      Not graded
      maintenance
      Enables AI-powered autonomous hardware design within EasyEDA Pro, allowing users to create schematics, PCB layouts, and manufacturing files using natural language. It integrates direct EDA tool control with an engineering knowledge base and real-time component searching via JLCPCB and LCSC.
      -

    • 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

    • 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
      265
      MIT

    • CircuitPilot

      Abdelhayali
      F
      license
      Not graded
      quality
      A
      maintenance
      AI copilot for PCB design: search real JLCPCB/LCSC parts, build schematics, run ERC, auto-place and autoroute 2-layer boards with DRC, export Gerbers/BOM/pick-and-place, and generate 3D-printable enclosures. Changes appear live in the CircuitPilot browser editor.
      4
      -

    • KiCAD MCP Server

      Avinash1286
      A
      license
      B
      quality
      B
      maintenance
      Enables AI assistants to interact with KiCAD for PCB design automation, including schematic editing, component placement, routing, DRC/ERC, and export.
      100
      29 npm
      2
      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.3/5.0

    Scored across 480 tools

    Disambiguation2/5

    The 480-tool set contains many near-overlapping tools: app_run_menu vs app_click_menu vs app_run_ui_command; app_list_open_dialogs vs app_read_window vs app_ui_snapshot; proj_get_nets vs proj_get_connectivity vs proj_get_component_info; and many audit_find_* and pcb_get_* variants. Descriptions often explain distinctions, but the sheer breadth makes misselection likely for an agent.

    Naming Consistency2/5

    There are recognizable prefix families (app_, proj_, lib_, pcb_, sch_, design_, audit_, sim_), but many tools use bare names (list_components, run_drc, run_erc, get_board_info, review_design, route_plan, tool_invoke). Snake_case is mostly preserved, but verb styles and prefixing conventions vary widely across the surface.

    Tool Count1/5

    480 tools is far beyond a well-scoped set; even a large EDA automation suite does not justify this count for an agent-facing MCP server. tool_catalog and tool_invoke mitigate discovery, but the raw surface remains extreme and impractical to load or reason about reliably.

    Completeness5/5

    The surface covers project and document lifecycle, schematic and PCB CRUD, library authoring, simulation, routing, auditing, BOM/export, UI driving, and meta-tooling. Despite redundancy, there is no obvious core gap for the stated Altium/EDA automation domain.

    Maintenance

    ActivityMaintained
    ResponsivenessNo issues

    Resources