Use Orca from Claude Code

​

Route 1: the Orca plugin (recommended)

claude plugin marketplace add okikorg/orca-cli
claude plugin install orca@orca

​

Route 2: MCP server only

claude mcp add orca -- orca mcp serve

​

First run

1. orca doctor --json to check the install, then curl -fsSL https://orcapods.ai/install.sh | sh if the CLI is missing.
2. orca login: in an agent context this automatically uses the device flow. Claude relays a one-time code and a URL; you open the URL on any device, check the code matches, and approve. The CLI picks up its key by polling; no key ever passes through the chat.
3. whoami, create_agent, run_agent, wait_for_run over MCP (or the --json CLI equivalents) to do the work.

​

A worked transcript

user: run my support-triage agent against the new tickets and summarize

claude: [tool: whoami] returns tenant acme, role member
claude: [tool: run_agent {agent: "support-triage", prompt: "..."}]
        returns {runId: "run_7f2", sessionId: "sess_9a1"}
claude: [tool: wait_for_run {runId: "run_7f2", timeoutSeconds: 120}]
        returns {status: "ok", done: true, events: [...]}
claude: The agent processed 14 tickets: 3 urgent (billing), 9 routine, 2 spam. ...

​

Notes

• The MCP server resolves credentials lazily (ORCA_API_KEY, then the API key stored in the selected CLI context; there is no CLI flag that supplies the key itself, --context only selects which stored context to use), so registering it before the first login is fine; tools answer with the exact fix until you sign in.
• Everything not covered by a dedicated tool is reachable through the api_request tool, documented by the live spec at the orca://openapi resource.
• Headless auth details, including CI: Headless authentication.

​

Next