
Verdi Bridge
io.github.RuihongYPublished by GitHub account RuihongYv0.3.3Updated Oct 24, 2026
Inspect waveforms and navigate RTL in live Synopsys Verdi. Requires a licensed Verdi installation.
Overview
Connects an AI assistant to a live Synopsys Verdi session so it can find signals, inspect waveforms and navigate RTL source.
- What you can do
- Find and display signals: search signals, browse scopes and add signals to the waveform view.
- Navigate time and errors: set the cursor, set a time window and jump before an error.
- Inspect values: find transitions, read value changes and sample signals, preserving X/Z values.
- Summarize long windows: count changes and sample on a clock.
- Discover error times and clocks: read logs and measure clock periods.
- Follow drivers into RTL: trace drivers, read source and source files, and jump to source.
- When to use it
- For RTL debugging with a licensed Verdi installation, when you want an agent to put relevant signals on screen, inspect their transitions and open the driving source while you follow along in the same GUI. Works locally or over SSH.
- Requirements
- A licensed Synopsys Verdi installation (no vendor software bundled); Python 3.11+ on the client, Python 3.6+ and Verdi's Tcl 8.6 on a remote host. Install the verdi-bridge package or run it with uvx, load the bundled Tcl adapter in Verdi, then run the stdio server. Optional environment variables VERDI_BRIDGE_HOST, VERDI_BRIDGE_DIR and VERDI_BRIDGE_CONTROL_PATH configure SSH and session paths.
Installation
In SourceWeft
- Open Verdi Bridge in the dashboard and add it to a workspace.
- Enable the server for the chats that should use its tools.
Desktop only via STDIO. STDIO servers start a local process, so they need the SourceWeft desktop host.
Other MCP clients
Follow the launch instructions in the repository.
README
[Verdi Bridge — connect AI agents to your live Verdi session]
[PyPI] [Tests] [MIT license] [Python 3.11 or newer]
Getting started · Tool reference · Architecture · 中文
Give your RTL debugging agent eyes on the waveform
Connect your AI agent to live Synopsys Verdi. Let it find signals, inspect transitions, move through simulation time, and open the driving RTL—all in the same GUI you use to debug.
“Add the FIFO read/write pointers, go 20 cycles before the error, and investigate why full stayed high.”
“When did BVALID drop? Show the handshake signals and the code that drives it.”
Verdi Bridge turns those requests into observations from your simulation and visible actions in nWave and nTrace. The agent reasons; the bridge observes. Eighteen typed MCP tools work locally or over SSH with your existing Verdi setup.
Video walkthrough
Ask an agent to investigate a bug, then watch it choose signals, inspect live waveforms and navigate RTL. A 1m38s silent demo: an English prompt and original English agent replies beside synchronized Verdi capture. This is a separate English-language run, not a translation. Tool calls are selected by the agent, not a replay script.
https://github.com/user-attachments/assets/b041c1bd-4be5-4040-b281-2f15001b1e35
How this was recorded · Installation tutorial
Quick start
Or run without a checkout using uv:
This prints the bundled Tcl adapter path. Load it in Verdi and connect your MCP
client, then use uvx verdi-bridge serve as the stdio server.
A licensed Verdi installation is required. Client: Python 3.11+; remote host:
Python 3.6+ and Verdi's Tcl 8.6. No vendor software is bundled.
What you can do
Waveform queries preserve X/Z values. Long windows on large FSDBs can run through Verdi's NPI reader outside the GUI, so the GUI stays responsive. Time arguments carry explicit units. The same interface works with different RTL designs; no FIFO-specific logic is built into the bridge. See the Python and CLI examples.
See it in a real debugging session
Tested with UART TX, AXI-Lite, FIFO and arbiter RTL in licensed VCS/Verdi sessions. The agent can put relevant signals on screen, inspect their changes, and navigate to source while you follow along.
[UART waveform and source in Verdi]
Real RTL examples · Blind debugging trial · Validation results and limitations
Project status
Experimental v0.3.3. Live checks used Verdi T-2022.06-SP2-1 on Linux, including the SSH, session and large-FSDB changes of v0.3.2–v0.3.3 (up to a 2.7 GB FSDB). New-session startup is verified; attachment to an arbitrary existing GUI is not yet separately validated. The bridge does not automatically compile, edit or repair RTL.
Contributing · Trust boundary · Validation limits · Report an issue
Inspired by the agent-to-EDA-tool workflow of virtuoso-bridge-lite. This is an independent implementation. MIT licensed; see third-party notices. Not affiliated with Synopsys. Verdi is a Synopsys trademark.
Source: README.md at commit 62070a3
Tools
0Version history
2- v0.3.3LatestOct 15, 2026
- v0.3.2Oct 14, 2026
Score
50% of the applicable checks met
How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.
- Reached in the last 30 days25 pts
Keep the endpoint answering the MCP handshake; SourceWeft probes it every 30 days.
- Auth declared10 pts
Declare the credential headers in the registry entry, or keep the endpoint answering the probe so its auth can be classified.
- Tools listed15 pts
Answer tools/list without a credential, or ship a package that starts in a sandbox without one.
- DescriptionRequired15 pts
- Logo10 pts
- Documentation15 pts
- License10 pts