Vivado MCP
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| VIVADO_BIN | No | Path to the Vivado executable (e.g., C:\Xilinx\Vivado\2023.1\bin\vivado.bat). If not set, the server attempts to auto-discover Vivado. | |
| VIVADO_MCP_WORKSPACE | No | Default working directory for managed Vivado sessions. | |
| VIVADO_MCP_ALLOWED_ROOTS | No | Semicolon-separated list of allowed root directories for workflow paths. Paths must stay under one of these roots unless using unrestricted capability profile. |
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {
"listChanged": false
} |
| prompts | {
"listChanged": false
} |
| resources | {
"subscribe": false,
"listChanged": false
} |
| experimental | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| vivado_check_installationC | Find Vivado and return its version. |
| vivado_start_sessionC | Start a managed Vivado Tcl session, optionally opening the GUI. |
| vivado_session_stateC | Return current bridge/process state for a managed Vivado session. |
| vivado_list_sessionsA | List active managed Vivado sessions. |
| vivado_stop_sessionC | Stop a managed Vivado session. |
| vivado_run_tclC | Run raw Tcl in a managed session. Requires trusted-local or unrestricted profile. |
| vivado_source_tclB | Source a Tcl file in a managed session. Requires trusted-local or unrestricted profile. |
| vivado_create_projectC | Create a Vivado Project Mode project in the managed session. |
| vivado_open_projectC | Open an existing Vivado project in the managed session. |
| vivado_add_sourcesC | Add RTL/source and constraint files to the current Vivado project. |
| vivado_run_synthesisC | Launch and wait for a Vivado synthesis run. |
| vivado_run_implementationC | Launch and wait for a Vivado implementation run. |
| vivado_generate_bitstreamC | Run implementation through write_bitstream. |
| vivado_reportC | Generate a Vivado report in the managed session. |
| vivado_project_summaryC | Return structured information about the current Vivado project, files, runs, IP, and block designs. |
| vivado_list_artifactsC | List files produced in a managed session directory. |
| vivado_read_artifactC | Read a text artifact from a managed session. |
| vivado_helpC | Return concise help for a Vivado MCP topic. |
| vivado_list_skillsC | List built-in Vivado MCP skills. |
| vivado_get_skillC | Return one built-in Vivado MCP skill document. |
| vivado_suggest_next_stepsC | Suggest next MCP operations from current context. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
| help_index | Vivado MCP help index. |
| resource_skills_index | Built-in Vivado MCP skills index. |
| server_info | Vivado MCP server metadata. |
TDQS
Scored across 21 tools
Most tools have clearly distinct purposes, but there is minor overlap between vivado_run_tcl and vivado_source_tcl, which could cause confusion. Overall, agents can distinguish the tools well.
All tools follow a consistent snake_case pattern with 'vivado_' prefix and verb_noun structure, making predictions easy.
21 tools are well-scoped for a Vivado development server, covering project management, synthesis, implementation, bitstream generation, session management, and reporting without bloat.
The tool surface covers the standard FPGA design flow from project creation to bitstream generation, and includes session and TCL management. Missing simulation-related tools, but that may be out of scope.