MCP for Vivado
Related Servers
Alternatives to MCP for Vivado
No user-submitted related servers found.
Related Servers
- AlicenseNot gradedqualityDmaintenanceA 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
- AlicenseBqualityDmaintenanceA Model Context Protocol (MCP) server that enables AI assistants like Claude to directly interact with AMD/Xilinx Vivado FPGA development tools.4069MIT
- FlicenseNot gradedqualityBmaintenanceMCP 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-
- FlicenseBqualityDmaintenanceA 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.211-
- FlicenseNot gradedqualityAmaintenanceEnables Claude Code, Cursor, Codex, and other AI agents to safely drive a locally installed Xilinx Vivado through MCP, covering synthesis, implementation, timing/CDC/XDC/IP/waveform analysis, bitstream programming, and evidence-driven workflow prompts.-
- FlicenseNot gradedqualityAmaintenanceEnables AI coding agents such as Claude Code, Cursor, and Codex to safely drive a locally installed Xilinx Vivado through 32 MCP tools spanning sessions, synthesis, implementation, timing and CDC analysis, XDC checks, IP inspection, offline waveform queries, and device programming, backed by evidence-driven workflow prompts and structured Chinese diagnostics.-
TDQS
Scored across 15 tools
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.
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.
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.
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.