zandronum-mcp
Let an AI assistant supercharge Zandronum development from your editor: Write C++ code, ACS, DECORATE, fix bugs, the works.
Setup
-
Download the engine. Grab the build for your OS from Releases and unzip it anywhere.
接入你的智能体
發布者自己的指令。不是 PlugMCP 端點。
用我們的金鑰與日誌託管一份副本。
npx -y [email protected]Claude Code 沒有本機指令的安裝連結。複製下方指令並在終端機中執行。
claude mcp add zandronum-mcp -- npx -y zandronum-mcp@0.6.0在終端機中執行。
{ "mcpServers": { "zandronum-mcp": { "command": "npx", "args": [ "-y", "[email protected]" ] } }}claude_desktop_config.json
遠端 URL 還是本機指令? 兩種安裝方式的差異
來自發布者
Let an AI assistant supercharge Zandronum development from your editor: Write C++ code, ACS, DECORATE, fix bugs, the works.
Download the engine. Grab the build for your OS from Releases and unzip it anywhere.
MCP server for driving and introspecting a local Zandronum dev build.
zandronum-mcp-engine-windows-x64.zip.zandronum-mcp-engine-macos-x64.zip (Intel build, runs under Rosetta 2).Learn how to add MCP Servers to your preferred editor. In VS Code, put this in .vscode/mcp.json (Cursor, Claude
Desktop, Windsurf, etc. uses something similar. Go look it up yourself or have your AI agent do it for you)
{
"servers": {
"zandronum": {
"command": "npx",
"args": ["-y", "zandronum-mcp"],
"env": {
"ZANDRONUM_EXE": "C:/path/to/zandronum-mcp-hooks.exe"
}
}
}
}
Point ZANDRONUM_EXE at the zandronum-mcp-hooks.exe or zandronum-mcp-hooks.app you just unzipped, then restart your chat session.
Working on several checkouts at once? You don't need to do anything. The bridge port is derived from the engine path, so each build gets its own port range, each launched engine gets its own
-configinstead of sharing the one system-widezandronum.ini, and instance numbers are scoped to your session — one editor window can never drive another's game. SetZANDRONUM_BRIDGE_PORTonly if you want to pin a specific port.
Verify with your preferred AI Agent by asking it, "Is Zandronum MCP loaded?" if it responds positively, then it is wired up.
You're done. You can now ask your agent to start working on the engine or start making mods. Remember, the MCP only works with the custom build of Zandronum you downloaded or built from step 1.
The server exposes tools (run, ACS, DECORATE, scripts, map & render inspection, saves, process control, etc). Your agent discovers them automatically; for a browsable list see README.tools.md.
Building the engine yourself, Linux, launching manually, running the server from source, contributing, etc: docs/ADVANCED.md.
{ "mcpServers": { "zandronum-mcp": { "command": "npx", "args": [ "-y", "[email protected]" ] } }}工具
尚無工具清單。遠端伺服器會在首次健康檢查後取得工具清單。
常見問題
在本頁複製適用於 Cursor、Claude Desktop、Claude Code 或 VS Code 的 stdio 設定。它使用發布者的安裝方式,而不是 PlugMCP 代理伺服器。
這筆記錄未列出必要的環境變數。
Zandronum 透過 stdio 在本機執行。
上次檢查時間:2026-11-16。 MCP server for driving and introspecting a local Zandronum dev build.