What it does
Drive AMD Vivado from AI assistants, with Red Pitaya STEMlab 125-14 build and deploy flows.
- Connects Runs on your computer
- Account or key No key needed
- Category Developer tools
Use together with
Skills that teach the AI this kind of work; they work alongside this one
andrej-karpathy-skills
A single CLAUDE.md file to improve Claude Code behavior, derived from Andrej Karpathy's observations on LLM coding pitfalls.
Why it ranks here
Lists are ordered by a usage score (out of 100) built from these parts
| Popularity | 0/80 | GitHub stars or weekly downloads: the larger counts 60, the smaller 20 |
|---|---|---|
| Freshness | 12/12 | Full marks for a release or code change within 30 days |
| Still answering | 0/8 | The cloud endpoint answered at the last check |
| Usage score | 12/100 |
Quality: Passed 3/3 basic checks (shown, not used for ordering) · Momentum: No data yet (Used only on the Trending tab)
Install
Pick the AI app you use, then copy the settings.
Let your AI install it with one sentence
Please install Vivado Red MCP. Follow https://mcp.popnx.com/i/sinemortal-vivado-red-mcp.md, show me the commands and wait for my OK before running them.Paste it into an AI that can work on your computer (such as Claude Code or Cursor). It reads our steps, shows you the commands and waits for your OK. No key, no sign-up. · See the full text your AI reads
Passed 3/3 checks · Runs on your computer · ✓ Commands checked Nov 14, 2026
First: which AI do you use?
Pick your app and the steps appear below.
Works with Claude, with some setup first
Install Python (uv) on your computer first (one time) · Only the Claude desktop app (Windows or Mac), not the web or phone
Let AI install it
Copy this message into a Claude chat. The AI checks your computer, tells you which file it will change, and waits for your OK every time.
Please install the MCP server Vivado Red MCP for Claude on this computer, in this order: 1) Check uv with uv --version. If it is missing, tell me to install it from https://docs.astral.sh/uv/getting-started/installation/; do not install it yourself. 2) Use only this config (already checked by PopNx MCP): { "mcpServers": { "vivado-red": { "command": "uvx", "args": [ "vivado-red-mcp" ] } } } 3) Tell me the full path of the file you will change, or the command you will run, and wait for my OK. 4) No key is needed. 5) Do what we agreed, then check that the Vivado Red MCP tools really show up.This message has no key in it. If a key is needed, the AI will ask you to paste it yourself into the file or the app’s field.
Install uv (if you don’t have it)
Already installed? Check first · Open Terminal, type this command and press Enter
uv --version- A version number such as uv … = installed, skip this step
- "command not found" (on Windows: "is not recognized") = not installed yet, or installed but Terminal needs to be closed and reopened
How to open Terminal
Mac: press ⌘ + Space, type Terminal, press Enter
Windows: open Start, type Windows PowerShell, then Open
Not installed: uv has no click-through installer. Copy the one-line command for your system (macOS or Windows) from uv’s official page into Terminal · no separate Python install needed; uv downloads it when required
When it’s done, close Terminal, open it again and run the same command. You should see a version number:
uv --versionInstall once; it works for everything that needs uv
Open the Claude desktop app’s settings file
SettingsDeveloperEdit Config
Paste these settings and save the file
{ "mcpServers": { "vivado-red": { "command": "uvx", "args": [ "vivado-red-mcp" ] } } }Quit Claude and open it again
Try it
Use Vivado Red MCP and tell me what you can do for me, then show me one thing✓ If Claude says it is using Vivado Red MCP or shows a Vivado Red MCP tool in the answer, you are connected
1 optional setting(s) (works without them)
The command above works without these. Add them only if you want to change something, following the maker’s description.
VIVADO_MCP_NO_AUTOFETCHSet to 1 to skip downloading the RedPitaya-FPGA repo on startup
Descriptions are as written by the maker.
Menu names checked against Anthropic’s help page on Nov 11, 2026 · your screen may differ slightly by app version
ChatGPT cannot connect Vivado Red MCP yet
Vivado Red MCP runs on your computer, but ChatGPT can only connect servers that run on the web
What you can do instead
A · Use an app that can connect Vivado Red MCP
- Install Python (uv) on your computer first (one time) · Only the Claude desktop app (Windows or Mac), not the web or phone
- Install Python (uv) on your computer first (one time)
- Install Python (uv) on your computer first (one time)
- Install Python (uv) on your computer first (one time)
B · Others in Developer tools that work with ChatGPT
Picked from the most used in the same category, only ones that connect by address with no key
- Sentry✓ ChatGPT
- Compiler Explorer✓ ChatGPT
- GitDiagram✓ ChatGPT
Works with Claude Code, with some setup first
Install Python (uv) on your computer first (one time)
Let AI install it
Copy this message into a Claude Code chat. The AI checks your computer, tells you which file it will change, and waits for your OK every time.
Please install the MCP server Vivado Red MCP for Claude Code on this computer, in this order: 1) Check uv with uv --version. If it is missing, tell me to install it from https://docs.astral.sh/uv/getting-started/installation/; do not install it yourself. 2) Use only this config (already checked by PopNx MCP): claude mcp add --scope user vivado-red -- uvx vivado-red-mcp 3) Tell me the full path of the file you will change, or the command you will run, and wait for my OK. 4) No key is needed. 5) Do what we agreed, then check that the Vivado Red MCP tools really show up.This message has no key in it. If a key is needed, the AI will ask you to paste it yourself into the file or the app’s field.
Install uv (if you don’t have it)
Already installed? Check first · Open Terminal, type this command and press Enter
uv --version- A version number such as uv … = installed, skip this step
- "command not found" (on Windows: "is not recognized") = not installed yet, or installed but Terminal needs to be closed and reopened
How to open Terminal
Mac: press ⌘ + Space, type Terminal, press Enter
Windows: open Start, type Windows PowerShell, then Open
Not installed: uv has no click-through installer. Copy the one-line command for your system (macOS or Windows) from uv’s official page into Terminal · no separate Python install needed; uv downloads it when required
When it’s done, close Terminal, open it again and run the same command. You should see a version number:
uv --versionInstall once; it works for everything that needs uv
Open Terminal
Mac: press Command+Space and type Terminal · Windows: open PowerShell
Paste this command and press Enter
claude mcp add --scope user vivado-red -- uvx vivado-red-mcpType /mcp in Claude Code
You should see Vivado Red MCP listed as connected
Try it
Use Vivado Red MCP and tell me what you can do for me, then show me one thing✓ If Claude Code says it is using Vivado Red MCP or shows a Vivado Red MCP tool in the answer, you are connected
1 optional setting(s) (works without them)
The command above works without these. Add them only if you want to change something, following the maker’s description.
VIVADO_MCP_NO_AUTOFETCHSet to 1 to skip downloading the RedPitaya-FPGA repo on startup
Descriptions are as written by the maker.
Menu names checked against Anthropic’s help page on Nov 11, 2026 · your screen may differ slightly by app version
Works with Cursor, with some setup first
Install Python (uv) on your computer first (one time)
Let AI install it
Copy this message into a Cursor chat. The AI checks your computer, tells you which file it will change, and waits for your OK every time.
Please install the MCP server Vivado Red MCP for Cursor on this computer, in this order: 1) Check uv with uv --version. If it is missing, tell me to install it from https://docs.astral.sh/uv/getting-started/installation/; do not install it yourself. 2) Use only this config (already checked by PopNx MCP): { "mcpServers": { "vivado-red": { "command": "uvx", "args": [ "vivado-red-mcp" ] } } } 3) Tell me the full path of the file you will change, or the command you will run, and wait for my OK. 4) No key is needed. 5) Do what we agreed, then check that the Vivado Red MCP tools really show up.This message has no key in it. If a key is needed, the AI will ask you to paste it yourself into the file or the app’s field.
Install uv (if you don’t have it)
Already installed? Check first · Open Terminal, type this command and press Enter
uv --version- A version number such as uv … = installed, skip this step
- "command not found" (on Windows: "is not recognized") = not installed yet, or installed but Terminal needs to be closed and reopened
How to open Terminal
Mac: press ⌘ + Space, type Terminal, press Enter
Windows: open Start, type Windows PowerShell, then Open
Not installed: uv has no click-through installer. Copy the one-line command for your system (macOS or Windows) from uv’s official page into Terminal · no separate Python install needed; uv downloads it when required
When it’s done, close Terminal, open it again and run the same command. You should see a version number:
uv --versionInstall once; it works for everything that needs uv
Open the AI chat in Cursor in Agent mode
Try it
Use Vivado Red MCP and tell me what you can do for me, then show me one thing✓ If Cursor says it is using Vivado Red MCP or shows a Vivado Red MCP tool in the answer, you are connected
1 optional setting(s) (works without them)
The command above works without these. Add them only if you want to change something, following the maker’s description.
VIVADO_MCP_NO_AUTOFETCHSet to 1 to skip downloading the RedPitaya-FPGA repo on startup
Descriptions are as written by the maker.
Menu names checked against Cursor’s help page on Nov 11, 2026 · your screen may differ slightly by app version
Works with VS Code, with some setup first
Install Python (uv) on your computer first (one time)
Let AI install it
Copy this message into a VS Code chat. The AI checks your computer, tells you which file it will change, and waits for your OK every time.
Please install the MCP server Vivado Red MCP for VS Code on this computer, in this order: 1) Check uv with uv --version. If it is missing, tell me to install it from https://docs.astral.sh/uv/getting-started/installation/; do not install it yourself. 2) Use only this config (already checked by PopNx MCP): { "servers": { "vivado-red": { "type": "stdio", "command": "uvx", "args": [ "vivado-red-mcp" ] } } } 3) Tell me the full path of the file you will change, or the command you will run, and wait for my OK. 4) No key is needed. 5) Do what we agreed, then check that the Vivado Red MCP tools really show up.This message has no key in it. If a key is needed, the AI will ask you to paste it yourself into the file or the app’s field.
Install uv (if you don’t have it)
Already installed? Check first · Open Terminal, type this command and press Enter
uv --version- A version number such as uv … = installed, skip this step
- "command not found" (on Windows: "is not recognized") = not installed yet, or installed but Terminal needs to be closed and reopened
How to open Terminal
Mac: press ⌘ + Space, type Terminal, press Enter
Windows: open Start, type Windows PowerShell, then Open
Not installed: uv has no click-through installer. Copy the one-line command for your system (macOS or Windows) from uv’s official page into Terminal · no separate Python install needed; uv downloads it when required
When it’s done, close Terminal, open it again and run the same command. You should see a version number:
uv --versionInstall once; it works for everything that needs uv
Open the AI chat in VS Code in Agent mode
Try it
Use Vivado Red MCP and tell me what you can do for me, then show me one thing✓ If VS Code says it is using Vivado Red MCP or shows a Vivado Red MCP tool in the answer, you are connected
1 optional setting(s) (works without them)
The command above works without these. Add them only if you want to change something, following the maker’s description.
VIVADO_MCP_NO_AUTOFETCHSet to 1 to skip downloading the RedPitaya-FPGA repo on startup
Descriptions are as written by the maker.
Menu names checked against VS Code’s help page on Nov 11, 2026 · your screen may differ slightly by app version
Other apps that use MCP, such as Windsurf, Zed or Gemini CLI, each add servers differently. See how in the app list.
JSON settings are under “For developers” below
For developers: Terminal commands and JSON settings
Installed on your computer
Claude Code
claude mcp add --scope user vivado-red -- uvx vivado-red-mcpClaude Desktop (claude_desktop_config.json)
{
"mcpServers": {
"vivado-red": {
"command": "uvx",
"args": [
"vivado-red-mcp"
]
}
}
}Cursor (~/.cursor/mcp.json)
{
"mcpServers": {
"vivado-red": {
"command": "uvx",
"args": [
"vivado-red-mcp"
]
}
}
}VS Code (mcp.json)
{
"servers": {
"vivado-red": {
"type": "stdio",
"command": "uvx",
"args": [
"vivado-red-mcp"
]
}
}
}Values you fill in
VIVADO_MCP_NO_AUTOFETCHenvSet to 1 to skip downloading the RedPitaya-FPGA repo on startup
Descriptions are as written by the maker.
These settings are generated from the maker’s registry entry. If the README says otherwise, follow the README.
At a glance
Which apps can use it
Based on how this server connects and on each app’s own docs, checked Nov 10, 2026.
Run on your computer in
ClaudeGooseLM StudioMsty StudioCherry StudioCursorVS Code + GitHub CopilotVisual StudioWindsurf (Devin Desktop)ZedKiroClineContinueJetBrains AI AssistantClaude CodeCodex CLIGemini CLIOpenCodenodecodeWarpLibreChatRaycast
Related guides
What it can do
Runs on your computer; the tool list appears in your AI app after you install it.
Basic checksi
We check information anyone can see; we have not read the code. Checks that do not apply are left out of the count. · Checked Nov 18, 2026
- ✓ Pass
Maker matches the repo
The registry name was verified with the GitHub account sinemortal, which owns the repo
- ✓ Pass
Still maintained
Code last changed 16 days ago
- ✓ Pass
Has a licence
Uses MIT
- – Not applicable
Endpoint responds
This one runs on your computer; there is no internet endpoint
- – Not applicable
Sign-in with OAuth
Runs on your computer and uses local settings instead
- … Not checked yet
No hidden instructions in tool descriptions
Runs on your computer; we can only read tool lists from internet endpoints
Published vulnerabilities (OSV.dev)
No entries on OSV.dev for vivado-red-mcp@0.5.0
Checks only this package version, not every dependency · checked Nov 16, 2026
Makers: ask for a re-check or report wrong info
For makers: add a badge to your README
If you made this, paste this code into your README. The badge links back to this page.
[](https://mcp.popnx.com/en/servers/sinemortal-vivado-red-mcp)Discussion
Ask, share a tip or report that it does not work. Sorted by what people marked helpful.
No posts yet. Be the first to ask or share.
Posts here are written by users, not the PopNx team.
User reviews
No reviews yet
Compared with others in Developer toolsi
- More stars than 0% of the other 6083 servers in this category
- Published to the registry more recently than 63% of the other 6083 servers in this category
- Basic checks equal to or better than 99% of the other 6083 servers in this category
Compared with every active server in this category in the registry. Stars count only when the publisher owns the repo.
Common questions
Is Vivado Red MCP safe?
It passed 3 of 3 applicable basic checks. We have not read the code. Before adding a key or token, see what access the server asks for and use a key with only the permissions you need.
What keys or codes does it need?
The registry does not list a required key, though some servers ask you to sign in on first use.
Does it run on my computer or in the cloud?
It runs on your computer. Your AI app starts it when needed, and data does not pass through the maker’s servers (unless it calls an online service itself).
Is it still maintained?
The GitHub repo last changed 16 days ago, and the latest version (0.5.0) reached the registry 16 days ago.
Which apps can use it?
Apps that support MCP, such as Claude Desktop, Claude Code, Cursor and VS Code. You also need Python (uv) on your computer.
What can I use instead?
In the same category: GitDiagram, Appllama, Cloudflare MCP, Omnara, Repowise
Similar alternatives
Same category, other makers, commands already checked. Official ones first, then by stars.
Reading a card:↓ Downloads per weeki★ GitHub starsiThree pillars: reviews · checks · usageiUpdated = latest version published to the registryi
GitDiagram
Architecture diagrams, explanations and Mermaid source for public GitHub repositories.
Appllama
Study screens, flows and paywalls from top-earning iOS apps, then build from what wins.
Cloudflare MCP
Cloudflare MCP servers
Omnara
Deploy durable AI agents with Omnara, an open-source managed-agent platform.
Repowise
Codebase intelligence for AI coding agents: graph, git history, docs, decisions, code health.
| This one Vivado Red MCP | GitDiagram | Appllama | Cloudflare MCP | Omnara | Repowise | |
|---|---|---|---|---|---|---|
| Runs where | Installs on your computer | Runs in the cloud, nothing to install | Runs in the cloud, nothing to install | Runs in the cloud, nothing to install | Runs in the cloud, nothing to install | Cloud or install on your computer |
| Needs a key | No | No | No | No | No | No |
| Add with + in Claude | No | No | No | Yes | No | No |
| Basic checks | 3/3 | 4/4 | 4/4 | 4/4 | 4/4 | 5/5 |
| License | MIT | MIT | MIT | Apache-2.0 | Apache-2.0 | AGPL-3.0 |
| Price | No cost listed in the registry | No cost listed in the registry | No cost listed in the registry | No cost listed in the registry | No cost listed in the registry | No cost listed in the registry |
README from the maker
Open the README
Copied from the maker’s repo as written. PopNx MCP has not reviewed or endorsed it. HTML, images and scripts are removed. Links lead off this site.
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 is
vivado-red-mcp: Python modulevivado_red_mcp, commandvivado-red-mcp.
Contents
- What it can do
- Tested with
- Requirements
- Installation
- First steps
- Red Pitaya
- What's new in 0.5.0
- Troubleshooting
- Available tools
- Architecture
- License
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 (mcp>=1.0,<2, pinned automatically) |
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 (
/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 /settings64.sh; Windows: add\bintoPATH), or - by 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-mcp
If 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_mcp
Or 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) | create_redpitaya_project_rtl | Logic clocked by the 125 MHz ADC clock: LEDs, counters, expansion-connector GPIO. One call does create → sources → XDC → synth → impl → bitstream → .bit.bin |
| PS + PL | rp_fetch_repo → rp_setup_workspace → rp_build_project | 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_ich,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.xdc` had 6 wrong pins (ADC channel A MSB and
dac_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 |
|---|---|
start_session fails with valid license was not found | Vivado 2025.x/2026.x needs a license file even for the free edition — see Requirements |
start_session cannot find Vivado | Put /bin on PATH or give Claude the full path of vivado.bat / vivado |
Server does not start: 'Server' object has no attribute 'list_tools' | MCP SDK 2.x installed. Run pip install "mcp>=1.0,<2" |
claude mcp list shows vivado as failed | vivado-red-mcp not on PATH for Claude Code: register it with the venv's Python (see Installation) |
A RedPitaya example fails synthesis with red_pitaya_pll ... port does not exist | Upstream issue in prj/Examples/Simple_moving_average (it pulls in rtl_250), not in this server |
Occasional Could not open 'C' for writing in an IP run | 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 recover
-