MINECRAFT WORK,
FROM YOUR TERMINAL
Inspect instances, build assets, launch Minecraft, and manage owned servers through one command surface for humans and coding agents.
orcaclient.com/minecraft-clifunction buildBase(area) { const planner = new Planner() const layout = planner.planBase(area) for (const step of layout) { await builder.place(step) } return verify(area)}$ orca init my-world
Initializing Minecraft project[✓] Scaffolding project...[✓] Configuring agents...Project ready.$ orca agent build --task "build base"
Agent Orca-1.2[✓] Planning[✓] ExecutingTask complete.$ orca run
Starting world...World running on port 25565$
Select a workflow, inspect its command, and run a safe simulation of the response your terminal or coding agent receives.
orca commands[✓] Loaded 42 available actions
minecraft · instances · assets · servers
Run any command with --help for its contract
The CLI and MCP are two surfaces for the same creation and server tools. Open any card for the exact workflow and a working example.
BUILDER HAMMERmade through CLIBuilder Hammer and Shark-Tooth Dagger
orca asset create --project-id demo --kind item --name shark_tooth_dagger --description "shark-tooth dagger"Open capability pageOrca Block and Happiness Ore
orca asset create --project-id demo --kind block --name happiness_ore --description "softly glowing happiness ore"Open capability pageWizard and Samurai skins
orca tool run generate_skin --name storm_wizard --description "storm wizard with a teal cloak"Open capability page
Retexture, custom build, or AI-to-Blockbench
orca tool run generate_model --name village_trex --description "friendly village guardian T-rex"Open capability pageFriendly noun-and-verb commands make common Minecraft workflows readable, scriptable, and easy to inspect before execution.
Run orca commands or orca actions to inspect supported capabilities instead of guessing command names.
List local instances and their installed mods using structured output suitable for scripts and agents.
Install a creation into a selected instance, resolve the launch, then start the matching Minecraft setup.
Generate item, block, GUI, texture, model, and skin assets for an Orca project.
Inspect status, logs, players, files, mods, settings, and power actions through owner-scoped server commands.
Use machine-readable results so a coding agent can verify state and continue a multi-step workflow.
The CLI separates discovery from consequential actions so automation stays predictable.
Use orca commands, orca actions, and orca doctor to understand the available local and cloud surfaces.
Name the Minecraft instance or server explicitly. Read-only commands return current state without changing it.
Use dry-run when available, then confirm the exact consequential action after reviewing its target and arguments.
The CLI never stores Orca service credentials. Local actions pass through a private desktop handoff; cloud and server actions use authenticated, owner-scoped hosts.
Everything you need before opening a terminal.
Install Orca Desktop, which installs and updates the matching command-line tool. The CLI is currently distributed with Orca rather than as a standalone npm package.
No. Orca CLI controls Orca and Minecraft capabilities. Your terminal, IDE, or workspace tool remains responsible for its own panes, tabs, and window layout.
Yes. The CLI exposes discoverable commands and structured JSON output so terminal-based agents can inspect capabilities, propose actions, and verify results.
They are two interfaces over the same canonical capability contracts. This keeps command names, schemas, permission requirements, and core behavior aligned.