Minehut MCP
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| MINEHUT_EMAIL | No | Minehut account email. Used by browser_login_panel when credentials are not passed per call. | |
| MINEHUT_TOKEN | No | Minehut API token. Direct API session (captured automatically after browser login). | |
| MINEHUT_HEADLESS | No | Set to '0' to run the browser visibly (recommended for first login, Cloudflare is friendlier with a visible window). Default is headless. | |
| MINEHUT_PASSWORD | No | Minehut account password. Used by browser_login_panel when credentials are not passed per call. | |
| MINEHUT_SESSION_ID | No | Minehut session ID. Direct API session (captured automatically after browser login). |
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 |
|---|---|
| minehut_statusA | Get the status, player count, RAM, MOTD, version and plugins of a Minehut server. Accepts the server name or its id. |
| minehut_serversA | List all servers on the logged-in Minehut account with their current status. |
| minehut_startA | Power on a Minehut server by name or id. |
| minehut_stopA | Power off a Minehut server by name or id. |
| minehut_restartC | Stop and start a Minehut server again. |
| minehut_commandA | Send any console command to a Minehut server (runs with operator privileges), e.g. 'say hello', 'time set day', 'give Inxx diamond 64', 'lp user Inxx group set admin'. |
| minehut_logsA | Read the most recent log lines of a Minehut server (useful to check console output, crashes, errors). |
| minehut_upgrade_ramB | Change the RAM allocation of a Minehut server. Minehut limits total RAM based on your plan. |
| browser_openA | Open a URL in the controlled browser (defaults to the Minehut dashboard) and return the page title, current URL and visible text so the AI understands the page. |
| browser_login_panelA | Log into the Minehut dashboard in the controlled browser using the provided credentials or MINEHUT_EMAIL and MINEHUT_PASSWORD. Captures the API session automatically when possible. Cloudflare challenges may need browser_wait_manual afterward. |
| browser_wait_manualA | Wait a number of seconds while the user finishes a manual action in the visible browser (Cloudflare challenge, 2FA, password manager), then capture the session tokens. |
| browser_clickA | Click the first visible element matching a CSS selector, e.g. 'button:has-text("Start")', '.server-row', 'a[href*="/console"]'. |
| browser_typeA | Type text into the first visible element matching a selector. Optionally press Enter afterwards. |
| browser_pressA | Press a keyboard key on the page, e.g. Enter, Escape, Tab, F5. |
| browser_textA | Return the visible text of an element (or the whole page when no selector is given) so the AI can read the current state of the panel. |
| browser_screenshotA | Take a screenshot of the page (or of one element) and return it as an image plus the saved file path. The AI can read the image contents. |
| browser_evaluateA | Run a small JavaScript expression in the dashboard page and return its result. Useful for reading React state, clicking via JS, or advanced automation. |
| browser_closeA | Close the controlled browser window and release resources. |
| minehut_helpA | Show a short guide about how to use this server, including the recommended flow for first-time setup with Minehut. |
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 19 tools
The tools are clearly separated by prefix: minehut_* for direct API operations and browser_* for dashboard automation. Within each group, actions are distinct (start vs stop vs restart, click vs type vs press). However, there is potential overlap between direct server actions and browser-based equivalents, e.g., minehut_start vs browser_click on a start button, though descriptions hint at the intended use.
The minehut_* group uses a mix of nouns (status, servers, logs, help) and verbs (start, stop, restart, command, upgrade_ram), while the browser_* group is more consistently verb-based (open, click, type, press, close, evaluate) but includes nouns (text, screenshot). The prefix system provides structure, but the lack of a uniform verb_noun pattern across all tools is a minor inconsistency.
19 tools is slightly above the typical well-scoped range (3-15), but the dual API/browser design justifies the count. Each tool serves a distinct function, and no tool feels redundant or unnecessary.
The server covers essential Minehut operations: status, list, start, stop, restart, command, logs, and RAM upgrades. Missing create/delete server operations, but the browser automation tools can handle dashboard actions, and minehut_help provides guidance. The core lifecycle of managing an existing server is well covered.