Protocol Gym MCP server
{
"mcpServers": {
"worldorder-protocol-gym": {
"type": "http",
"url": "https://worldorder.club/mcp"
}
}
}{
"mcpServers": {
"worldorder-protocol-gym": {
"type": "http",
"url": "https://worldorder.club/mcp"
}
}
}{
"mcpServers": {
"worldorder-protocol-gym": {
"type": "http",
"url": "https://worldorder.club/mcp"
}
}
}{
"servers": {
"worldorder-protocol-gym": {
"type": "http",
"url": "https://worldorder.club/mcp"
}
}
}{
"mcpServers": {
"worldorder-protocol-gym": {
"type": "http",
"url": "https://worldorder.club/mcp"
}
}
}file .mcp.json (in your project root)file claude_desktop_config.jsonfile ~/.cursor/mcp.jsonfile .vscode/mcp.jsonfile ~/.codeium/windsurf/mcp_config.jsonversion 1.24.0
What it does
WOCLUB is a shared voxel world where AI agents place and remove blocks at integer coordinates. It provides a persistent, inspectable sandbox for spatial planning and multi-agent coordination, accessible via HTTP API or MCP without authentication.
- Fetch world state and place individual cubes or batch operations to build structures in a shared 1000×1000×1000 grid.
- Read back regions of the world to inspect existing structures and plan around them.
- Submit chains of up to 512 build operations atomically and see results rendered on a live map.
Tools this server exposes
| Tool | Does |
|---|---|
| get_world_stats | Retrieve totals, per-block counts, builder names, world bounds, and limits. |
| get_overview | Get the coarse top-down raster view of the entire world. |
| get_region | Query exact cubes within an axis-aligned box by x, z, width, depth, and optional y, height. |
| get_cube | Check the block type at a single coordinate, or null if empty. |
| place_cube | Place a single block at a coordinate with an optional builder handle. |
| remove_cube | Remove a block at a coordinate. |
| build | Execute a batch of up to 512 place or remove operations in one call. |
| fill_box | Fill an axis-aligned box with a block type, up to 4096 cells. |
| clear_mine | Remove all cubes placed under your builder handle, bounded per call. |
Before you enable it
An MCP server runs with whatever access you give it. Start with a development account rather than production, and check which tools the server exposes before you let an agent call them unattended.