mcpField
D
dockerized-mcpaper-server

dockerized-mcpaper-server

Local
github.com/LeoMaininiGames & Entertainment0Updated 44w ago
Repository

About dockerized-mcpaper-server

A Docker Compose setup for creating a reproducible, portable Minecraft server, configured primarily for PaperMC. It is intended for server operators who want to set core settings in a compose file and persist server data in a mounted folder.

Key features

  1. 01Docker-based Minecraft server
  2. 02PaperMC-oriented configuration
  3. 03Compose-based startup and shutdown
  4. 04Persistent server data
  5. 05Configurable port and RAM

Use cases

  1. 01Running a PaperMC server in a container
  2. 02Setting server options through Docker Compose
  3. 03Keeping server files across container rebuilds
#docker#server#microservices#mcpaper

Configuration

Local server config is the same for every client. Copy it into your client’s MCP config file.

mcp.json · Universal config
{
  "mcpServers": {
    "dockerized-mcpaper-server": {
      "command": "docker",
      "args": [
        "run",
        "-i",
        "--rm",
        "compose"
      ]
    }
  }
}
Run commanddocker run -i --rm compose

Local servers need a runtime on your machine (e.g. Node.js 18+). Config file locations differ by client; see your client’s docs.

Packages
ocicompose

Tools

No tool list yet

Local servers expose tools only once running on your machine, and the maintainer has not provided a tool list.

Details

From the project README

Containerized Minecraft server 🐋🧱

This project automates creating a Minecraft server using a simple, reproducible, and transportable Docker container.

The configuration was built around the requirements for the PaperMC server software. Another runnable type can be used, but YMMV.

Requirements

Docker Engine
PaperMC server download URL

How-to

The docker-compose.yml leaves some configuration to the end user. The only required inputs are:

  • OUT_PORT
  • SERVER_JAR_URL
  • DEDICATED_RAM

All other inputs are optional and are only present as a simple way to edit values without diving into the server.properties file.

  1. Set the URL, output port, and dedicated RAM in docker-compose.yaml

  2. Start the server with docker compose up -d from the base folder

    • To attach to the server console, run docker attach <container_name>
    • To detach, press CTRL+P+Q inside the terminal window

  3. Stop the server with docker compose down

Nice to knows

Persist more folders from container

The persistent data for the server will be mounted in ./volumes/server. Any data inside the server runnable folder will be persisted.

If other folders need to be persisted, add another entry to the volumes section in docker-compose.yaml, like so:

- type: bind
  source: <HOST PATH>
  target: <PATH IN CONTAINER>

Example for world backups:

- type: bind
  source: /volume/backups
  target: /world_backups
Rebuild image with changes to Dockerfile

If there are changes in the Dockerfile, dependencies, Java version, etc., the image needs to be rebuilt for them to take effect:

docker compose up --build

Any data being persisted will not be deleted when rebuilding the image, for this you must manually delete the persisted folders.

Comments

Markdown supported

New to MCP?

From what the protocol is to installing your first server, these answers cover most first questions.

An open protocol that defines how AI applications connect to external tools and data in a uniform way. Clients talk to the model; MCP servers provide tools, resources and prompt templates. They exchange standard messages, so one server can be reused by many clients.