Minecraft Server MCP
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
} |
| resources | {
"listChanged": true
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| start_serverA | Start the Minecraft Java Edition server. Ensures RCON is enabled and waits for startup completion. |
| stop_serverA | Gracefully stop the Minecraft server. Uses RCON 'stop' command, falls back to stdin, then SIGKILL after 30s. |
| restart_serverA | Restart the Minecraft server (stop then start). Useful after configuration changes. |
| server_statusA | Get the current server status including running state, uptime, online players, and MOTD. |
| server_logsA | Get recent server console output. Useful for debugging startup issues or monitoring activity. |
| validate_serverB | Check if the server directory, JAR file, and EULA are properly configured. |
| configure_mcpC | Update the MCP server configuration (server directory, JAR path, RCON settings, Java path, JVM args). |
| get_server_propertiesA | Read all server.properties settings. Returns key-value pairs with descriptions for known settings. |
| set_server_propertyA | Set a server.properties value. The server must be restarted for changes to take effect. Common properties: gamemode, difficulty, level-seed, level-type, max-players, view-distance, motd, online-mode, pvp, spawn-protection. |
| set_server_properties_bulkA | Set multiple server.properties values at once. Useful for configuring a new server or changing world generation settings. |
| get_game_rulesA | Get all game rules for the current world via RCON. Server must be running. |
| set_game_ruleB | Set a game rule value via RCON. Common rules: doDaylightCycle, doWeatherCycle, doMobSpawning, keepInventory, mobGriefing, doFireTick, randomTickSpeed, playersSleepingPercentage. |
| setup_worldA | Configure server.properties for generating a new world. Sets the level name, seed, world type, and other generation options. The server must be restarted (with the old world deleted or renamed) to generate the new world. |
| list_worldsA | List all Minecraft worlds in the server directory with their sizes. |
| get_world_infoA | Get detailed information about a world from its level.dat file, including seed, spawn point, game type, and version. |
| delete_worldA | Delete a world folder. WARNING: This is irreversible! Consider creating a backup first. The server must be stopped. |
| set_world_spawnA | Set the world spawn point by modifying level.dat. The server must be stopped. |
| execute_commandB | Execute a Minecraft server command via RCON. Send any command without the leading '/'. Examples: 'time set 0', 'weather clear', 'give @a diamond 64', 'tp @a 0 64 0', 'setblock 0 64 0 diamond_block'. |
| execute_commandsA | Execute multiple Minecraft commands sequentially via RCON. Useful for batch operations like building structures or setting up game scenarios. |
| set_timeA | Set the world time. Presets: 'day' (1000), 'noon' (6000), 'sunset' (12000), 'night' (13000), 'midnight' (18000), 'sunrise' (23000). Or use a tick value. |
| set_weatherC | Set the weather. Options: clear, rain, thunder. |
| set_blockC | Place a block at a specific position. Uses the /setblock command. |
| fill_blocksA | Fill a region with blocks. Uses the /fill command. Max 32,768 blocks per operation. |
| summon_entityB | Summon an entity at a position. Examples: 'zombie', 'skeleton', 'villager', 'item_frame', 'armor_stand'. |
| teleportB | Teleport a player or entity to coordinates or another entity. |
| give_itemB | Give items to a player. Examples: 'diamond', 'diamond_sword', 'golden_apple'. |
| list_playersA | List all online players and the server's max player count. |
| op_playerB | Grant operator status to a player. |
| deop_playerC | Revoke operator status from a player. |
| kick_playerB | Kick a player from the server with an optional reason. |
| ban_playerC | Ban a player from the server. |
| pardon_playerA | Remove a ban from a player. |
| whitelist_manageC | Manage the server whitelist. |
| set_gamemodeC | Change a player's game mode. |
| apply_effectA | Apply a status effect to a player. Examples: speed, strength, regeneration, night_vision, invisibility, resistance. |
| list_opsB | List all server operators from ops.json. |
| create_backupA | Create a compressed backup (tar.gz) of a world. Safe to use while the server is running (uses save-off/save-on). |
| list_backupsB | List all available world backups, optionally filtered by world name. |
| restore_backupA | Restore a world from a backup. Creates a safety backup of the current world before overwriting. The server MUST be stopped first. |
| delete_backupC | Delete a backup file. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
| server-status | Current Minecraft server status (running state, players, uptime) |
| server-properties | Current server.properties configuration |
| world-list | List of all worlds with basic info |
| server-logs | Recent server console output (last 100 lines) |
TDQS
Scored across 40 tools
Most tools have distinct purposes with clear boundaries, such as apply_effect for status effects, ban_player for bans, and create_backup for backups. However, there is some overlap between execute_command and execute_commands, which could cause confusion as they differ only in single vs. multiple command execution, and between set_server_property and set_server_properties_bulk, which are similar in function but differ in scope.
Tool names follow a highly consistent verb_noun pattern throughout, such as apply_effect, ban_player, create_backup, and delete_world. All tools use snake_case without deviation, making the naming predictable and easy to understand across the entire set.
With 40 tools, the count is excessive for a Minecraft server management domain, leading to potential bloat and complexity. While the tools cover many operations, a more streamlined set of 15-25 tools could achieve similar functionality without overwhelming users or agents.
The tool set provides comprehensive coverage for Minecraft server management, including server control (start/stop/restart), player management (ban/kick/op), world operations (backup/restore/setup), configuration (properties/game rules), and in-game commands (teleport/summon/set_block). No significant gaps are apparent, supporting full lifecycle management.