The 22 tools cover the loop a player actually runs — find the blocks, dig them, craft the result, smelt what needs heat — rather than a build API that skips to the finished structure, so the model has to plan the way you would. read-chat and send-chat make it a participant instead of a process: you can redirect it from inside the game.
A local server that joins a bot to a running Minecraft server and exposes 22 tools for it: movement and flight, inventory and equipment, block placing and digging, block and entity search, crafting and smelting, and chat in both directions.
- Move the bot — move-to-position with a range and timeout, move-in-direction for a duration, fly-to, jump, look-at, get-position.
- Handle what it carries: list-inventory, find-item, equip-item into a chosen slot.
- Change the world: place-block with a face direction, dig-block, get-block-info, and find-blocks to locate nearby blocks of a type within a distance.
- Craft and smelt — list-recipes for what is makeable right now, can-craft for a specific item, get-recipe for the details, craft-item, and smelt-item with a fuel and a furnace position.
- Find the nearest entity of a type within a range (find-entity).
- Talk to the players around it: read-chat returns recent messages, send-chat posts one.
- Check which game mode the bot is in (detect-gamemode).
A Minecraft server the bot can join, and Node.js on the machine. The documented configuration joins localhost on port 25565 as ClaudeBot; --host, --port and --username point it elsewhere. Apache-2.0.
One command — npx -y github:yuniko-software/minecraft-mcp-server --host localhost --port 25565 --username ClaudeBot