Skip to main content
Glama
InsungHeo

opensta-mcp

by InsungHeo
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

Related Servers

Alternatives to opensta-mcp

No user-submitted related servers found.

    Related Servers

    • Vivado MCP Native

      Arthurzxy
      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.
      48 PyPI
      MIT

    • Fusion Compiler Session MCP

      camucamulemon7
      -
      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.
      -

    • vivado-mcp

      HenkAli44
      F
      license
      Not graded
      quality
      A
      maintenance
      Enables AI agents such as Claude Code, Cursor, and Codex to safely drive a locally installed Xilinx Vivado through 32 curated tools covering sessions, synthesis, implementation, timing, CDC, XDC, IP, waveforms, and device programming. Provides structured timing evidence with baseline comparison, offline VCD queries, Chinese diagnostics for critical warnings, and GUI/Tcl/attach session modes.
      -

    • Fusion Compiler Session MCP

      camucamulemon7
      -
      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.
      -

    • vivado-mcp

      josegomez399
      F
      license
      Not graded
      quality
      A
      maintenance
      Enables AI agents such as Claude Code, Cursor, and Codex to safely drive a locally installed Xilinx Vivado through 32 curated tools spanning GUI, Tcl, and attach sessions, synthesis, implementation, timing, CDC, XDC, IP, waveforms, and device programming. It provides structured timing evidence with baseline comparison, offline VCD queries for unknown values and handshake events, environment self-checks, and Chinese-language diagnosis of timing issues and CRITICAL WARNINGs.
      -

    • vivado-mcp

      chavez58534
      F
      license
      Not graded
      quality
      A
      maintenance
      Enables AI agents such as Claude Code, Cursor, and Codex to safely drive a locally installed Xilinx Vivado through 32 tools covering sessions, synthesis, implementation, timing, CDC, XDC, IP, waveforms, and device programming. Includes structured timing evidence with baseline comparison, offline VCD queries, evidence-driven workflow prompts, and one-command environment self-checks.
      -
    Deploy Server
    Shareable, User-Owned Context BackendPeople, applications, and agents read, write, and coordinate together in one context lake. Reach it over MCP, a CLI, a Python SDK, or REST.fulcradynamics.comAd

    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

    Resources