Everything happens through one logged-in player: it walks, digs, opens the chest in front of it and hands items to a villager, and getNearbyPlayers means other people on the server see the same character. Because credentials go to connectToServer at call time, the server keeps nothing between runs. There is no batch or blueprint primitive — placeBlock takes one coordinate triple, so a structure costs as many calls as it has blocks.
A remote-control server for one Minecraft player — 27 tools spanning connection, movement, world edits, inventory, containers, crafting and villager trade.
- A session against any reachable server: connectToServer takes host, port, username, password and version, and disconnectFromServer ends it.
- Movement and aim — moveTo for exact coordinates, moveControl for a basic action held for a duration, lookAt for direction, getPosition to read where the player stands.
- World edits at explicit coordinates through digBlock and placeBlock.
- Inventory handling: checkInventory and inventoryDetails to read it, equipItem to hand or armor slot, tossItem to drop a count of something.
- Container work — openContainer at coordinates, then withdrawItem, depositItem and closeContainer.
- Entity interaction: getNearbyEntities within a range, attackEntity, useOnEntity with the held item, followEntity at a set distance.
- Crafting and commerce — getRecipes, craftItem, listTrades from a nearby villager, and tradeWithVillager by trade index.
A reachable Minecraft server and an account on it. The login is passed to connectToServer per session — host, port, username, password and version — so nothing is held in the environment.
One command — npx -y mcp-minecraft-remote@latest