Skip to main content
Glama
zesun33

@zesun33/mcp-openroad

by zesun33

Related Servers

Alternatives to @zesun33/mcp-openroad

No user-submitted related servers found.

    Related Servers

    • A
      license
      A
      quality
      B
      maintenance
      Enables AI coding agents and IDEs to synthesize Verilog/SystemVerilog designs with Yosys, inspect cell hierarchies and gate counts, and detect synthesis hazards like inferred latches and combinational loops before physical design flows.
      4
      15 npm
      Apache 2.0
    • A
      license
      A
      quality
      C
      maintenance
      Enables AI coding agents and IDEs to run a complete open-source FPGA flow, including synthesis, place-and-route, bitstream generation, and safe hardware programming for iCE40/ECP5 boards.
      6
      13 npm
      Apache 2.0
    • F
      license
      Not graded
      quality
      C
      maintenance
      Enables multi-agent orchestration of digital IC design flows (DFT, synthesis, APR, STA, PV, IREM, thermal, SIPI) through natural language by integrating heterogeneous EDA tools into a unified, secure, and observable API space with per-agent knowledge bases and decision traceability.
      -
    • A
      license
      A
      quality
      B
      maintenance
      Enables AI coding agents and IDEs to lint, compile, syntax-check, and simulate Verilog/SystemVerilog designs through structured, token-efficient MCP tools with isolated containerized toolchains.
      4
      17 npm
      Apache 2.0
    • A
      license
      A
      quality
      C
      maintenance
      Enables AI agents to run GDSII stream-out, KLayout DRC, Netgen LVS, and Magic extraction via MCP.
      6
      14 npm
      Apache 2.0

    TDQS

    A4/5.0

    Scored across 6 tools

    Disambiguation5/5

    Each tool targets a distinct, non-overlapping stage of the ASIC physical design flow: floorplan, place, route, static timing analysis, or the full end-to-end PNR run. The info tool is clearly separated as a utility for runtime details. No ambiguity in purpose.

    Naming Consistency5/5

    All tools follow a consistent 'openroad_' prefix with a lowercase action or stage identifier (pnr, floorplan, place, route, sta, toolchain_info). This creates a predictable and readable pattern that makes tool selection straightforward.

    Tool Count5/5

    Six tools is well-scoped for a physical-design-oriented MCP server covering the main flow stages plus an end-to-end wrapper and an info utility. Each tool earns its place, supporting both granular control and a one-shot option.

    Completeness4/5

    The set covers the primary stages (floorplan, place, route, STA) and an end-to-end PNR path, which likely includes clock tree synthesis internally. A minor gap is the lack of a dedicated clock tree synthesis tool for users who need to run CTS in isolation, but the core lifecycle is otherwise complete.

    Maintenance

    ActivityMaintained
    ResponsivenessNo issues