MCP server that holds vivado and allows access to vivado without starting a new batch command every time
Config is the same across clients — only the file and path differ.
{
"mcpServers": {
"vivado-mcp": {
"command": "<see-readme>",
"args": []
}
}
}Are you the author?
Add this badge to your README to show your security score and help users find safe servers.
MCP server that holds vivado and allows access to vivado without starting a new batch command every time
No automated test available for this server. Check the GitHub README for setup instructions.
Five weighted categories — click any category to see the underlying evidence.
No known CVEs.
No package registry to scan.
This server is missing a description. Tools and install config are also missing.If you've used it, help the community.
Add informationBe the first to review
Have you used this server?
Share your experience — it helps other developers decide.
Sign in to write a review.
Others in other
Persistent memory using a knowledge graph
Privacy-first. MCP is the protocol for tool access. We're the virtualization layer for context.
Pre-build reality check. Scans GitHub, HN, npm, PyPI, Product Hunt — returns 0-100 signal.
Hash-verified file editing MCP server with token efficiency hook. 11 tools for AI coding agents.
MCP Security Weekly
Get CVE alerts and security updates for Vivado_mcp and similar servers.
Start a conversation
Ask a question, share a tip, or report an issue.
Sign in to join the discussion.
A Model Context Protocol (MCP) server that enables AI assistants like Claude to directly interact with AMD/Xilinx Vivado FPGA development tools.
git clone https://github.com/coreyhahn/vivado_mcp.git
cd vivado_mcp
pip install -e .
Add to your Claude Code MCP configuration (~/.claude/claude_desktop_config.json or project-level .mcp.json):
{
"mcpServers": {
"vivado": {
"command": "vivado-mcp"
}
}
}
Or if you want to specify the Python interpreter:
{
"mcpServers": {
"vivado": {
"command": "python",
"args": ["-m", "vivado_mcp"]
}
}
}
Once configured, Claude can interact with Vivado through natural language. Example workflow:
start_session - Start a persistent Vivado TCL sessionstop_session - Stop the Vivado sessionsession_status - Get session statisticsopen_project - Open a Vivado project (.xpr)close_project - Close the current projectget_project_info - Get project information (part, directory, etc.)run_synthesis - Run synthesisrun_implementation - Run place and routegenerate_bitstream - Generate bitstreamget_timing_summary - Get timing summary (WNS, TNS, WHS, THS)get_timing_paths - Get detailed timing paths for failing/critical pathsget_utilization - Get resource utilization (LUTs, FFs, BRAMs, DSPs)get_clocks - Get clock informationget_messages - Get synthesis/implementation messagesget_design_hierarchy - Get module/instance hierarchyget_ports - Get top-level portsget_nets - Search for netsget_cells - Search for cells/instanceslaunch_simulation - Launch behavioral/post-synth/post-impl simulationrun_simulation - Run simulation for specified timerestart_simulation - Restart from time 0close_simulation - Close the simulatorget_simulation_time - Get current simulation timeget_signal_value - Get a signal's current valueget_signal_values - Get multiple signal values by patternadd_signals_to_wave - Add signals to waveform viewerset_simulation_top - Set the testbench moduleget_simulation_objects - List signals in a scopeget_scopes - List hierarchy scopesstep_simulation - Step simulationadd_breakpoint - Add signal breakpointremove_breakpoints - Remove all breakpointsrun_tcl - Execute raw TCL commandsgenerate_full_report - Generate full reports to fileread_report_section - Read portions of large reportsrequest_feature - Request new featureslist_feature_requests - List submitted requests┌─────────────────┐ MCP Protocol ┌─────────────────┐
│ Claude Code │◄────(JS
... [View full README on GitHub](https://github.com/coreyhahn/vivado_mcp#readme)