MCP for Vivado
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
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 |
|---|---|
| list_public_methodsB | List released v2 public FPGA MCP methods. |
| list_registered_toolchainsA | List registered Vivado toolchains available to stdio workflows. |
| register_toolchain_pathB | Register another Vivado install path or vivado.bat path and persist it for future sessions. |
| remove_registered_toolchainB | Remove a previously registered Vivado toolchain option from stdio workflows. |
| create_workflowD | Create a workflow record. |
| get_workflowC | Get a workflow snapshot. |
| list_workflowsD | List workflows. |
| get_workflow_eventsC | Get public workflow events. |
| design_block_designC | Design a block design workflow intent. |
| design_ipC | Design an IP workflow intent. |
| run_simulationD | Run a simulation workflow intent. |
| confirm_workflowD | Confirm a workflow. |
| reject_workflowC | Reject a workflow. |
| cancel_workflowC | Cancel a workflow. |
| submit_workflow_inputC | Submit workflow user input. |
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 15 tools
Most tools have distinct purposes (e.g., workflow CRUD, toolchain management, design intents), but 'cancel_workflow' and 'reject_workflow' could be ambiguous—both involve stopping a workflow but with different semantics. Descriptions are brief but generally clear.
Tool names follow a consistent verb_noun pattern (e.g., create_workflow, list_workflows). Minor inconsistency: 'design_block_design' is redundant (block design appears twice), and 'run_simulation' uses a different verb style than 'design_*' intents.
15 tools is well-scoped for a Vivado MCP server covering workflow lifecycle, design intents, toolchain registration, and public methods. Each tool serves a clear purpose without unnecessary bloat.
Covers CRUD for workflows, toolchain registration, and design intents. Minor gaps: lacks update/delete for registered toolchains (only remove), and no tool for listing or managing IP/block designs after creation. Core workflows are complete.