worldbox-mcp
Give your AI agent god-mode in WorldBox. Spawn dragons. Burn continents. Run civilization speedruns. From a conversation.
Potencialize seu agente
Instalação do publicador. Não é um endpoint do PlugMCP.
Host a copy with our keys and logs.
Ainda não há uma versão empacotada no registro. Siga o README do repositório.
URL remota ou um comando na sua máquina? Como as duas instalações diferem
Rodar no 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.
AbrirDo publicador
Give your AI agent god-mode in WorldBox. Spawn dragons. Burn continents. Run civilization speedruns. From a conversation.
An MCP server that lets any AI agent (Claude Code, OpenCode, Codex, Cursor, ...) directly control the game WorldBox. Includes a BepInEx C# mod that exposes a local HTTP API to the game's internals, and a Python MCP server distributed on PyPI.
worldbox-mcp is a two-piece bridge that lets any MCP-compatible AI client (Claude Code, OpenCode, Codex, Cursor, Continue, ...) directly control the live game WorldBox.
29 MCP tools spanning discovery, action, observation, simulation control, multi-agent identity, and an inter-agent message bus. The agent observes the world, chooses what to do, acts on it, then observes the outcome, a full agentic loop running against an actual running game. Since v0.3, multiple AI agents can share the same world simultaneously with role-based permissions, fog-of-war, turn-taking, and direct messaging. See docs/multi-agent.md.
> You: "Build me a Roman empire surrounded by hostile dragons, fast-forward
50 years of evolution, then tell me who's still alive."
> Agent:
pause()
list_actors() → finds 'human', 'dragon'
list_tiles() → finds 'soil_high', 'sand'
paint_tile(soil_high, x=80, y=80, radius=10) # founder territory
spawn(human, x=80, y=80, count=15, adult=True) # the empire
spawn(dragon, x=200, y=80, count=4, adult=True) # the threat
set_speed("x5")
resume()
# ... waits ~10 seconds for 50 years of simulation ...
screenshot()
query_actors(race="human", alive=True)
list_kingdoms()
→ "After 50 years, the Romans built 2 cities. The dragons
razed the western one but the eastern capital Aletalda
still stands with 47 citizens."
The whole exchange is real, examples/scenarios/ecology_smoke.py runs a stripped-down version of it as a smoke test.
┌─────────────┐ MCP stdio ┌──────────────────┐ HTTP 127.0.0.1 ┌─────────────────────┐
│ AI client ├────────────►│ worldbox-mcp ├──────────────────►│ WorldBoxBridge │
│ (any MCP) │ │ (Python on PyPI) │ │ BepInEx C# plugin │
└─────────────┘ └──────────────────┘ │ inside worldbox.exe │
└──────────────────────┘
WorldBoxBridge: a BepInEx 5 plugin (C#) injected into WorldBox that exposes a local, auth-protected HTTP API to the game's internals.worldbox-mcp: a Python MCP server distributed via PyPI (uvx worldbox-mcp) that translates MCP tool calls into HTTP requests against the mod.The mod uses only reflection to access game types (no static binding) so it survives WorldBox updates as long as core class names stay stable. All asset ids (tile types, actor races, powers, world speeds) are discovered at runtime from the running build, so the catalog is always correct.
Requires WorldBox installed (Steam) and Experimental Mode enabled in-game (Settings → Experimental Mode).
# Windows
iex (irm https://raw.githubusercontent.com/fullya99/worldbox-mcp/main/scripts/install-mod.ps1)
# Linux / macOS
curl -fsSL https://raw.githubusercontent.com/fullya99/worldbox-mcp/main/scripts/install-mod.sh | bash
This downloads BepInEx + the latest WorldBoxBridge.dll, installs both into your WorldBox folder, and generates a per-install random auth token. Launch WorldBox once and look for this line in BepInEx/LogOutput.log:
[Info: WorldBoxBridge] listening on http://127.0.0.1:8723
The MCP server runs via uvx (zero install) thanks to the uv tooling.
claude mcp add worldbox -- uvx worldbox-mcp
// ~/.config/opencode/config.json
{
"mcp": {
"worldbox": { "type": "local", "command": ["uvx", "worldbox-mcp"] }
}
}
# ~/.codex/config.toml
[mcp_servers.worldbox]
command = "uvx"
args = ["worldbox-mcp"]
// .cursor/mcp.json
{
"mcpServers": {
"worldbox": { "command": "uvx", "args": ["worldbox-mcp"] }
}
}
# ~/.continue/config.yaml
mcpServers:
- name: worldbox
command: uvx
args: [worldbox-mcp]
Any other MCP-compatible client: see docs/install/manual.md. The server also supports a --http flag for Streamable HTTP transport.
In your agent client:
> Call worldbox_health to verify the bridge is connected.
> Now list_actors and pick a few interesting races, then build me
a small ecology experiment near the center of the map.
Or paste the full god-mode ecology prompt from examples/prompts/godmode-ecology.md to exercise every tool category in one go.
Each tool has rich docstrings the agent reads at startup to decide when to call what. Asset ids that don't exist trigger UNKNOWN_ASSET errors with Levenshtein did_you_mean suggestions drawn from the live catalog.
Full reference: docs/command-reference.md.
Assembly-CSharp.dll in every /health so bug reports are traceable.invoke_power alone covers ~270 actions because the in-game GodPower model unifies spawns, disasters, and toggles. spawn reaches the actor catalog directly for non-power creatures. paint_tile handles terrain. The discovery tools tell the agent what's valid right now in this build.127.0.0.1, 0.0.0.0 is refused at startup. Auth is a per-install random token in BepInEx/config/WorldBoxBridge.cfg, or one bearer per agent in multi-agent mode via BepInEx/config/WorldBoxBridge.agents.json. Constant-time token comparison. No telemetry, no remote endpoints.examples/scenarios/multi-agent/.release-please, automated CI/CD across Win/Linux/Mac × Py 3.11 to 3.13.A daily CI cron monitors WorldBox releases on Steam and opens a tracking issue when a new version ships, so update breakage gets caught the day-of. See docs/compatibility.md.
docs/architecture.md, component layout, thread model, lifecycledocs/multi-agent.md, session layer: agents, permissions, fog-of-war, turns, message bus, objectivesdocs/protocol.md, exact HTTP/JSON contract between server and moddocs/game-api-notes.md, reflection paths into WorldBox's internals (lives alongside the code, updated per game version)docs/development.md, local dev setup + testingexamples/scenarios/ecology_smoke.py, single-agent end-to-end demo (legacy mode)examples/scenarios/multi-agent/pvp_smoke.py, multi-agent PvP end-to-end demoIssues, PRs, new commands welcome. See CONTRIBUTING.md. Good first contributions: drive click_special_action (the last power delegate invoke_power cannot reach), or a get_actor(name_or_id) single-actor lookup.
MIT © 2026 fullya99
worldbox-mcp is an unofficial community project and is not affiliated with or endorsed by the WorldBox developers.
An MCP server that lets any AI agent (Claude Code, OpenCode, Codex, Cursor, ...) directly control the game WorldBox. Includes a BepInEx C# mod that exposes a local HTTP API to the game's internals, an
Visão geral
An MCP server that lets any AI agent (Claude Code, OpenCode, Codex, Cursor, ...) directly control the game WorldBox. Includes a BepInEx C# mod that exposes a local HTTP API to the game's internals, and a Python MCP server distributed on PyPI.
Ferramentas
Ainda não há lista de ferramentas. Servidores remotos recebem uma após a primeira verificação de saúde.
Perguntas frequentes
Copie nesta página a configuração stdio para Cursor, Claude Desktop, Claude Code ou VS Code. Ela usa a instalação do publicador, não um proxy do PlugMCP.
Este registro não lista nenhuma variável de ambiente obrigatória.
Worldbox roda localmente via stdio.
Última verificação: 2026-10-28. An MCP server that lets any AI agent (Claude Code, OpenCode, Codex, Cursor, ...) directly control the game WorldBox. Includes a BepInEx C# mod that exposes a local HTTP API to the game's internals, and a Python MCP server distributed on PyPI.