minecraft-bedrock-claude-plugin

Turns a Minecraft build plan into named, reusable structure definitions saved inside the world, so build elements can be placed, copied, and iterated later without any external state. Use after planning, to create or update the structure library for a build. Part of the minecraft-builder workflow.

Designs and blueprints specific named buildings and building complexes in a live Minecraft Bedrock world — real-world replicas (historical and modern), pop-culture replicas (Hogwarts, Minas Tirith), user-described originals, and generative-style fictional buildings — with deep research, advanced building technique, and heavy reuse of defined structure modules. Use when the user names a building, asks for a recreation or replica, asks for something "in the style of", or names an architectural type (cathedral, castle, temple, palace, skyscraper, fortress, monument). Part of the minecraft-builder workflow.

Designs and blueprints whole cities and city districts in a live Minecraft Bedrock world — real-world replicas (modern and historical), pop-culture replicas, and original cities. Plans the urban fabric — district zoning, street hierarchy, transit, walls, and reused vernacular building modules — and defers every named landmark to the building-architect skill. Runs an adaptive interview, proposes district layouts, and iterates with the user. Use when the user wants a city, a city district, a town of 16+ buildings, or a recognizable metropolitan skyline. Part of the minecraft-builder workflow.

Designs, plans, and verifies complex redstone and mechanical contraptions in a live Minecraft Bedrock world — item sorters, hidden and piston doors, automatic farms, mob-spawner collectors, minecart networks and roller coasters, water and bubble elevators, note-block music, traps, and decorative machines. Bedrock-correct: Java-only mechanics are excluded. Designs ship with functional in-world verification and automated correction. Use when the user wants a redstone build, an automatic farm, a contraption, or any working machine. Part of the minecraft-builder workflow.

Verifies a Minecraft Bedrock build in-world after each phase — checks the plan was carried out as specified, that the result fits the world cleanly (no dangling edges, blocked paths, or unintended overrides), and proposes concrete course corrections. Use after every major phase of executing a build plan, as the build's self-correction checkpoint. Part of the minecraft-builder workflow.

Designs and blueprints intentionally designed outdoor space in a live Minecraft Bedrock world — formal gardens, parks, plazas, courtyards, hedge mazes, fountains, parterres, topiary, cloister gardens, estate grounds. Covers French formal, Italian, English landscape, Mughal, Japanese, Chinese, modernist, and other traditions. Geometric and intentional — the deliberate counterpart to the naturalistic terraforming skill. Use when the user wants a garden, park, plaza, courtyard, hedge maze, fountain, or designed grounds. Part of the minecraft-builder workflow.

Designs and blueprints monuments, sculptures, and build-art in a live Minecraft Bedrock world — giant statues, organic creatures and dragons, abstract sculpture, pixel art and murals, large 3D text and logos. Produces solid or shell-only figurative forms with no habitable interiors, using pixel-grid image mapping, organic-curve construction, palette-gradient mapping, and armor-stand detailing. Use when the user wants a statue, sculpture, monument, memorial, mural, pixel art, logo, giant text, or a large creature. Part of the minecraft-builder workflow.

