Skip to main content
Glama
sinemortal

vivado-red-mcp

by sinemortal
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

Related Servers

Alternatives to vivado-red-mcp

No user-submitted related servers found.

    Related Servers

    • vivado-mcp

      hiroshi85108
      F
      license
      Not graded
      quality
      A
      maintenance
      Lets AI agents such as Claude Code, Cursor and Codex drive a locally installed Xilinx Vivado across the whole FPGA flow — GUI, headless Tcl and attach sessions, synthesis and implementation with progress polling, bitstream safety checks, and device programming. Adds structured timing and IO reports with baseline comparison, offline VCD waveform and CDC report analysis, and Chinese diagnostics for CRITICAL WARNINGs, all through 32 curated tools and evidence-gated workflow prompts.
      -

    • vivado-mcp

      catherinekato75
      F
      license
      Not graded
      quality
      B
      maintenance
      Enables AI coding 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 and CDC analysis, XDC/IP debugging, offline VCD waveform queries, and device programming. It provides structured timing evidence with baseline comparison, evidence-driven workflow prompts, environment self-checks via doctor, and Chinese-language diagnostics for CRITICAL WARNINGs and timing issues.
      -

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

    • vivado-mcp

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

    • vivado-mcp

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

    • Vivado MCP Server

      jLambert11
      F
      license
      Not graded
      quality
      A
      maintenance
      Enables AI agents to drive a locally installed Xilinx Vivado through 32 curated tools covering sessions, synthesis, implementation, timing and CDC analysis, XDC constraints, IP inspection, waveform queries, and device programming, with structured evidence, environment self-checks, and evidence-gated workflow prompts. Supports GUI, headless Tcl, and attach session modes.
      -
    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

    B3/5.0

    Scored across 93 tools

    Disambiguation3/5

    Most tools target distinct Vivado operations, but the set mixes low-level primitives with composite one-shots (e.g., create_redpitaya_project_rtl vs rp_build_project vs create_project/run_synthesis, and generate_ip_target vs synth_ip). Several getters/report wrappers also require reading descriptions to choose correctly. Descriptions help, but with 93 tools misselection risk remains.

    Naming Consistency4/5

    Nearly all names are snake_case verb_noun, with domain prefixes such as rp_, report_, and get_ used consistently. Minor exceptions like session_status and rp_workspace_info are noun-first but still readable and predictable.

    Tool Count1/5

    93 tools far exceeds a reasonable single-server surface; even for a complex FPGA flow this creates high selection and cognitive load. It should be split into session/project/simulation/block-design/hardware/Red-Pitaya sub-servers. This falls in the extreme 50+ tool mismatch range.

    Completeness4/5

    The surface covers end-to-end Vivado flow plus Red Pitaya deployment, documentation, and a run_tcl escape hatch. Some granular removal/delete/debug operations are missing (e.g., remove sources/constraints, delete BD cells/nets, ILA or memory reports), but these are largely workaroundable via raw TCL.

    Maintenance

    ActivityMaintained
    ResponsivenessNo issues

    Resources