OpsLevel Official MCP Server: Survival and Creative

Overview

The OpsLevel Official MCP server provides a ready-to-run community Minecraft hosting setup tuned for both Survival and Creative playstyles. The project bundles configuration, runtime orchestration, and operational tips so developers and server operators can deploy and manage a stable, reproducible multiplayer environment for community events, testing, and long-term play.

This repository is useful if you want a minimal, reproducible server deployment that supports multiple game modes (Survival and Creative), automated backups, and common operational hooks (RCON, log rotation, and plugin support). It’s suitable for running locally, on a VM, or inside container orchestration platforms.

GitHub: https://github.com/opslevel/opslevel-mcp

Features

• Dual-mode setup: Survival and Creative worlds with separated data folders
• Container-friendly configuration (Docker / docker-compose examples)
• Environment-driven configuration for automated deployments
• Backup and restore scripts for world data and server configs
• Support for server jars compatible with Vanilla/Paper/Spigot
• Optional RCON and whitelist configuration for admin control
• Basic monitoring hooks: logs, healthcheck endpoints, and resource guidelines
• Example systemd unit and Kubernetes manifest for production deployments

Installation / Configuration

Clone the repository and start from the included templates.

1. Clone the repo

git clone https://github.com/opslevel/opslevel-mcp.git
cd opslevel-mcp

2. Quick start with docker-compose (example)

# docker-compose.yml (excerpt)
version: "3.8"
services:
  mcp-server:
    image: openjdk:17-jdk-slim
    container_name: mcp-server
    volumes:
      - ./data:/opt/minecraft
    ports:
      - "25565:25565"
    environment:
      - SERVER_JAR=/opt/minecraft/server.jar
      - MAX_MEMORY=2G
      - MODE=survival   # or creative
    command: ["/bin/sh", "/opt/minecraft/start.sh"]

Start:

docker-compose up -d

3. systemd unit example (non-container)

[Unit]
Description=OpsLevel MCP Minecraft Server
After=network.target

[Service]
User=minecraft
WorkingDirectory=/srv/minecraft
ExecStart=/usr/bin/java -Xms1G -Xmx2G -jar server.jar nogui
Restart=on-failure

[Install]
WantedBy=multi-user.target

4. Environment variables and config files

• SERVER_JAR: path to the server jar file (e.g., paper.jar)
• MODE: survival | creative
• RCON_ENABLED, RCON_PASSWORD, RCON_PORT
• BACKUP_CRON: schedule for automated backups (when using provided scripts)

Adjust server.properties and whitelist.json in the repository before first run.

Available Resources

• Repository with configuration templates and scripts: https://github.com/opslevel/opslevel-mcp
• start.sh: startup wrapper that applies environment variables and launches the server
• backup.sh / restore.sh: simple world backup and restore utilities
• server.properties.template: example properties used to generate production config
• Example manifests: docker-compose.yml, systemd unit, Kubernetes Deployment+Service
• Optional plugin folder (plugins/): drop-in directory for Paper/Spigot plugins

Configuration layout (example)

Use Cases

• Community server for a company or open community

  • Run the server in containerized form on a single VM using docker-compose. Use the included whitelist.json and RCON to manage admin access and automate moderation tasks from CI/CD pipelines.

• Testing mods or plugins

  • Use separate folders (data/testing/) and copy server.properties.template to run an isolated instance for plugin compatibility tests. Start with low memory (Xmx) and instrument logs to capture plugin errors.

• Automated backups and CI integration

  • Schedule backup.sh via cron or a Kubernetes CronJob. Store backups in object storage or mount an NFS/volume. Example: backup.sh tars the active world folder and pushes to S3-compatible storage using environment-provided credentials.

• Multi-mode deployment (Survival + Creative)

  • Launch two instances (or a single multiworld-capable server) so moderators can operate a creative build world and a survival progression world independently. Use coordinated RCON scripts to broadcast messages and swap player permissions.

• Production deployment on Kubernetes

  • Use the provided Deployment and Service manifests as a starting point. Ensure persistent volumes for world data, configure resource requests/limits, and expose the service via a LoadBalancer/NodePort on port 25565.

Operational tips

• Always keep regular backups before applying major updates (jar or plugin upgrades).
• Monitor JVM memory and GC behavior; adjust Xmx/Xms to avoid inode/heap pressure on long uptimes.
• Use whitelist and RCON for controlled access during maintenance windows.
• Apply server.properties tuning (view-distance, tick-distance) to match host capacity and expected player concurrency.

This repository provides a practical, deployable baseline for running OpsLevel’s community MCP server with both Survival and Creative experiences. Start with the templates here, then adapt resource limits, plugin choices, and backup destinations to your environment.