Pack local or remote codebases into AI-friendly files that LLMs and coding agents can read or search
Nothing to run from here
Vivado MCP Native is installed from its publisher's own source and answers where it runs, so this marketplace is not in the path of a single call. There is no address here to send one to, and a panel that pretended otherwise would be showing you an answer we made up. Install it and call it from your own client — the Installation tab has the entry for each one.
94/100
trust score
10
downloads a day
local
runs on your machine
151
downloads in 30d
What it does
Native MCP server for controlling AMD/Xilinx Vivado on Windows and Linux via persistent Tcl.
Quickstart
# 1 — add it to Claude Code
claude mcp add --scope user vivado-mcp-native '--' uvx --with 'mcp<2' vivado-mcp-native
# 2 — ask your agent for something these tools do
# start_session, stop_session, session_status and 37 more
Vivado MCP Native costs nothing on mcprush: there is no plan to choose here, no cap to set and nothing mcprush can bill you for.
Publishernot claimed
ARAll 1 server
Arthurzxy1 server
1 category
Collected from a public index. Nobody has claimed this account, so nothing here was written by its author — claim it if it is yours.
Installation
Where are you running it?
Every route below installs the same thing and ends at the same approval screen. This one runs on your machine: your client starts Vivado MCP Native as a process under your own user, with your files and your network, so the tool surface below is what it can do to your computer rather than to a server somewhere else. Its scan result is on the Security tab — read the surface before you approve it.
Claude Codedeclared by this listing
This is a public server: you run it yourself and this marketplace is not in the path. You need uv (docs.astral.sh/uv): uvx comes with it. Claude Code registers it in one command; --scope user makes it available in every project. The '--' is in quotes so that PowerShell passes it on.
claude mcp add --scope user vivado-mcp-native '--' uvx --with 'mcp<2' vivado-mcp-nativeReconnect, or start a new session, and the tools appear in the model’s tool list.
Free on mcprush, and it runs from its publisher’s own package: this marketplace is not in the path, so there is no key of ours to hold and no card to add.
What it asks of you
Nothing is required, but it can take VIVADO_PATH (Optional path to a Vivado launcher, bin directory, or version directory.), VIVADO_MCP_OUTPUT_ENCODING (Optional Vivado Tcl console output encoding, such as utf-8 or gbk.) if you want to set them.
What it writes
One config entry your client uses to start the process locally. A local server runs with your file system and your network, which is why it is priced without metering.
What you approve
40 tools, with what each one reads, writes and reaches shown before you agree — the same list on every route above. Read the tool surface.
Tool surface
What the model actually sees. Descriptions are diffed on every release — see version history.
Start a persistent Vivado TCL session. Must be called before other commands.
No parameter schema on file.
Stop the Vivado TCL session and free resources
No parameter schema on file.
Get status and statistics of the current Vivado session
No parameter schema on file.
Check if Vivado session is responsive and recover if needed. Use this if commands are timing out or behaving unexpectedly.
No parameter schema on file.
Get status of this Vivado MCP server host including hostname, free memory, and session state. If free memory is below 64GB, use vivado-snoke instead.
No parameter schema on file.
Open a Vivado project (.xpr file)
No parameter schema on file.
Close the current project
No parameter schema on file.
Get information about the currently open project
No parameter schema on file.
Run synthesis on the current project
No parameter schema on file.
Run implementation (place and route) on the current project
No parameter schema on file.
Generate bitstream for the implemented design
No parameter schema on file.
Get timing summary (WNS, TNS, WHS, THS). Returns parsed metrics only by default. Use generate_full_report for raw output.
No parameter schema on file.
Get timing paths for failing or critical paths. Returns structured summary (slack, source, dest, clocks) by default. Use generate_full_report for verbose path details.
No parameter schema on file.
Get resource utilization (LUT, FF, BRAM, DSP, IO). Returns parsed metrics only by default. Use generate_full_report for hierarchical details.
No parameter schema on file.
Get clock information and constraints
No parameter schema on file.
Get synthesis/implementation messages (errors, warnings)
No parameter schema on file.
Get the design hierarchy (modules and instances)
No parameter schema on file.
Get top-level ports of the design
No parameter schema on file.
Search for nets in the design
No parameter schema on file.
Search for cells (instances) in the design
No parameter schema on file.
Execute a raw TCL command in Vivado. Use for advanced operations not covered by other tools.
No parameter schema on file.
Launch behavioral simulation (xsim). Opens the simulator and loads the design.
No parameter schema on file.
Run the simulation for a specified time
No parameter schema on file.
Restart the simulation from time 0
No parameter schema on file.
Close the current simulation
No parameter schema on file.
Get the current simulation time
No parameter schema on file.
Get the current value of a signal in simulation
No parameter schema on file.
Get current values of multiple signals matching a pattern
No parameter schema on file.
Add signals to the waveform viewer
No parameter schema on file.
Set the top module for simulation
No parameter schema on file.
List simulation objects (signals, variables) in a scope
No parameter schema on file.
List available scopes (hierarchy) in the simulation
No parameter schema on file.
Step the simulation by a delta cycle or time step
No parameter schema on file.
Add a simulation breakpoint on a signal condition
No parameter schema on file.
Remove all breakpoints
No parameter schema on file.
Get simulation log messages (errors, warnings, info)
No parameter schema on file.
Request a new feature or capability for the Vivado MCP server. Use this when you encounter a limitation or wish you had a tool that doesn
No parameter schema on file.
List all feature requests that have been submitted
No parameter schema on file.
Generate a full Vivado report to a file. Use when inline reports are truncated or you need the complete output.
No parameter schema on file.
Read a section of a previously generated report file
No parameter schema on file.
Free
$0 forever
- Every tool, no call limit
- No card, and mcprush charges nothing for it
- Source published under MIT
- Runs on your machine — nothing of it reaches our gateway
- Nothing to cap, because mcprush bills nothing
What counts against your monthly calls
| Tool | Unit | Calls used | Out of the allowance |
|---|
Nothing here is billable: mcprush charges nothing to install Vivado MCP Native or to call it, at any volume.
Call allowance · this installenforced at the gateway
Monthly allowance, in calls
—
—
Alert at 80% · then the tool returns a normal MCP error
Used this month: —
ATrust score 94 / 100
Release 0.2.1 · scanned 15 Oct 2026
Two independent axes, because powerful and malicious are different questions. The grade is threat only. The capability level is blast radius, and it is never a penalty on the grade — it is priced as one subtract-only term in the score, where you can see it.
Threat score100
Client score94
Findings1 threat · 3 capability
Capabilityhigh
Coveragesource
Verificationsource
Surface digest024f6d262d2ac58f4b77a4e9fe6aee258970753f88e0742ab055b82a45c96faf
Score vectorthreat 100 → client 94
| Term | Level | What it prices | Points |
|---|---|---|---|
| capability-exposure | high | capability blast radius (high) — client exposure if the model is manipulated | −6 |
| verification-discount | source | publisher verification (provenance) — cryptographic build provenance ties the artifact to its source | −0 |
| coverage-honesty | source | inspection depth (source) — how much of the target the scan could see | −0 |
score = clamp(round(threatScore − E_cap − E_ver − E_cov), 0, 100). No model, no opinion, no network call at scoring time: the same methodology version against the same bytes always produces this number, and every line above is a field of the report rather than a summary of it.
What the scan could actually read
A grade is only as meaningful as its coverage, so the scanner publishes its own depth before it publishes its result.
Tool surfaceread
Implementation sourceread
Package metadataread
Live transportnot available
Tools were statically extracted from the published source (40 recovered), not enumerated from a running server. Tool-poisoning, Unicode-smuggling, capability and toxic-flow analysis ran on this inferred surface, but a mis-parsed registration could be missed or mis-attributed, so tool-derived findings are capped below “confirmed”. To grade the real runtime surface, scan the running server: --command "npx -y <package>".
Capability — what it could do if the model were manipulated
Tags derived from each tool’s schema and the implementation, not from what the tool calls itself. high is the level these add up to.
| Tool | Capability tags | Why the tag was assigned |
|---|---|---|
| start_session | no tags | |
| stop_session | no tags | |
| session_status | no tags | |
| check_session_health | no tags | |
| get_host_status | no tags | |
| open_project | no tags | |
| close_project | no tags | |
| get_project_info | no tags | |
| run_synthesis | no tags | |
| run_implementation | no tags | |
| generate_bitstream | no tags | |
| get_timing_summary | no tags | |
| get_timing_paths | no tags | |
| get_utilization | no tags | |
| get_clocks | no tags | |
| get_messages | no tags | |
| get_design_hierarchy | no tags | |
| get_ports | no tags | |
| get_nets | no tags | |
| get_cells | no tags | |
| run_tcl | code-exec | code-exec: parameter "command" |
| launch_simulation | no tags | |
| run_simulation | no tags | |
| restart_simulation | no tags | |
| close_simulation | no tags | |
| get_simulation_time | no tags | |
| get_signal_value | no tags | |
| get_signal_values | no tags | |
| add_signals_to_wave | no tags | |
| set_simulation_top | no tags | |
| get_simulation_objects | no tags | |
| get_scopes | no tags | |
| step_simulation | no tags | |
| add_breakpoint | no tags | |
| remove_breakpoints | no tags | |
| get_simulation_messages | no tags | |
| request_feature | no tags | |
| list_feature_requests | no tags | |
| generate_full_report | no tags | |
| read_report_section | no tags |
Toxic-flow graph
The lethal trifecta, checked as a graph rather than as a checklist: untrusted input, a sensitive source and an external sink have to meet before there is a path worth worrying about.
The public result for this release does not print the flow graph, so there is nothing to show here. That is not the same as "no paths were found": what the scan did read is above, under coverage.
Supply chain and provenance
Integrityfirst-seen
Surface digest024f6d262d2ac58f
Scanned2026-10-15
This is the first scan of this surface here, so there is nothing yet to compare it against.
Every result on this tab comes from one deterministic pass over the published package — offline, rule by rule, and auditable line by line above. Same methodology version, same bytes, same score.
Release history
Always latest — the install command names no version, so it installs the newest release when it runs; the current release on file is 0.2.1. Pin a release below and the command asks for exactly that one.
0.2.1
undated
latestNo release note was published with this version.
—
no reviews yet
Who can review
One review per account, from a signed-in account that does not publish this listing. Nothing else is asked — you can say what you think before you install it. Publishers can reply once per review, and a review can be edited or deleted by whoever wrote it.
Sign in to write one
Any signed-in account that does not publish Vivado MCP Native can review it, once — before installing it or after. A review from an account that has installed it is marked as one.
No reviews yet
Nobody has reviewed this listing. The rating on the card is the mean of the reviews written here and nothing else, so there is no rating until somebody writes the first — which takes a signed-in account that does not publish it, and nothing else.