About Xsdb MCP
Xsdb MCP is an MCP server published by HashSource in the Data category: xILINX XSDB MCP Server.
The repository has 1 stars and 0 forks, with the last commit 7 months ago. Six months or more without a commit doesn't mean the server is broken, but check the open issues before depending on it in production.
Install
git clone https://github.com/HashSource/xsdb-mcpThis server has no ConduID identity, so agent calls to it are not receipted. Pin the version you install and review the source before granting it credentials.
Tools (5)
--
Parameters not published.
xsdb_connectSpawn XSDB and connect to its TCP server
Parameters not published.
xsdb_disconnectClose connection and kill the process
Parameters not published.
xsdb_evalSend a TCL command and return the result
Parameters not published.
xsdb_statusReport connection state, PID, and port
Parameters not published.
Ask AI
Ask AI about Xsdb MCP
Powered by Claude · Grounded in docs
Security checks
- ✓README presentThe repository ships documentation.
5 checks have not been run yet.
README
xsdb-mcp
MCP server for Xilinx XSDB/XSCT — hardware debugging, FPGA programming, and TCL scripting from AI assistants.
Install
cargo install --path .
Configure
Add to your MCP client settings (e.g. ~/.claude/settings.json):
{
"mcpServers": {
"xsdb": {
"command": "xsdb-mcp",
"args": ["--xsdb-path", "/opt/Xilinx/2025.2/Vivado_Lab/bin/xsdb"]
}
}
}
The XSDB path can also be set via the XSDB_PATH environment variable or passed per-call in xsdb_connect.
Tools
| Tool | Description |
|---|---|
xsdb_connect |
Spawn XSDB and connect to its TCP server |
xsdb_eval |
Send a TCL command and return the result |
xsdb_status |
Report connection state, PID, and port |
xsdb_disconnect |
Close connection and kill the process |
Usage
xsdb_connect → connects using configured path
xsdb_eval "pid" → returns XSDB process ID
xsdb_eval "targets" → list available debug targets
xsdb_eval "fpga -f design.bit" → program FPGA
xsdb_disconnect → clean shutdown
How it works
The server spawns XSDB with xsdbserver start in interactive mode, connects via TCP, and exchanges TCL commands using the XSDB wire protocol (okay <result>\r\n / error <msg>\r\n). Communication with the MCP client uses JSON-RPC over stdio.
License
MIT
README copy captured when this server was indexed; it may lag the repository. The original is authoritative.