Minecraft RCON MCP Server
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| RCON_HOST | No | RCON server hostname | localhost |
| RCON_PORT | No | RCON server port | 25575 |
| LOG_PREFIX | No | Prefix for filtered log reading | [TEST] |
| SERVER_DIR | Yes | Minecraft server root directory | |
| DATABASE_PATH | No | Path to plugin SQLite database | |
| RCON_PASSWORD | Yes | RCON password |
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 |
|---|---|
| run_commandA | Execute an RCON command on the Minecraft server (without leading slash). |
| run_command_with_logA | Execute an RCON command and capture server log output produced afterwards. |
| read_server_logA | Read the last N lines from the Minecraft server log file. |
| read_test_logA | Read plugin test/debug logs filtered by a configurable prefix. |
| query_databaseA | Execute a read-only SELECT query against the plugin's SQLite database. |
| check_plugin_statusA | Check overall plugin health: RCON connectivity, recent errors in the server log, and database file status. |
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 6 tools
Most tools have clearly distinct purposes: checking plugin status, querying databases, reading server logs, reading test logs, and executing commands. However, run_command and run_command_with_log have some overlap—both execute RCON commands—but their descriptions clarify that the latter is specifically for capturing log output, which helps differentiate them.
All tool names follow a consistent verb_noun pattern (e.g., check_plugin_status, query_database, read_server_log). There are no deviations in naming conventions, making the set predictable and easy to understand.
With 6 tools, the server is well-scoped for managing a Minecraft RCON server. Each tool serves a specific function—monitoring, logging, database queries, and command execution—without feeling excessive or insufficient for the domain.
The toolset covers core operations for Minecraft server management: health checks, log reading, database queries, and command execution. A minor gap is the lack of tools for writing to the database or managing server configurations, but agents can work around this using existing tools like run_command.