Vivado MCP Server
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| VIVADO_BAT_PATH | No | Path to vivado.bat executable. Resolved in order: start_session tool argument, then this env var, then PATH, then fallback. |
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
} |
| experimental | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| start_sessionA | Start a persistent Vivado TCL session (vivado.bat -mode tcl). Optionally override the vivado.bat path. Reuses an existing session if one is already running. |
| run_tcl_commandA | Send an arbitrary TCL command to the persistent Vivado session and return its output. Auto-starts a session if none exists. |
| session_statusA | Return status/statistics for the current Vivado session. |
| stop_sessionB | Stop the running Vivado session and free resources. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 4 tools
Each tool targets a distinct aspect: running commands, querying status, starting, and stopping the session. No ambiguity between them.
All tools use consistent snake_case verb_noun naming (run_tcl_command, session_status, start_session, stop_session), following the same pattern.
For a Vivado session manager, 4 tools is slightly thin but covers the essential lifecycle and command execution. Could be expanded with project or file operations.
The set covers session management and command execution fully. Missing an explicit health check or reset, but most workflows are supported.