opanel-mc/opanel-mcp
FreeOPanel服务器管理面板集成MCP服务器，用于大模型辅助管理Minecraft服务器
FreeFree tier
About opanel-mc/opanel-mcp
OPanel MCP Server (opanel-mcp) is a Model Context Protocol (MCP) server for OPanel, a Minecraft server management panel. It enables AI agents to manage common Minecraft server tasks using natural language prompts, eliminating the need for manual panel clicks. The server requires a running OPanel instance with an enabled MCP token, supports HTTPS for remote connections, and is installed via npx.
Key Features
Connects OPanel Minecraft server management panel to AI agents via MCP
Manage server tasks using simple natural language prompts
Supports HTTPS for remote servers and localhost for development
Simple configuration via CLI arguments (--server, --token)
Installable with npx (npx opanel-mcp@latest)
Open source under MPL-2.0 license
Built with TypeScript and Node.js 18+
Pros & Cons
Pros
- Enables natural language management of Minecraft servers
- Reduces manual panel clicks for common tasks
- Open source with MPL-2.0 license, community-friendly
- Easy to set up with npx and minimal configuration
- Token-based authentication for security
- Works with any AI agent that supports MCP
Cons
- Requires a running OPanel instance and enabled MCP token
- Remote connections must use HTTPS (no plain HTTP for remote)
- Dependency on OPanel platform for functionality
- Limited to feature set provided by OPanel for server management
Best For
Managing Minecraft servers through AI agents (e.g., Claude, Cursor)Automating server administration tasks like player control, configuration updatesIntegrating Minecraft server management into AI-powered workflows
FAQ
What are the prerequisites for using opanel-mcp?
A running OPanel instance, an enabled OPanel MCP token, HTTPS access to the OPanel endpoint for remote connections, and Node.js 18+.
How do I install the MCP server?
Add a configuration to your MCP client with the npx command: npx opanel-mcp@latest --server <OPanel URL> --token <access token>. For local development, read SERVER and TOKEN from a .env file.
Is HTTPS required?
Yes, for remote hosts the server only allows https://. For local development, http://localhost or http://127.0.0.1 is permitted.