SERVERS / SERVER SETTINGS

Change server rules by asking

Update gamemode, difficulty, whitelist, gamerules, loader, version, online mode, memory, and power state.

Real example: Validated server configuration

SURVIVALOWNER SCOPED
$ orca server gamerule keepInventory trueRun the example to see the verified result.

Use the protected server surface

The owner-bound CLI controls live servers. Public MCP can list your servers and install finished Orca creations.

CLI
orca server set-gamerule --rule keepInventory --value true
MCP
Public MCP does not expose live settings; use the owner-bound Orca server agent.
manage_server:set_gamemodemanage_server:set_difficultymanage_server:set_whitelistmanage_server:set_gamerulemanage_server:resize_ram

Live setting changes stay in the protected owner-bound server surface.

How Orca makes it

Start with the result you want. Orca handles the Minecraft file structure and verifies the build.

01

Inspect current rules

The agent reads the existing setting instead of assuming it.

02

Validate the change

Unsupported values and dangerous combinations are rejected.

03

Persist and verify

Orca checks that the setting survives the necessary reload or restart.

What you get

The deliverable is Minecraft-ready, not just a concept image or a pasted code sample.

Current value
Validated change
Persistent configuration
Post-change status

Keep building

Combine capabilities into one mod, plugin, world, or server workflow.