Crafty MCP

What HadiCherkaoui/crafty-mcp MCP server does

HadiCherkaoui/crafty-mcp MCP server connects an MCP client to Crafty Controller 4 and exposes Crafty API V2 operations as individual tools. It is intended for administrators who want to manage Minecraft servers from an AI assistant rather than switching between an assistant and the Crafty web panel.

The available operations cover host and panel information, server configuration, runtime control, console access, file management, backups, scheduled tasks, webhooks, users, and roles. Server creation supports Java, Bedrock, and custom server types. The tools can also retrieve live server statistics, historical metrics, console logs, and server configuration.

How it works

The MCP process runs locally and sends requests to the Crafty Controller URL configured in CRAFTY_URL. Authentication can use a bearer token supplied through CRAFTY_API_TOKEN, or an assistant can call crafty_login with a Crafty username and password to obtain a token dynamically. Crafty’s API token can be generated from the user profile’s API Keys section.

An MCP client invokes tools such as server_list, server_start, server_send_command, or server_get_file. Administrative tools can change panel configuration, create or remove servers, alter files, restore backups, manage scheduled tasks, configure webhooks, and administer users and roles. These actions depend on the permissions of the Crafty account or token in use.

Setup and configuration

Install the HadiCherkaoui/crafty-mcp MCP server through npm and register it in the MCP client configuration. A typical stdio setup uses npx -y crafty-mcp and provides the following environment values:

• CRAFTY_URL: Required base URL for the Crafty Controller instance.
• CRAFTY_API_TOKEN: Optional bearer token; dynamic login can be used instead.
• CRAFTY_ALLOW_INSECURE: Set to true when the Crafty instance uses a self-signed certificate.
• CRAFTY_TIMEOUT: Optional request timeout in milliseconds; the documented default is 30,000.

The README gives configuration examples for Claude Desktop, Claude Code, and Cursor. The project can also be built from source with npm install and npm run build, then started with node dist/index.js.

Tools and capabilities

Core capabilities include:

• Inspect Crafty API metadata, schemas, host statistics, and panel configuration.
• Create, update, clone, start, stop, restart, kill, back up, and delete Minecraft servers.
• Read console logs, historical statistics, live resource usage, player counts, versions, and worlds.
• Send console commands and update a server executable.
• List, read, write, create, delete, rename, and decompress server files.
• Create and manage backups, interval or cron tasks, and webhooks.
• Create and administer Crafty users, API keys, permissions, and roles.

Limitations and notes

The server requires access to a running Crafty Controller 4 instance and suitable Crafty permissions. CRAFTY_URL must point to the target panel, while the token is optional only when authentication is performed with crafty_login. Enabling CRAFTY_ALLOW_INSECURE permits self-signed certificates and should be used only when that behavior is appropriate for the deployment. Operations such as deleting servers, files, users, roles, or backups can be destructive, so client workflows should verify targets before invoking them.