vivado-mcp
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| VIVADO_PATH | No | Path to the local Vivado executable. Windows example: "D:/Xilinx/Vivado/2019.1/bin/vivado.bat"; Linux example: "/opt/Xilinx/Vivado/<version>/bin/vivado". Optional: if not set, the Vivado bin directory must be added to the system PATH. This lets the MCP server locate the Vivado executable. | |
| VIVADO_MCP_LOG_DIR | No | Directory for the Vivado startup logs and Launcher logs. Optional; defaults to a "vivado-mcp/logs" directory inside the system temporary directory. Log paths can also be found from the start_session/list_sessions startup_log and launcher_log fields. |
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
Server capabilities have not been inspected yet.
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
No tools | |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
This server cannot be deployed
Maintenance
ActivityActive
ResponsivenessNo issues