Skip to main content
Glama

Related Servers

Alternatives to opensta-mcp

No user-submitted related servers found.

    Related Servers

    • A
      license
      Not graded
      quality
      B
      maintenance
      Enables AI clients to directly launch, control, and analyze AMD/Xilinx Vivado on Windows and Linux, supporting project management, synthesis, implementation, bitstream generation, timing/resource analysis, and simulation through a persistent Tcl session.
      34 PyPI
      MIT
    • -
      license
      Not graded
      quality
      Not graded
      maintenance
      Manages a persistent Fusion Compiler session via PTY, enabling Tcl command execution and common EDA queries through an MCP interface.
      -
    • -
      license
      Not graded
      quality
      Not graded
      maintenance
      Enables starting and managing named independent PTY sessions for Synopsys Fusion Compiler, sending arbitrary Tcl commands, and listing/interrupting sessions via MCP.
      -
    • A
      license
      A
      quality
      B
      maintenance
      Enables AI coding agents and IDEs to execute ASIC physical design flows including floorplanning, placement, clock tree synthesis, routing, and static timing analysis through the OpenROAD engine, returning concise low-token JSON metrics.
      6
      14 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
      B
      quality
      B
      maintenance
      MCP server for elaborated SystemVerilog and gate-level netlists. Agents query design structure against a real elaboration - what drives this net, what a module instantiates, what registers are in a fanin cone - instead of reading RTL files. Answers come from najaeda's netlist engine, so they reflect post-elaboration connectivity across hierarchy, not text matches.
      20
      159 PyPI
      16
      Apache 2.0

    TDQS

    A4.2/5.0

    Scored across 9 tools

    Disambiguation4/5

    Most tools have clearly distinct purposes: load_design loads, report_timing/report_power produce specific reports, restart_session resets, etc. However, run_tcl is a general escape hatch that overlaps functionally with report_timing and report_power, and get_status vs get_conditions both report session state, creating some potential for misselection. Descriptions mitigate this well.

    Naming Consistency5/5

    All tool names follow a consistent snake_case verb_noun pattern (get_summary, load_design, report_timing, run_tcl, find_commands, get_status, get_conditions, restart_session). There are no deviations in casing or style.

    Tool Count5/5

    Nine tools is a well-scoped set for an STA server. Each tool covers a distinct operation (load, report, inspect, reset, discover) and there is no redundant tool that could be removed without losing functionality.

    Completeness5/5

    The surface covers the full lifecycle: loading a design, querying conditions/status, producing timing and power reports, discovering commands, running arbitrary Tcl, and restarting. Missing specialized reports (e.g., area, clocks) can be accessed via run_tcl, so there are no dead ends.

    Maintenance

    ActivityMaintained
    ResponsivenessNo issues