Skip to main content
Glama
lzw12123

MCP for Vivado

by lzw12123
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

Related Servers

Alternatives to MCP for Vivado

No user-submitted related servers found.

    Related Servers

    • vivado-mcp

      WangErShao
      A
      license
      Not graded
      quality
      C
      maintenance
      A lean MCP server that lets AI agents drive Xilinx Vivado for synthesis, implementation, simulation, and diagnostics through 30 curated tools and raw Tcl execution.
      Apache 2.0

    • Xilinx Vivado MCP

      zdx8637-gitdog
      F
      license
      Not graded
      quality
      B
      maintenance
      MCP server for AMD Xilinx Vivado 2023.1 that enables Claude Code to act as an AI FPGA engineer, providing 27 tools for querying, building, simulating, and programming FPGA designs.
      2
      -

    • Vivado MCP

      Shanqianlvshui
      F
      license
      B
      quality
      B
      maintenance
      A Model Context Protocol server that lets AI clients operate AMD Vivado through safe, workflow-level tools while allowing the user to watch and interact with the Vivado GUI.
      21
      -

    • 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.
      34 PyPI
      MIT

    • vivado-mcp-agent

      wangyuxin0707
      A
      license
      Not graded
      quality
      D
      maintenance
      MCP server for deterministic Vivado FPGA automation including project scaffolding, simulation, synthesis, implementation, and gated bitstream generation.
      4
      MIT
    Deploy Server
    One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

    TDQS

    C2.8/5.0

    Scored across 15 tools

    Disambiguation4/5

    Most tools have distinct purposes (e.g., workflow CRUD, toolchain management, design intents), but 'cancel_workflow' and 'reject_workflow' could be ambiguous—both involve stopping a workflow but with different semantics. Descriptions are brief but generally clear.

    Naming Consistency4/5

    Tool names follow a consistent verb_noun pattern (e.g., create_workflow, list_workflows). Minor inconsistency: 'design_block_design' is redundant (block design appears twice), and 'run_simulation' uses a different verb style than 'design_*' intents.

    Tool Count5/5

    15 tools is well-scoped for a Vivado MCP server covering workflow lifecycle, design intents, toolchain registration, and public methods. Each tool serves a clear purpose without unnecessary bloat.

    Completeness4/5

    Covers CRUD for workflows, toolchain registration, and design intents. Minor gaps: lacks update/delete for registered toolchains (only remove), and no tool for listing or managing IP/block designs after creation. Core workflows are complete.

    Maintenance

    ActivityInactive
    ResponsivenessNo issues

    Resources