Native MCP server for controlling AMD/Xilinx Vivado on Windows and Linux via persistent Tcl.
Connect Runs on your machine
claude mcp add vivado-mcp-native -e VIVADO_PATH=<VIVADO_PATH> -e VIVADO_MCP_OUTPUT_ENCODING=<VIVADO_MCP_OUTPUT_ENCODING> -- uvx vivado-mcp-native==0.2.1
{
"mcpServers": {
"vivado-mcp-native": {
"command": "uvx",
"args": [
"vivado-mcp-native==0.2.1"
],
"env": {
"VIVADO_PATH": "<VIVADO_PATH>",
"VIVADO_MCP_OUTPUT_ENCODING": "<VIVADO_MCP_OUTPUT_ENCODING>"
}
}
}
}
{
"mcpServers": {
"vivado-mcp-native": {
"command": "uvx",
"args": [
"vivado-mcp-native==0.2.1"
],
"env": {
"VIVADO_PATH": "<VIVADO_PATH>",
"VIVADO_MCP_OUTPUT_ENCODING": "<VIVADO_MCP_OUTPUT_ENCODING>"
}
}
}
}
{
"servers": {
"vivado-mcp-native": {
"type": "stdio",
"command": "uvx",
"args": [
"vivado-mcp-native==0.2.1"
],
"env": {
"VIVADO_PATH": "<VIVADO_PATH>",
"VIVADO_MCP_OUTPUT_ENCODING": "<VIVADO_MCP_OUTPUT_ENCODING>"
}
}
}
}
Replace the values in angle brackets with your own. Keys stay on your machine; we never see them.
Tools
This server runs locally, so its tools are listed by your MCP client once it starts.
Environment variables
| Name | Description |
|---|---|
VIVADO_PATHOptional | Optional path to a Vivado launcher, bin directory, or version directory. |
VIVADO_MCP_OUTPUT_ENCODINGOptional | Optional Vivado Tcl console output encoding, such as utf-8 or gbk. |
Details
| Package | [email protected] (PYPI, stdio) |
| First published | 27 Jul 2026 |
| Last updated | 27 Jul 2026 |
| Registry name | io.github.Arthurzxy/vivado-mcp-native |
More other servers See all
Listing data from the official MCP registry. Status and tools from NestDaddy's daily check. Browse all MCP servers.
