SEC.01
The playbook
The run starts read-only: the recon probes decide what happens next. The steps that follow are adapted to the distribution and state found — a real machine is rarely clean.
- 01reconJava already present? version compatible with the Minecraft version?
- 02recondoes a dedicated user already exist?
- 03reconis the server port free?
- 04recondoes a server already exist at this location? do not overwrite a world
- 05actInstall Java (headless JRE)verify
- 06actCreate the user and the folderverify
- 07actDownload the server (${flavor} ${mc_version})verify
- 08actAccept the EULA + server.propertiesverify
- 09actsystemd service + startupverify
- 10actThe server is listeningverify
SEC.02
What it verifies
Each step ships its own check. The run only moves on when the check passes, so what the recipe reports as done is what is actually on the server.
- 01verifyInstall Java (headless JRE)Verified by
java -version 2>&1 - 02verifyCreate the user and the folderVerified by
id minecraft && test -d /opt/minecraft && echo ok - 03verifyDownload the server (${flavor} ${mc_version})Verified by
test -f /opt/minecraft/server.jar && echo ok - 04verifyAccept the EULA + server.propertiesVerified by
grep -q eula=true /opt/minecraft/eula.txt && echo ok - 05verifysystemd service + startupVerified by
systemctl is-active minecraft - 06verifyThe server is listeningVerified by
ss -tlnH "sport = :${port}" | grep -c LISTEN
SEC.03
Variables
What you choose before launching — the recipe fills in the rest.
| Name | Meaning |
|---|---|
| ${mc_version} | Minecraft version |
| ${flavor} | Server type |
| ${max_players} | Max players |
| ${ram_mb} | RAM (MB) |
| ${port} | Port |
| ${difficulty} | Difficulty |
SEC.04
How a recipe runs in Servor
Servor is zero-knowledge: the platform cannot execute anything on its own. When you launch this recipe, a run reads the reconnaissance, plans the steps and asks for your approval. Each approved command is signed by your browser — with a key the server never sees — then relayed verbatim to the agent, which verifies the signature locally before executing.
search by intent — type “firewall”, get ufw
- 01Read-only reconnaissance before any change
- 02Every command signed by your browser, approved by you
- 03Each step verified before the run moves on, every run kept in the history
SEC.05
More game servers recipes
- 01Valheim ServerDedicated Valheim game server via Docker.
- 02Factorio ServerDedicated Factorio game server via Docker.
- 03Mumble ServerMumble (murmur) voice server, started and verified.
- 04Minecraft Bedrock ServerDedicated Minecraft Bedrock server via Docker.
- 05Terraria ServerDedicated Terraria (TShock) game server via Docker.
Verified recipe
Run this recipe on your server
Connect a server, launch the recipe, and approve each step as Servor executes and verifies it. Free plan, no card required.