opensta-mcp
Related Servers
Alternatives to opensta-mcp
No user-submitted related servers found.
Related Servers
- AlicenseNot gradedqualityBmaintenanceEnables 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 PyPIMIT
- -licenseNot gradedqualityNot gradedmaintenanceManages a persistent Fusion Compiler session via PTY, enabling Tcl command execution and common EDA queries through an MCP interface.-
- -licenseNot gradedqualityNot gradedmaintenanceEnables starting and managing named independent PTY sessions for Synopsys Fusion Compiler, sending arbitrary Tcl commands, and listing/interrupting sessions via MCP.-
- AlicenseAqualityBmaintenanceEnables 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.614 npmApache 2.0
- FlicenseNot gradedqualityCmaintenanceEnables 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.-
- AlicenseBqualityBmaintenanceMCP 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.20159 PyPI16Apache 2.0
TDQS
Scored across 9 tools
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.
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.
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.
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.