Skip to main content
Glama

Related Servers

Alternatives to Vivado MCP

No user-submitted related servers found.

    Related Servers

    • F
      license
      Not graded
      quality
      A
      maintenance
      Enables AI coding agents such as Claude Code, Cursor, and Codex to drive a locally installed Xilinx Vivado across the full FPGA flow, from GUI, headless Tcl, or attached sessions through synthesis, implementation, timing and CDC analysis, waveform queries, and device programming. It exposes 32 curated tools plus evidence-driven workflow prompts that return structured timing/IO reports, Chinese-language CRITICAL WARNING diagnostics, and guarded bitstream generation.
      -
    • F
      license
      Not graded
      quality
      A
      maintenance
      Enables AI coding agents to safely drive a locally installed Xilinx Vivado FPGA flow, covering session control, synthesis, implementation, timing and CDC analysis, XDC constraints, IP inspection, waveform queries, and device programming with structured, evidence-based diagnostics.
      -
    • 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 across the full FPGA flow, with tools for sessions, synthesis, implementation, timing, CDC, XDC, IP, waveform analysis, and device programming. It also provides evidence-driven workflow prompts, structured timing reports with baseline comparison, offline VCD queries, Chinese diagnostics for critical warnings, and environment self-check/repair.
      -
    • F
      license
      Not graded
      quality
      A
      maintenance
      Enables AI coding agents such as Claude Code, Cursor, and Codex to drive a locally installed Xilinx Vivado across the full FPGA flow, with tools for sessions, synthesis, implementation, timing, CDC, XDC, IP, waveform querying, and device programming. It also provides structured timing evidence with baseline comparison, offline VCD analysis, evidence-driven workflow prompts, and a read-only doctor for environment self-checks.
      -
    • F
      license
      Not graded
      quality
      A
      maintenance
      Enables AI coding agents such as Claude Code, Cursor, and Codex to drive a locally installed Xilinx Vivado through 32 curated tools covering sessions, synthesis, implementation, timing and CDC reports, XDC, IP, waveforms, and device programming. It also provides structured timing evidence with baseline comparison, offline VCD queries, environment self-diagnostics, and evidence-driven workflow prompts.
      -
    • A
      license
      Not graded
      quality
      C
      maintenance
      Enables AI assistants to drive Xilinx Vivado, Intel Quartus, and Anlogic TangDynasty for FPGA development, including project creation, synthesis, implementation, timing closure, and hardware programming through natural language.
      42 PyPI
      6
      MIT

    TDQS

    B3/5.0

    Scored across 40 tools

    Disambiguation4/5

    The tools are mostly cleanly separated by workflow stage: session management, project control, build steps, reporting, design queries, and simulation. A few boundaries are slightly fuzzy, such as get_signal_value versus get_signal_values, session_status versus check_session_health, and the report-generation/read-report pair, but descriptions make the intended use clear.

    Naming Consistency4/5

    Names are consistently snake_case and predominantly follow a verb_noun pattern, e.g. run_synthesis, get_timing_summary, launch_simulation, generate_bitstream. Minor deviations like session_status and the singular/plural get_signal_value(s) are readable but keep it from perfect consistency.

    Tool Count2/5

    Forty tools is heavy for a single MCP surface, even for a complex domain like Vivado. Several simulation and reporting helpers could likely be consolidated or made optional, and the large surface increases selection burden.

    Completeness4/5

    The surface covers the core FPGA flow from opening a project through synthesis, implementation, bitstream generation, reporting, and simulation, with run_tcl as an escape hatch. Notable gaps remain around project creation, file/constraint management, IP/block-design operations, and device programming, but most can be worked around via TCL.

    Maintenance

    ActivitySlowing
    ResponsivenessNo recent community issues