MCP Minecraft Remote
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {
"listChanged": true
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| connectToServerC | Connect to a Minecraft server with the specified credentials |
| disconnectFromServerA | Disconnect from the Minecraft server |
| sendChatB | Send a chat message to the Minecraft server |
| getPositionA | Get the current position of the player in the Minecraft world |
| moveToB | Move the player to a specific location |
| moveControlC | Control the player with basic movement commands |
| lookAtB | Make the player look in a specific direction or at coordinates |
| digBlockB | Dig a block at the specified coordinates |
| placeBlockC | Place a block at the specified location |
| getNearbyPlayersA | Get a list of players nearby |
| getServerInfoA | Get information about the currently connected server |
| checkInventoryB | Check the items in the player inventory |
| equipItemA | Equip an item from inventory to hand or armor slot |
| inventoryDetailsB | Get detailed information about inventory items |
| tossItemC | Throw items from inventory |
| getNearbyEntitiesB | Get a list of all entities nearby |
| attackEntityC | Attack a specific entity |
| useOnEntityB | Use held item on a specific entity |
| followEntityC | Follow a specific entity |
| openContainerB | Open a container (chest, furnace, etc.) at specific coordinates |
| withdrawItemB | Take items from an open container |
| depositItemB | Put items into an open container |
| closeContainerA | Close the currently open container |
| getRecipesC | Get a list of available crafting recipes |
| craftItemB | Craft an item using available materials |
| listTradesB | List available trades from a nearby villager |
| tradeWithVillagerB | Trade with a nearby villager |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 27 tools
Most tools target distinct actions (e.g., attack vs. follow vs. use on entity). The only minor overlap is between getNearbyEntities and getNearbyPlayers, but descriptions clarify the latter is a subset.
The vast majority follow a verb_noun pattern (e.g., checkInventory, digBlock). One outlier is inventoryDetails, which should be getInventoryDetails for consistency.
27 tools is high but justifiable for comprehensive Minecraft control. It sits between the borderline heavy (16-25) and excessive (25+), but each tool serves a distinct purpose.
Major actions are covered, but notable gaps exist: no tool to inspect container contents (only deposit/withdraw), and no way to use items on blocks (only entities). This can hinder essential workflows.