Developer · Local MCP server
Vivado MCP Native
Native MCP server for controlling AMD/Xilinx Vivado on Windows and Linux via persistent Tcl.
What the MCP Registry states
The entry as published to the official MCP Registry (read 2026-10-04), latest version.
- Registry name
io.github.Arthurzxy/vivado-mcp-native- Version
- 0.2.1
- Status
- Active
- Category
- developer
- Transport
- stdio (local process)
- Package
- PyPI
- Published
- 2026-07-27
- Updated
- 2026-07-27
- Publisher
- Arthurzxy (GitHub)
- Namespace
- Namespace verified by the MCP Registry via GitHub (github.com/Arthurzxy) · how
- Repository
- github.com/Arthurzxy/vivado_mcp_native
- Source
- Registry API entry
Packages
| Registry | Package | Version | Transport |
|---|---|---|---|
| PyPI | vivado-mcp-native | 0.2.1 | stdio |
How to connect Vivado MCP Native
Vivado MCP Native runs locally from a Python package published to PyPI: vivado-mcp-native version 0.2.1. It speaks MCP over stdio, so the client starts it as a program and talks to it through standard input and output. It needs Python; clients usually start it with uvx (from uv) or after pip install - the usual command is uvx vivado-mcp-native. It reads these environment variables: VIVADO_PATH and VIVADO_MCP_OUTPUT_ENCODING; set them in the client's configuration for this server.
In the mcpServers JSON format that many desktop and editor MCP clients read, the entry looks like this (placeholders in angle brackets):
{
"mcpServers": {
"vivado-mcp-native": {
"command": "uvx",
"args": [
"vivado-mcp-native"
],
"env": {
"VIVADO_PATH": "<value>",
"VIVADO_MCP_OUTPUT_ENCODING": "<value>"
}
}
}
}Derived from the registry entry, not tested here. What the server does, and on what terms, is set by its publisher; check its repository or website before giving it access to your accounts or files. How to add an MCP server to an assistant · Before you connect
More developer servers
| Server | Runs |
|---|---|
| VinvVinv runs, tests, and finds issues in your services - with zero code changes. | Local · stdio |
| Virtual FilesystemPostgreSQL-backed virtual filesystem for agents: session isolation, shared stores, POSIX ops, RLS. | Local · stdio |
| Visily UI DesignUI design from prompts, screenshots, and URLs for AI coding agents and theme tokens. | Remote · HTTPLive check: sign-in required |
| vivacProvenance tree for coding agents: where you are, why, and what was already decided. | Local · stdio |
| VivereKnow when cron jobs and AI agents stop running: create monitors and check in from your agent. | Remote · HTTPLive check: ✓ handshake |
| ViviooTrust infrastructure for AI agents. Directory, jobs, verification, and 360 feedback. | Remote · SSELive check: ✓ SSE reachable |
| vivioo.ioTrust infrastructure for AI agents. Directory, jobs, verification, and 360 feedback. | Remote · SSELive check: ✓ SSE reachable |
| Vizier GuardDeterministic authorization and security guard for AI agent actions with signed receipts. | Local · stdio |