Minehut MCP

A Model Context Protocol server that lets any AI agent fully manage your Minehut Minecraft server. It combines a real-browser controller with direct API access, and plugs into Claude Code, Codex, opencode, Cursor, Hermes and any other MCP client.

How it works #

Minehut MCP runs as a local stdio server next to your AI tool. The AI calls tools, and each tool either drives a real Chromium window against the Minehut dashboard or speaks to the Minehut HTTP API. Nothing runs remotely; everything happens on your machine.

Layer	What it is for
`browser_*` tools	Driving the actual dashboard through Playwright: login, Cloudflare, plugin pages, file manager, billing, anything you could do by hand.
`minehut_*` tools	Fast control through the REST API once a session is captured: server power, console commands, logs, player counts, RAM.

Why two layers #

The Minehut dashboard sits behind Cloudflare and its session system changes over time. The browser layer keeps working through any change, because it operates the real UI. When a session is captured, the API layer gives the AI the speed and precision of direct calls. Both layers are always available; neither depends on the other.

Quick start #

Install the package and Chromium.
Register the server with your AI client, following the client setup page.
Ask the AI to run browser_login_panel with your credentials.
Start using minehut_status, minehut_command and the browser tools.

Before you go further. Console commands run with operator privileges and the stored session controls your whole account. Read the safety page.

NextInstallation →