Composes recognizable real-world natural wonders and landmarks — canyons, mesas, monoliths, volcanoes, waterfalls, karst towers, glaciers, sea stacks, salt flats — in a live Minecraft Bedrock world from a library of reusable formation primitives. Use when a build recreates a named natural wonder (Grand Canyon, Niagara, Uluru, Halong Bay, Giant's Causeway, …) or a recognizable landmark type. Part of the minecraft-builder workflow.

Reviews a completed Minecraft build — the plan, the execution, what worked and what did not — and records reusable process lessons in Claude's project memory so future builds go better. Use after a build is finished or a build session wraps up. Part of the minecraft-builder workflow.

Captures build requirements for a Minecraft Bedrock world, interviews the user to resolve ambiguity, and produces a detailed, fully-resolved build plan that a small model can execute mechanically. Use when starting a new Minecraft build or feature, or when a build request must be turned into a concrete plan before any blocks are placed. Part of the minecraft-builder workflow.

Designs and blueprints a player's base of operations in a live Minecraft Bedrock world — a place to live, store, craft, enchant, and display from — not NPC villager housing. Runs an adaptive interview, proposes ASCII / Markdown / Mermaid blueprints, iterates with the user until approved, then writes the build plan. Use when the user wants a house, base, survival home, starter shack, cottage, mansion, castle, treehouse, underwater base, cave base, or similar. Part of the minecraft-builder workflow.

Investigates the current state of a Minecraft Bedrock world — terrain, biomes, existing structures and builds, player surroundings, and anything else needed to ground a build plan. Use before planning a build, or whenever the user asks what is in the world, what is around them, or where there is room to build. Part of the minecraft-builder workflow.

Designs and builds natural-looking terrain and environments in a live Minecraft Bedrock world — mountains, valleys, rivers, lakes, coastlines, caves, biomes, and weathering — using vetted landscaping techniques. Use whenever a build involves shaping land, water, or natural scenery, rather than (or alongside) buildings and structures. Part of the minecraft-builder workflow.

Designs and blueprints world-spanning transit and infrastructure networks in a live Minecraft Bedrock world — rail lines, roads and highways, nether-hub transit, bridges, tunnels, elevators, docks, and airports — the connective network between separate builds. Chooses the network topology and routes the links. Use when the user wants to connect two or more sites, build a transit network, a nether hub, a highway, a bridge, a tunnel, or a rail line between places. Part of the minecraft-builder workflow.

Designs functional, customized villages and settlements in a live Minecraft Bedrock world — hamlets of a few buildings up to standard villages of 5–15 — by reusing standard Minecraft village building types adapted to the biome and the user's request. Runs an adaptive interview, proposes layout options, iterates with the user, and respects Bedrock village mechanics (iron golems, beds, workstations, bells, raids). Use when the user wants a village, hamlet, town, settlement, or trading hub. Part of the minecraft-builder workflow.

Executes a detailed Minecraft build plan step by step — placing, filling, cloning blocks and stamping structures exactly as specified, with no redesign or improvisation. Use to carry out a plan.toon produced by the planner once it is detailed enough to follow mechanically. Part of the minecraft-builder workflow.

Step 2 of 4 of the Minecraft Bedrock MCP setup. Create a Minecraft world with the Beta APIs experiment enabled, export it, transfer it onto the dedicated server, and install + activate the bedrock-bridge behavior pack. Use when the user has a Bedrock Dedicated Server ready and needs a compatible world and the behavior pack installed.

Researches real-world buildings, cities, landmarks, vehicles, and mechanisms so they can be represented faithfully as Minecraft structures. Use when a build request references a real or historical thing and the planner or blueprinter needs accurate proportions, layouts, materials, or details. Part of the minecraft-builder workflow.

Step 4 of 4 of the Minecraft Bedrock MCP setup. Register the running minecraft-bedrock-mcp-server with Claude (Claude Code or Claude Desktop) so the mc_* tools become available, then verify the connection with a live test call. Use when the user has the MCP server running and needs to connect Claude to their Minecraft world.

Step 1 of 4 of the Minecraft Bedrock MCP setup. Install and configure a Minecraft Bedrock Dedicated Server (BDS) — the foundation the MCP stack runs on. Use when the user wants to set up a dedicated Minecraft Bedrock server, start setting up Minecraft for AI/MCP control from scratch, or asks how to get a Bedrock server running so Claude can build in it.

Step 3 of 4 of the Minecraft Bedrock MCP setup. Install the minecraft-bedrock-mcp-server, generate its bearer tokens, write its .env, configure the behavior pack's permissions/variables/secrets files, start BDS and the MCP server, and verify the bridge handshake. Use when the user has a Bedrock server and a world with the behavior pack installed and needs the MCP server running.