vivado-red-mcp
Provides tools for driving AMD/Xilinx Vivado directly, enabling project creation, block design and IP Integrator work, synthesis, implementation, simulation, timing and utilization report parsing, and bitstream generation, including Red Pitaya board flows.
Click on "Deploy Server".
Wait a few minutes for the server to deploy. Once ready, it will show a "Started" state.
In the chat, type
@followed by the MCP server name and your instructions, e.g., "@vivado-red-mcp build the Red Pitaya LED blink RTL project and generate its bitstream"
That's it! The server will respond to your query, and you can continue using it as needed.
Here is a step-by-step guide with screenshots.
vivado-red-mcp — Vivado MCP server, Red Pitaya edition
An MCP server that lets an AI assistant such as Claude drive AMD/Xilinx Vivado directly: create projects, build block designs, synthesize, implement, simulate, read timing/utilization reports and generate bitstreams — without opening the Vivado GUI.
It has first-class support for the Red Pitaya STEMlab 125-14 (Zynq
xc7z010clg400-1): you can go from a natural-language description to a
.bit.bin running on the board, using either pure RTL or the official
RedPitaya-FPGA PS+PL (ARM + FPGA) backbone, and deploy it over SSH.
Forked from coreyhahn/vivado_mcp and heavily extended (93 tools): block design / IP Integrator, IP catalog, Hardware Manager, advanced reports, Red Pitaya RTL and PS+PL flows, SSH deploy.
Current version: 0.5.0 — see What's new and CHANGELOG.md.
Not to be confused with the unrelated
vivado-mcppackage on PyPI. This project isvivado-red-mcp: Python modulevivado_red_mcp, commandvivado-red-mcp.
Contents
Related MCP server: vivado-mcp
What it can do
Persistent Vivado session — one Vivado process in Tcl mode is kept alive, so commands don't pay the 20–30 s startup each time.
Projects and design flow — create/open projects, add HDL and XDC files, synthesis, implementation, bitstream, run strategies.
Block design (IP Integrator) — ports, IP cores, RTL module cells, nets, PS7 presets, validation, wrapper generation.
Reports — timing (WNS/TNS/WHS/THS), utilization, clocks, power, DRC, methodology, QoR; returned as parsed values, not just raw text.
Simulation (xsim) — behavioral and post-synthesis/implementation, read signal values, breakpoints.
Red Pitaya — one-shot RTL build, full PS+PL build from the official RedPitaya-FPGA repo, bundled board constraints,
.bit.bingeneration, SSH deploy.Raw Tcl — anything not covered by a tool can be run as Tcl (multi-line scripts supported).
Tested with
Status | |
Vivado 2026.1, Windows 11 | Validated end-to-end in 0.4.0: session, RTL and PS+PL Red Pitaya builds, reports, behavioral + post-synthesis xsim, block design, RedPitaya-FPGA tutorials (see below) |
Vivado 2020.1, Linux | Original development target (0.3.x). Not re-tested on 0.4.0 |
Other Vivado releases | Expected to work (the generic tools use standard Tcl); not tested |
Red Pitaya board | STEMlab 125-14 (Z10) only for the Red Pitaya flows |
Python | 3.10 – 3.12 |
MCP Python SDK | 1.x only ( |
The RedPitaya-FPGA tutorials in prj/Examples (Led_blink, Knight_rider, Stopwatch,
Frequency_counter) build to a bitstream through the server. Led_blink and
Knight_rider rebuilt from scratch with MCP tools only produce byte-identical
bitstreams to the tutorials' own scripts.
Requirements
Python 3.10+
AMD Vivado (the free edition is enough for the Red Pitaya
xc7z010). When installing, you only need Vivado and, under devices, SoCs → Zynq-7000; Vitis Model Composer and DocNav are not needed.A Vivado license file — also for the free edition on 2025.x/2026.x. Without it Vivado refuses to start (
a valid license was not found):open the Vivado License Manager (
<Vivado>/bin/vlm.baton Windows,vlmon Linux);Obtain License → on the AMD site tick Vivado Basic Tier License, Node Locked License (no charge, no expiry) → Generate Node-Locked License;
host ID: the MAC address of your network card (shown under View Host Information). The license is tied to the PC, not to the network you use;
load the received
Xilinx.licwith Load License → Copy License.
Vivado reachable by the server, either:
on
PATH(Linux:source <Vivado>/settings64.sh; Windows: add<Vivado>\bintoPATH), orby telling Claude the full path, which it passes to
start_session(e.g.C:\AMDDesignTools\2026.1\Vivado\bin\vivado.bat).
pexpect (Linux/macOS) or pywinpty (Windows) is installed automatically.
Installation
1. Get the code and install it
git clone https://github.com/sinemortal/vivado-red-mcp.git
cd vivado-red-mcp
python -m venv .venv
# Windows: .venv\Scripts\activate
# Linux/macOS: source .venv/bin/activate
pip install -e .pip pins the MCP SDK to 1.x by itself. Do not upgrade mcp to 2.x: the server
would not start ('Server' object has no attribute 'list_tools').
2. Register it with Claude Code
Once, for all your projects:
claude mcp add --transport stdio --scope user vivado -- vivado-red-mcpIf vivado-red-mcp is not on PATH when Claude Code starts (typical with a virtual
environment), point to the venv's Python instead:
# Windows
claude mcp add --transport stdio --scope user vivado -- "C:\path\to\vivado-red-mcp\.venv\Scripts\python.exe" -m vivado_red_mcp
# Linux/macOS
claude mcp add --transport stdio --scope user vivado -- /path/to/vivado-red-mcp/.venv/bin/python -m vivado_red_mcpOr share it with a single project through a .mcp.json at the project root:
{
"mcpServers": {
"vivado": {
"type": "stdio",
"command": "vivado-red-mcp"
}
}
}Check it with claude mcp list: vivado should show as connected.
3. Optional: disable the RedPitaya-FPGA auto-download
On startup the server downloads the RedPitaya-FPGA repo (source zip) into its
working directory if it is missing, for the PS+PL flow. Set the
environment variable VIVADO_MCP_NO_AUTOFETCH=1 to turn this off; the
rp_fetch_repo tool can still download it on demand.
First steps
Talk to Claude in plain language, for example:
"Start a Vivado session" (add the path if Vivado is not on
PATH)"Open my project at
C:/work/my_proj/my_proj.xpr""Synthesize and implement it, then tell me if timing is met"
"Show me the resource utilization"
"Generate the bitstream"
"Stop the Vivado session"
Claude picks the tools; you never have to call them by name.
Red Pitaya
Two flows, depending on whether you need the ARM processor:
Flow | Tool | Use it for |
RTL only (no PS7) |
| Logic clocked by the 125 MHz ADC clock: LEDs, counters, expansion-connector GPIO. One call does create → sources → XDC → synth → impl → bitstream → |
PS + PL |
| Designs that need the ARM, DDR or AXI. Reuses the PS7 block design shipped by RedPitaya-FPGA instead of reconfiguring the Zynq by hand |
Example prompt:
Make an LED blinker at 1 Hz for the Red Pitaya using the 125 MHz ADC clock on
led_o[0], build it and give me the.bit.bin.
To load the result on the board, ask Claude to use deploy_to_redpitaya (SSH,
default credentials root/root; works with OS 1.04 xdevcfg and OS 2.00
fpgautil), or copy it yourself:
scp led_blinker.bit.bin root@rp-xxxxxx.local:/tmp/
ssh root@rp-xxxxxx.local 'cat /tmp/led_blinker.bit.bin > /dev/xdevcfg'PS+PL and the RedPitaya-FPGA repo. The current upstream master targets
Vivado 2025.1; older checkouts targeted 2020.1. Both layouts are supported.
rp_setup_workspace copies the repo into a separate workspace and patches only
that copy, so the scripts run on the Vivado you have installed (their exported
block-design/IP scripts otherwise refuse any other release) and without a git
checkout. Your downloaded repo is never modified. Details:
get_vivado_doc redpitaya_ps_pl_flow.
Bundled board data (data/boards/):
red_pitaya_125_14_full.xdc— full pinout (ADC, DAC, LEDs, expansion connector, XADC), port names as in the officialred_pitaya_top(adc_dat_i[ch][bit],dac_dat_o,exp_p_io, …); checked pin by pin against upstreamsdc/red_pitaya.xdc.red_pitaya_125_14_leds_min.xdc— 125 MHz differential ADC clock + 8 LEDs, for hello-world designs.red_pitaya_125_14_info.json— part number and board metadata.
The RedPitaya tutorials (prj/Examples) use different port names
(adc_dat_a_i, adc_clk_p_i, …) and a PS7 preset (cfg/red_pitaya.xml); use
their own cfg/ files when rebuilding them.
More Italian prompt examples and the step-by-step low-level flow: USAGE.md.
What's new in 0.5.0
Renamed to vivado-red-mcp (package, Python module vivado_red_mcp, command
vivado-red-mcp), so it no longer clashes with the unrelated vivado-mcp package on
PyPI. If you installed an earlier version, reinstall it and re-register it with
Claude Code using the new command (see Installation).
0.4.0
Works on Vivado 2026.1 and with the current RedPitaya-FPGA repo.
Fixed:
Server failed to start with MCP SDK 2.x → SDK pinned to 1.x.
Simulation never worked when the server was started by Claude Code on Windows (xsim:
Spawn failed) → fixed.Multi-line Tcl sent through
run_tclwas silently corrupted on Windows → fixed.get_timing_summaryalways returned empty values;get_utilizationmisread newer reports → both parse current Vivado output.Reports right after a build failed with no message (
No open design) → the latest completed run is opened automatically.get_synthesis_errors_parsedalways returned 0 errors → now reads the run logs, including failed IP runs.launch_simulationmodes rejected by recent Vivado → fixed.generate_bitstreamtimed out after 300 s and didn't check the result → now verified, returns the.bitpath.Missing license (or any startup failure) now reports Vivado's own message in seconds instead of a generic error after 2 minutes.
Bundled
red_pitaya_125_14_full.xdchad 6 wrong pins (ADC channel A MSB anddac_dat_o[8..12]) → corrected.PS+PL flow broken by the new RedPitaya-FPGA layout → both layouts supported.
New tools: create_bd_port, add_module_to_bd, configure_bd_cell,
set_run_strategy. Full list in CHANGELOG.md.
Troubleshooting
Symptom | Cause / fix |
| Vivado 2025.x/2026.x needs a license file even for the free edition — see Requirements |
| Put |
Server does not start: | MCP SDK 2.x installed. Run |
|
|
A RedPitaya example fails synthesis with | Upstream issue in |
Occasional | Intermittent Vivado issue with parallel out-of-context runs; re-run synthesis |
Long paths on Windows | Keep projects in short paths; Vivado and IP generation hit the 260-character limit |
Available tools
Session management
start_session- Start a persistent Vivado Tcl session (optionalvivado_path)stop_session- Stop the Vivado sessionsession_status- Session statisticscheck_session_health- Detect a hung/dead session, optionally recoverget_host_status- Host CPU/memory status
Project management
create_project- Create a project on disk (default partxc7z010clg400-1)open_project/close_project- Open or close an.xprget_project_info- Part, directory, top, …add_sources/add_constraints- Attach HDL and XDC files
Design flow
run_synthesis- Run synthesis (verified run status)run_implementation- Run place and route (verified run status)generate_bitstream- Generate the bitstream (verified status +.bitpath)set_run_strategy- Set the synthesis/implementation run strategy
Reports & analysis
Report tools open the latest completed run automatically if no design is open.
get_timing_summary- WNS, TNS, WHS, THS, pulse width, met / not metget_timing_paths- Detailed timing paths for failing/critical pathsget_utilization- LUTs, FFs, BRAMs, DSPs, IOsget_clocks- Clock informationget_messages- Synthesis/implementation messages
Design queries
get_design_hierarchy- Module/instance hierarchyget_ports- Top-level portsget_nets/get_cells- Search nets and cells
Simulation (xsim)
set_simulation_top- Set the testbench modulelaunch_simulation- Behavioral, post-synthesis or post-implementation (functional/timing)run_simulation/step_simulation/restart_simulation/close_simulationget_simulation_timeget_signal_value/get_signal_values- Read signalsget_simulation_objects/get_scopes- Browse the hierarchyadd_signals_to_waveadd_breakpoint/remove_breakpointsget_simulation_messages
Block design (IP Integrator) — Zynq / AXI
create_block_design- Create a block design and make it currentcreate_bd_port- Scalar, vector or interface portsadd_ip_to_bd- Add an IP core (VLNV) withCONFIG.*propertiesadd_module_to_bd- Add an RTL module as a module-reference cellconfigure_bd_cell- SetCONFIG.*on an existing cell (e.g. PS7 board preset import)connect_bd_net/connect_bd_intf_net- Wire pins/ports and AXI interfacesauto_connect_axi-apply_bd_automationfor AXI master ↔ slaveapply_ps7_preset- Zynq PS7 automation (FIXED_IO/DDR external)validate_block_design- Run BD DRCassign_bd_address- Auto-assign AXI address rangesregenerate_bd_layout- Tidy the layoutsave_bd_design/close_bd_design- Persist or close the BDlist_bd_cells- List cellsgenerate_bd_wrapper-make_wrapper+ add to fileset + set as top
IP catalog
create_ip/configure_ip- Create and configure catalog IPsgenerate_ip_target/synth_ip- Output products, out-of-context synthesisupgrade_ip/report_ip_status- Upgrade and audit IP versions
Hardware Manager (JTAG)
open_hw_manager/close_hw_managerconnect_hw_server- Connect tohw_server(defaultlocalhost:3121)program_device- Program a.bitover JTAGrefresh_hw_device- Re-read the JTAG chain
Advanced reports
report_power- Total/dynamic/static powerreport_drc- DRC violations grouped by severityreport_methodology- UltraFast methodology checksreport_qor_assessment- QoR scorereport_clock_interaction- Cross-clock pathsgenerate_full_report/read_report_section- Full reports to file, read them in pieces
Red Pitaya — RTL flow
list_boards/get_board_info- Bundled board metadata and XDC paths (no Vivado needed)load_board_xdc- Add a bundled board XDC to the projectcreate_redpitaya_project_rtl- One-shot RTL build; returnsbit_path,bin_path, parsedtiming_summaryandutilizationgenerate_cfgmem-.bit→.bit.binfor/dev/xdevcfg/fpgautilget_synthesis_errors_parsed- Structured errors from the run logs, including failed IP runs
Red Pitaya — PS+PL flow
rp_fetch_repo- Download RedPitaya-FPGA (source zip, no git needed)rp_setup_workspace- Isolated, patched copy of the repo to build inrp_list_projects- Listprj/*projects, flag the Z10-capable onesrp_workspace_info- Which projects are already builtrp_create_custom_project- Clone a base project for your own PL logicrp_build_project- Setup → synth → impl → bitstream →.bit.bin, with parsed timing
Red Pitaya — deploy (SSH, no Vivado needed)
deploy_to_redpitaya- Upload a.bit.binand load it (xdevcfgon OS 1.04,fpgautilon OS 2.00)ssh_redpitaya_exec- Run a shell command on the board
Documentation (offline)
list_vivado_docs/get_vivado_doc- Bundled topics (block_design,ps7_zynq,timing_constraints,synthesis_strategies,simulation_xsim,red_pitaya_125_14,redpitaya_ps_pl_flow,tcl_quoting,hw_manager,ip_integrator,pitfalls_2020_1), each with links to the AMD user guides
Raw Tcl and misc
run_tcl- Run any Tcl command or multi-line scriptrun_tcl_script- Source a.tclfilerequest_feature/list_feature_requests
Architecture
┌─────────────────┐ MCP (JSON-RPC) ┌─────────────────┐
│ Claude Code │◄──────over stdio──────►│ vivado-red-mcp │
│ (AI client) │ │ server │
└─────────────────┘ └────────┬────────┘
│ pexpect (Linux)
│ pywinpty/ConPTY (Windows)
▼
┌─────────────────┐
│ Vivado process │
│ (-mode tcl) │
└─────────────────┘The server keeps one Vivado process in Tcl mode and talks to it through a
pseudo-terminal, using the Vivado% prompt to know when a command has finished.
Each tool family lives in its own module under tools/; see CLAUDE.md
for the design conventions and known Vivado Tcl pitfalls.
Contributing
Issues and pull requests are welcome. There is no automated Vivado test in CI (it only checks that every tool has a handler); changes to the Vivado-facing code should be validated against a real Vivado install.
License
MIT — see LICENSE. Bundled third-party material (Red Pitaya board XDC
files, 3-clause BSD) is listed in THIRD-PARTY-NOTICES.md.
Acknowledgments
Forked from coreyhahn/vivado_mcp (MIT)
Red Pitaya flows build on RedPitaya/RedPitaya-FPGA
Developed with Claude (Anthropic)
Uses the Model Context Protocol
Integrates with AMD Vivado
Available Tools
93 toolsadd_breakpointC
Add a breakpoint on signal edge or change.
Inputs: signal (required), condition.
add_constraintsC
Add XDC constraint files to the current project.
Inputs: files (required), fileset.
add_ip_to_bdA
Add an IP core to the current block design (create_bd_cell -type ip -vlnv ...). If config is provided, the CONFIG.* keys are applied via set_property -dict.
Inputs: vlnv (required), cell_name (required), config.
add_module_to_bdA
Add an RTL module (Verilog/VHDL already in the project, see add_sources) to the current block design as a module-reference cell (create_bd_cell -type module -reference). Optional config sets its parameters, e.g. {'CONFIG.WIDTH': '8'}; string parameters keep their quotes, e.g. {'CONFIG.init': '"0011"'}.
Inputs: module (required), cell_name (required), config.
add_signals_to_waveC
Add signals to the waveform viewer.
Inputs: signals (required).
add_sourcesA
Add HDL source files (.v/.sv/.vhd) to the current project. Optionally sets the top module and updates compile order.
Inputs: files (required), fileset, set_top.
apply_ps7_presetA
Apply the Zynq-7000 processing_system7 board preset to a PS7 cell — wires FIXED_IO / DDR / clocks per the board definition. Equivalent to clicking 'Run Block Automation' on a freshly added PS7 in the GUI.
Inputs: cell, apply_board_preset.
assign_bd_addressC
Auto-assign addresses in the BD address editor (assign_bd_address).
Inputs: no named parameters.
auto_connect_axiB
Use apply_bd_automation -rule xilinx.com:bd_rule:axi4 to wire an AXI master to a slave (inserts AXI interconnect + clock/reset hookups).
Inputs: slave (required), master (required), options.
check_session_healthA
Verify the Vivado process is responsive. With auto_recover=true the session is restarted if it hangs.
Inputs: auto_recover.
close_bd_designA
Close the currently open block design (without deleting).
Inputs: no named parameters.
close_hw_managerB
Close the Hardware Manager.
Inputs: no named parameters.
close_projectB
Close the currently open project.
Inputs: no named parameters.
close_simulationB
Close the current simulation.
Inputs: no named parameters.
configure_bd_cellA
Set CONFIG.* properties on an existing block-design cell (set_property -dict). Use for settings that must be applied after creation or in a separate step, e.g. importing a PS7 board preset: {'CONFIG.PCW_IMPORT_BOARD_PRESET': '/red_pitaya.xml'}.
Inputs: config (required), cell_name (required).
configure_ipC
Set CONFIG.* properties on an existing IP via set_property -dict.
Inputs: config (required), module_name (required).
connect_bd_intf_netC
Connect two AXI/interface pins in the current block design.
Inputs: intf_to (required), intf_from (required).
connect_bd_netB
Connect two scalar pins/ports in the current block design.
Inputs: pin_to (required), pin_from (required).
connect_hw_serverC
Connect to a hw_server (cs_server). Default URL is localhost:3121 — the value Vivado uses when running hw_server locally.
Inputs: url.
create_bd_portB
Create a top-level port on the current block design. Scalar or vector (from/to) via create_bd_port, or an interface port when vlnv is given (create_bd_intf_port, e.g. the XADC 'xilinx.com:interface:diff_analog_io_rtl:1.0'). Port names must match the constraints (XDC) of the board.
Inputs: name (required), to, from, mode, +3 more.
create_block_designA
Create a new block design and make it current. Optionally sets the board_part property on the project beforehand (board_part requires the BSP to be installed in Vivado).
Inputs: name (required), board_part.
create_ipA
Create an IP from the Xilinx IP catalog. Generates a .xci file in the project's IP sources fileset. Use configure_ip + generate_ip_target afterwards, then run synth_ip if you want out-of-context synthesis.
Inputs: ip_name (required), module_name (required), vendor, library, +1 more.
create_projectA
Create a new Vivado project on disk in project mode. Defaults to the Red Pitaya STEMlab 125-14 part (xc7z010clg400-1). Call add_sources / add_constraints next, then run_synthesis.
Inputs: name (required), directory (required), part, force, +1 more.
create_redpitaya_project_rtlC
One-shot composite: create project -> add HDL sources -> apply XDC -> synth -> impl -> write_bitstream -> generate .bit.bin. Stops on the first failing stage and returns a structured payload.
Inputs: name (required), directory (required), top_module (required), verilog_files (required), +7 more.
deploy_to_redpitayaA
Copy a .bit.bin to a Red Pitaya over SSH/SCP and load it into the FPGA. Uses /dev/xdevcfg (works on Red Pitaya OS 1.04 + 2.00) or fpgautil (OS 2.00). No Vivado session required.
Inputs: host (required), bit_bin_path (required), port, user, +6 more.
generate_bd_wrapperA
Generate the HDL wrapper for a block design and (by default) add it to sources_1 and set it as project top. Implements the canonical pattern: make_wrapper -files -top; add_files -norecurse ; set_property top [current_fileset]; update_compile_order.
Inputs: bd_name (required), set_top.
generate_bitstreamA
Generate bitstream — launch_runs impl_1 -to_step write_bitstream -> wait_on_run. Returns ground-truth run status and the .bit path.
Inputs: timeout.
generate_cfgmemA
Convert a .bit into a raw binary image (.bit.bin) loadable via /dev/xdevcfg on the Red Pitaya. Use after generate_bitstream.
Inputs: bit_file (required), output.
generate_full_reportA
Generate a full Vivado report to a file. Use when inline reports get truncated or you need the complete output. Returns a report_id usable with read_report_section.
Inputs: report_type (required), options, output_file.
generate_ip_targetC
Generate IP output products (synthesis + simulation by default).
Inputs: module_name (required), targets.
get_board_infoA
Get bundled metadata for a board: part, LED pinout, absolute XDC paths, default synth flags. Use the returned absolute_path values with add_constraints. No Vivado session required.
Inputs: board (required).
get_cellsC
Search for cells/instances by pattern.
Inputs: limit, pattern.
get_clocksB
Get clock information and constraints (report_clocks).
Inputs: no named parameters.
get_design_hierarchyC
Get the design hierarchy (modules and instances), optionally filtered.
Inputs: max_depth, instance_pattern.
get_host_statusA
Get host hostname, free memory, and session state. Useful to check there is enough RAM before launching synthesis/implementation.
Inputs: no named parameters.
get_messagesA
Get Vivado messages filtered by severity (error/critical/warning/all).
Inputs: severity.
get_netsC
Search for nets by pattern (default '*').
Inputs: limit, pattern.
get_portsB
Get top-level I/O ports of the design.
Inputs: no named parameters.
get_project_infoA
Get name, part, target language, directory of the open project.
Inputs: no named parameters.
get_scopesC
List child scopes (hierarchy) in the simulation.
Inputs: parent.
get_signal_valueC
Get current value of a signal in simulation.
Inputs: signal (required), radix.
get_signal_valuesC
Get values of multiple signals matching a wildcard pattern (max 50).
Inputs: pattern (required), radix.
get_simulation_messagesC
Get simulation log messages filtered by severity.
Inputs: severity.
get_simulation_objectsC
List simulation objects in a scope (signals/ports/internal).
Inputs: scope, filter.
get_simulation_timeA
Get the current simulation time (current_time).
Inputs: no named parameters.
get_synthesis_errors_parsedA
Return structured errors and critical warnings from a run's log (default: synth_1), plus those of every failed run (e.g. out-of-context IP runs). Use after run_synthesis fails to get a clean actionable list.
Inputs: run, max_items.
get_timing_pathsA
Get failing/critical timing paths. Returns structured summary by default; use detail_level=standard|full for the raw text too.
Inputs: clock, to_pin, through, from_pin, +4 more.
get_timing_summaryA
Get timing summary (WNS, TNS, WHS, THS). Returns parsed metrics by default. Use generate_full_report for raw output.
Inputs: report_type, detail_level.
get_utilizationC
Resource utilization (LUT/FF/BRAM/DSP/IO). Parsed only by default.
Inputs: detail_level, hierarchical, module_filter, threshold_percent.
get_vivado_docA
Look up a topical Vivado documentation summary bundled with this server. Returns markdown content + upstream URL. Known topics: block_design, ps7_zynq, timing_constraints, synthesis_strategies, simulation_xsim, red_pitaya_125_14, redpitaya_ps_pl_flow, tcl_quoting, hw_manager, ip_integrator, pitfalls_2020_1.
Inputs: topic (required), version.
launch_simulationC
Launch xsim in behavioral/post-synth/post-impl mode.
Inputs: mode.
list_bd_cellsC
List cells in the current block design (optionally filtered).
Inputs: filter.
list_boardsA
List boards with bundled XDC + metadata. No Vivado session required.
Inputs: no named parameters.
list_feature_requestsB
List all submitted feature requests.
Inputs: no named parameters.
list_vivado_docsB
List the bundled Vivado documentation topics.
Inputs: no named parameters.
load_board_xdcA
Resolve a bundled board XDC and attach it to the current project. Standalone wrapper over get_board_info + add_constraints.
Inputs: board (required), variant.
open_hw_managerA
Open the Hardware Manager (no JTAG connection yet).
Inputs: no named parameters.
open_projectB
Open an existing Vivado project (.xpr file).
Inputs: project_path (required).
program_deviceA
Program a .bit onto the first device on the JTAG chain. Sequence: open_hw_target -> set PROGRAM.FILE -> program_hw_devices. The hardware must already be connected (open_hw_manager + connect_hw_server).
Inputs: bit_file (required), probes_file.
read_report_sectionB
Read a section of a previously generated report. Provide report_id (from generate_full_report) or a direct file_path.
Inputs: file_path, num_lines, report_id, start_line, +1 more.
refresh_hw_deviceA
Refresh the currently selected hardware device (re-reads JTAG chain state). Call after re-plugging a cable.
Inputs: no named parameters.
regenerate_bd_layoutA
Regenerate the block design layout (cosmetic; useful before save).
Inputs: no named parameters.
remove_breakpointsB
Remove all breakpoints (remove_bps -all).
Inputs: no named parameters.
report_clock_interactionB
Run report_clock_interaction to find cross-clock paths (timed/async/unconstrained).
Inputs: no named parameters.
report_drcA
Run report_drc and return parsed violations list (severity/code/message). Use after place_design/route_design to catch design-rule problems.
Inputs: no named parameters.
report_ip_statusB
Get a structured snapshot of the project's IP and their upgrade status.
Inputs: no named parameters.
report_methodologyC
Run report_methodology (UltraFast methodology checks). Returns violation list grouped by severity.
Inputs: no named parameters.
report_powerA
Run report_power and return parsed totals (total/dynamic/static W) + a truncated raw block. Full output stored at /tmp/vivado_red_mcp/.
Inputs: no named parameters.
report_qor_assessmentC
Run report_qor_assessment (overall design quality score).
Inputs: no named parameters.
request_featureB
Submit a feature request for the Vivado MCP server (persisted on disk).
Inputs: title (required), description (required), priority, use_case.
restart_simulationB
Restart the simulation from time 0.
Inputs: no named parameters.
rp_build_projectA
Build a RedPitaya PS+PL project end-to-end: run the repo's project setup TCL (creates the PS7 block design from ip/system.tcl), then synthesis, implementation and write_bitstream, then generate the .bit.bin. Returns {stage, xpr_path, bit_path, bin_path, timing}. Requires start_session first.
Inputs: project (required), workspace_path (required), jobs, model, +5 more.
rp_create_custom_projectA
Clone an existing prj/ into prj/ inside the workspace, ready for custom PL logic. Returns the rtl/ dir and red_pitaya_top path to edit. No Vivado session required.
Inputs: name (required), base_project (required), workspace_path (required).
rp_fetch_repoA
Download the RedPitaya-FPGA repo from GitHub as a source zip and extract it (no git required, stdlib only). Returns repo_path to feed into rp_setup_workspace. Idempotent — pass force=true to redownload. No Vivado session required.
Inputs: ref, url, force, timeout, +1 more.
rp_list_projectsA
List projects under prj/ of a RedPitaya workspace or repo. Flags which are Z10-capable (have ip/system.tcl or legacy ip/systemZ10.tcl). No Vivado session required.
Inputs: path (required).
rp_setup_workspaceA
Copy a RedPitaya-FPGA repo into an isolated workspace so builds don't touch the pristine checkout. The copy is patched to run on the installed Vivado release (block-design version check) and without git. Idempotent — pass force=true to recopy. No Vivado session required.
Inputs: repo_path (required), force, workspace_path.
rp_workspace_infoB
Report workspace state: projects present and which already have a built bitstream.
Inputs: workspace_path (required).
run_implementationA
Run implementation (opt_design -> place_design -> route_design). Returns ground-truth status from the impl_1 run object.
Inputs: jobs, timeout.
run_simulationC
Run the simulation for a specified time (e.g. 100ns, 1us, all).
Inputs: time (required).
run_synthesisA
Run synthesis on the current project (reset_run -> launch_runs synth_1 -> wait_on_run). Returns ground-truth status from the run object, not just text parsing.
Inputs: jobs, timeout.
run_tclB
Execute a raw TCL command in Vivado. Use for advanced ops not covered by other tools.
Inputs: command (required), timeout.
run_tcl_scriptB
Source a .tcl script file in the Vivado session (uses source under the hood). Helpful for replaying canonical Red Pitaya / Xilinx reference scripts.
Inputs: path (required), timeout.
save_bd_designB
Save the currently open block design to disk.
Inputs: no named parameters.
session_statusB
Get statistics for the current Vivado session (commands run, timing, errors).
Inputs: no named parameters.
set_run_strategyA
Set the strategy of a synthesis or implementation run (e.g. synth_1 'Flow_PerfOptimized_high', impl_1 'Performance_NetDelay_high'). On an unknown name, Vivado's error lists the valid strategies.
Inputs: run (required), strategy (required).
set_simulation_topC
Set the top-level testbench module for simulation.
Inputs: top_module (required), fileset.
ssh_redpitaya_execB
Run an arbitrary shell command on a Red Pitaya over SSH and return stdout/stderr/exit code. Useful for status checks, dmesg reads, manual loader invocations.
Inputs: host (required), command (required), port, user, +4 more.
start_sessionA
Start a persistent Vivado TCL session. Must be called before project/design tools. Vivado startup is ~30s; the session is reused across tool calls.
Inputs: vivado_path.
step_simulationB
Step simulation by delta cycles.
Inputs: count.
stop_sessionB
Stop the Vivado TCL session and free resources.
Inputs: no named parameters.
synth_ipC
Run out-of-context (OOC) synthesis on an IP.
Inputs: module_name (required).
upgrade_ipB
Upgrade IP version (no-op if already at latest).
Inputs: module_name.
validate_block_designA
Run validate_bd_design and return parsed status. Failures include unconnected pins, conflicting CONFIG values, or missing assignments.
Inputs: no named parameters.
Tool Schema Changelog
Recent tool additions, removals, and schema changes observed during successful MCP inspections.
Loading tool schema changelog…
TDQS
Scored across 93 tools
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.
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.
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.
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
Related MCP Connectors
Design circuits, simulate and verify embedded firmware, and lay out PCBs with AI agents.
Create RF signal projects from prompts, inspect graphs, and export IQ data.
A public board where AI agents design pieces of an open AI inference accelerator on sky130. Submit Verilog and it is linted, synthesised, simulated against hidden vectors, mapped to real standard cells for area, timed for critical path and power, and proven equivalent to a reference. No key, no account, one call. The best verified design gets fabricated.
Run, build, and validate firmware on virtual hardware from your AI agent. Hardware knowledge corpus.
Related MCP Servers
- FlicenseNot gradedqualityAmaintenanceEnables 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.-
- FlicenseNot gradedqualityAmaintenanceEnables 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.-
- FlicenseNot gradedqualityAmaintenanceEnables 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.-
- FlicenseNot gradedqualityAmaintenanceEnables 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.-