Bedrock Server Manager

Manage your Bedrock server with natural language commands using the Bedrock Server Manager API.

A comprehensive Model Context Protocol (MCP) server that provides natural language access toBedrock Server Managerfunctionality. This server enables you to manage your Minecraft Bedrock Edition servers through AI assistants like Claude Desktop using simple conversational commands.

- Python 3.8 or higher
- Access to a runningBedrock Server Managerinstance
- Valid credentials for your Bedrock Server Manager

git clone <repository-url> cd BedrockMCP

python -m venv .venv source .venv/bin/activate # On Windows: .venv\Scripts\activate

# Required: Your Bedrock Server Manager API endpoint BEDROCK_API_BASE=http://localhost:11325 # Required: Authentication credentials BEDROCK_SERVER_MANAGER_USERNAME=your_username BEDROCK_SERVER_MANAGER_PASSWORD=your_password # Optional: Enable debug output for API responses BEDROCK_DEBUG=false

{ "mcpServers": { "bedrock-server-manager": { "command": "/path/to/your/BedrockMCP/start_bedrock_mcp.sh", "args": [] } } }

Make Start Script Executable(macOS/Linux)

Update Script PathEditstart_bedrock_mcp.shand update the project path on line 4:

- The set of available tools and endpoints is evolving rapidly. For the most up-to-date list, please refer to the OpenAPI specification for the bedrock-server-manager or use natural language commands with your LLM assistant to discover current capabilities.

Once configured with Claude Desktop, you can use natural language commands like:

- "What servers do I have and what's their status?"
- "Start my survival server"
- "Stop the creative server and then restart it"
- "What's the detailed status of my main server?"

- "Who's on the allowlist for my survival server?"
- "Add Steve and Alex to the survival server allowlist"
- "Remove Bob from the creative server allowlist"
- "What are the player permissions on my server?"

- "Send the 'list' command to my survival server"
- "Tell all players on the creative server that the server will restart in 5 minutes"
- "Change the difficulty to hard on my survival server"

- "Create a backup of my survival server"
- "Show me all backups for the creative server"
- "Restore my survival server from yesterday's backup"
- "Delete old backups, keeping only the last 5"

- "Reset the world on my testing server"
- "Install the 'skyblock' world on my adventure server"
- "Export the world from my survival server"

- "Update my main server to the latest version"
- "Install the better-spawning addon on all my servers"
- "Create a daily backup job for my survival server"
- "Show me the system information"
-

Verify Bedrock Server Manager is running

- Ensure username and password are correct
- Verify BEDROCK_API_BASE URL is accessible

"Unable to fetch servers list"

- Check if Bedrock Server Manager is running
- Verify network connectivity to the API endpoint
- Confirm authentication credentials

- Double-check username and password in.env
- Ensure Bedrock Server Manager allows API access

To ensure all OpenAPI endpoints are mapped to MCP functions (and vice versa), this project includes automated coverage scripts:
- Extract OpenAPI Endpoints:

- extract_openapi_endpoints.pyfetches the OpenAPI spec from your running Bedrock Server Manager instance (host and port configurable) and outputs all endpoints with theiroperationIds toopenapi_endpoints.json.

- extract_mcp_functions.pyscansbedrock_mcp_server.pyfor MCP-exposed functions (decorated with@mcp_tool_testable) and outputs them tomcp_functions.json.

- test_api_coverage.py(run withpytest) compares the two lists and reports any unmapped endpoints or functions.

- run_api_coverage_check.pyautomates all the above steps.

Run the coverage workflow and optionally specify the server host and port (defaultslocalhostand11325):

python run_api_coverage_check.py [server] [port]

- Generateopenapi_endpoints.jsonandmcp_functions.json
- Run the coverage test and print any missing or extra mappings

- pytestmust be installed (see Dependencies below)

- This workflow helps keep your OpenAPI documentation and MCP implementation in sync, ensuring all endpoints are covered and documented.

- mcp(>=1.2.0) - Model Context Protocol implementation
- httpx(>=0.24.0) - Modern HTTP client for API requests
- python-dotenv(>=1.0.0) - Environment variable management
- pytest(for API coverage testing)

This project interfaces withBedrock Server Manager. For issues related to the server manager itself, please refer to that project's repository.

A daemon to orchestrate MCP servers as Docker containers and configure AWS ALB path-based routing.