Model Context Protocol + VoxelForge tools

Hand Bloxd building tools to any AI.

A website and an MCP server. The model places Stone, carves rivers, raises castles, then exports a real .bloxdschem. Over 160 chunks? It splits itself. Meshes export as World Code you paste into Bloxd.

2,090 official blocks
160 chunk auto-split
45 MCP tools
Live voxel preview · Y is up · same codec Bloxd loads

Builder tools

Boxes, shells, spheres, cylinders, lines, flood fill, terrain brushes, castles, towers, cities, mazes — the VoxelForge kit, as MCP tools an AI can actually call.

.bloxdschem out

Avro + RLE, 32³ chunks. Bigger than Bloxd's 160-chunk cap? Files named build_part001_x0_z64.bloxdschem plus a ZIP, manifest and placement guide.

Mesh → World Code

Coloured boxes and Bloxd-block meshes, like Mesh Studio. Export JavaScript you paste into World Code (or a Code Block). Decorative, not terrain.

0 blocks
orbit drag · scroll zoom · WASD
0 parts
decorative entities · not terrain
Give this to an AI

Streamable HTTP + stdio MCP.

Point Claude, Cursor, or any MCP client at this server. GitHub Pages hosts the studio only; the MCP process is node server.js --stdio on your machine (or any Node host for HTTP).

loading…

        
        

        

          
          Tool JSON
        

      

      

        
What the model can do

        
45 tools including fill_box, fill_sphere, terrain_brush, generate_structure (castle, tower, city…), export_schematic (auto-split at 160 chunks), mesh_add and export_mesh_code.

        
Start with new_project, build with official block names, finish with export_schematic or export_mesh_code.