mcc-fleet
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| MCC_BINARY | No | Path to the mcc executable | mcc |
| MCC_SERVER_HOST | No | Minecraft server hostname | localhost |
| MCC_SERVER_PORT | No | Minecraft server port | 25565 |
| MCC_BASE_MCP_PORT | No | First MCP port to allocate for bot instances | 33334 |
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
} |
| logging | {} |
| prompts | {
"listChanged": false
} |
| resources | {
"subscribe": false,
"listChanged": false
} |
| extensions | {
"io.modelcontextprotocol/ui": {}
} |
| experimental | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| spawn_botA | Start a new MCC bot that joins the server under Waits until the bot's in-game MCP endpoint is ready. Returns its status and the
tools it exposes. |
| list_botsA | List all bots with their status, MCP port, pid and uptime. |
| list_bot_toolsB | List the in-game tools a ready bot exposes (discovered from its MCC instance). |
| bot_callC | Invoke one of a bot's in-game tools. |
| stop_botC | Disconnect and terminate a bot's MCC process. |
| stop_allA | Disconnect and terminate every running bot. |
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
Each tool has a clearly distinct purpose: listing bots, listing their tools, spawning, stopping, and invoking tools. No ambiguity between tools.
All tools follow a consistent verb_noun naming pattern (e.g., spawn_bot, stop_bot, bot_call), using snake_case throughout.
With 6 tools covering fleet management operations, the count is well within the ideal range and feels appropriately scoped for the domain.
The toolset covers essential lifecycle operations (spawn, list, stop, call) but lacks a dedicated tool for inspecting a single bot's detailed status or logs, which is a minor gap.