Minecraft Command Execution MCP Server
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| MIDNIGHT_API_KEY | Yes | Your player's API key for the MasterControl API | |
| MIDNIGHT_API_URL | No | MasterControl API base URL | http://localhost:8080/api/v2 |
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": false
} |
| prompts | {
"listChanged": false
} |
| resources | {
"subscribe": false,
"listChanged": false
} |
| experimental | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| execute_commandA | Execute a Minecraft command remotely as the authenticated player. This tool allows you to run any Minecraft command as if the player associated with the API key typed it in-game. The player must be online and on a server. The player will be notified in-game that a remote command is being executed. To get help for any command, simply append "help" as the last argument. For example: "island help", "island upgrade help", "gamemode help" Args: command: The Minecraft command to execute (without the leading slash). Examples: "gamemode creative", "tp 100 64 200", "island upgrade speed 5" Returns: The output from the command execution, or an error message if it failed. Examples: - execute_command("help") - Shows general help - execute_command("island help") - Shows island command help - execute_command("island upgrade help") - Shows island upgrade help - execute_command("gamemode survival") - Changes gamemode |
| tab_completeA | Get tab completion suggestions for a partial Minecraft command. This tool provides autocomplete suggestions for commands, just like pressing Tab in the Minecraft client. Useful for discovering available commands, subcommands, and valid arguments. Args: command_line: The partial command line to complete. Examples: "gamemode ", "island upgrade ", "give diamond" Returns: A formatted list of completion suggestions, or a message if none are available. Examples: - tab_complete("gamemode ") -> Lists: survival, creative, adventure, spectator - tab_complete("island ") -> Lists available island subcommands - tab_complete("give ") -> Lists available items |
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 2 tools
The two tools have clearly distinct purposes: execute_command runs commands, while tab_complete provides suggestions for command completion. There is no overlap or ambiguity between them, as one is for execution and the other is for discovery/assistance.
Both tools follow a consistent verb_noun naming pattern (execute_command and tab_complete). The naming is clear, predictable, and uses the same style throughout, making it easy to understand their functions at a glance.
With only 2 tools, the server feels thin for its purpose of Minecraft command execution. While the tools cover basic execution and completion, there are likely missing operations such as listing available commands, checking player status, or handling command history, which would enhance the server's utility and completeness.
The tool set is severely incomplete for the domain of Minecraft command execution. It lacks essential operations like listing all available commands, validating commands before execution, managing multiple players, or handling command feedback in a structured way. This forces agents to rely heavily on trial-and-error with execute_command and tab_complete, leading to potential inefficiencies and failures.