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.
Potencia tu agente
El comando propio del publicador. No es un endpoint de PlugMCP.
Host a copy with our keys and logs.
npx -y [email protected]Claude Code no tiene enlace de instalación para un comando local. Copia el comando de abajo y ejecútalo en una terminal.
claude mcp add zandronum-mcp -- npx -y zandronum-mcp@0.6.0Ejecútalo en una terminal.
{ "mcpServers": { "zandronum-mcp": { "command": "npx", "args": [ "-y", "[email protected]" ] } }}claude_desktop_config.json
¿URL remota o un comando en tu máquina? En qué se diferencian las dos instalaciones
Ejecutar en PlugMCP
A new server you create. It is not this listing's official endpoint. Use the publisher install when you want their URL and their credentials.
AbrirDel publicador
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.
MCP server for driving and introspecting a local Zandronum dev build.
{ "mcpServers": { "zandronum-mcp": { "command": "npx", "args": [ "-y", "[email protected]" ] } }}Herramientas
Aún no hay lista de herramientas. Los servidores remotos la reciben tras la primera comprobación de estado.
Preguntas frecuentes
Copia en esta página la configuración stdio para Cursor, Claude Desktop, Claude Code o VS Code. Usa la instalación del publicador, no un proxy de PlugMCP.
Este registro no indica ninguna variable de entorno obligatoria.
Zandronum se ejecuta localmente por stdio.
Última comprobación: 2026-11-16. MCP server for driving and introspecting a local Zandronum dev build.