Orca Minecraft CLI

Minecraft work, from your terminal

Give developers and coding agents a predictable command line for Orca. Discover capabilities, inspect local Minecraft instances, launch the game, build assets, and work with servers your account owns.

Installed with Orca Desktop · Windows, macOS, and Linux

terminal
$ orca commands
$ orca instances list --json
$ orca minecraft launch --instance my-pack --dry-run
$ orca minecraft launch --instance my-pack --confirm
$ orca server get-status --server survival --json
One command surface

Built for humans and coding agents

Friendly noun-and-verb commands make common Minecraft workflows readable, scriptable, and easy to inspect before execution.

Discover commands

Run orca commands or orca actions to inspect supported capabilities instead of guessing command names.

Inspect Minecraft instances

List local instances and their installed mods using structured output suitable for scripts and agents.

Install and launch

Install a creation into a selected instance, resolve the launch, then start the matching Minecraft setup.

Create Minecraft assets

Generate item, block, GUI, texture, model, and skin assets for an Orca project.

Manage owned servers

Inspect status, logs, players, files, mods, settings, and power actions through owner-scoped server commands.

Return structured JSON

Use machine-readable results so a coding agent can verify state and continue a multi-step workflow.

How it works

Inspect, preview, then execute

The CLI separates discovery from consequential actions so automation stays predictable.

01

Discover the command

Use orca commands, orca actions, and orca doctor to understand the available local and cloud surfaces.

02

Select the exact target

Name the Minecraft instance or server explicitly. Read-only commands return current state without changing it.

03

Preview and confirm

Use dry-run when available, then confirm the exact consequential action after reviewing its target and arguments.

Permissions and safety

Automation with clear boundaries

The CLI never stores Orca service credentials. Local actions pass through a private desktop handoff; cloud and server actions use authenticated, owner-scoped hosts.

  • Explicit instance and server selectors
  • Dry-run support before consequential actions
  • Single-use authorization for protected server changes
  • No raw access to service credentials
FAQ

Common questions

How do I install the Orca CLI?

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.

Does the Orca CLI control terminal panels or IDE tabs?

No. Orca CLI controls Orca and Minecraft capabilities. Your terminal, IDE, or workspace tool remains responsible for its own panes, tabs, and window layout.

Can a coding agent use the Orca CLI?

Yes. The CLI exposes discoverable commands and structured JSON output so terminal-based agents can inspect capabilities, propose actions, and verify results.

Are CLI and MCP separate implementations?

They are two interfaces over the same canonical capability contracts. This keeps command names, schemas, permission requirements, and core behavior aligned.