Skip to main content
orca mcp serve runs an MCP server on stdio with one tool per CLI action. A coding agent can then list and create agents, start sessions and chat with them, manage skills, vaults, files, and kits, and read usage and your wallet, all as you. It uses the CLI’s own login, read again on every call, so you can add it before you sign in. Sign in first with orca login. Without a key, each tool answers “not logged in to Orca.” and how to log in.

Claude Code

Install the Orca plugin. It adds the use-orca skill and registers the MCP server for you:
Or register only the MCP server:

Cursor

Add the server to ~/.cursor/mcp.json for every project, or .cursor/mcp.json for one:

Codex

Or add it to ~/.codex/config.toml:

The tools

chat sends a message to an agent or session and waits for the reply, by default up to 120 seconds and at most 600. It returns the session ID, whether the turn finished, its status, and the reply, so the coding agent can continue the same session. Commands that only touch your machine (login, logout, context, doctor, update) have no tool. Tools act with your key’s role, so admin-only actions fail for a member.

In practice

Ask your coding agent things like:
  • “Create an Orca agent called reviewer on orca/openrouter/openai/gpt-5.6-luna that reviews pull request descriptions.”
  • “Chat with reviewer about this diff and give me its answer.”
  • “How much Orca credit do I have left?”
Treat what the agent does with these tools as you would any command it runs: it can create, delete, and spend on your behalf.