Codex CLI talks to Orca through the same MCP server the CLI ships.
Setup
Install the CLI and sign in once:
Then register the server in ~/.codex/config.toml:
Notes
- The tool surface is identical across clients: golden-path tools plus the
api_request escape hatch. See The Orca MCP server for the full table.
- In fully headless environments, skip the login flow and export
ORCA_API_KEY before launching Codex; the server picks it up per call. See Headless authentication.
- The
orca CLI itself is also agent-friendly if you prefer shelling out: every command takes --json, streaming commands emit NDJSON, and exit codes are stable (0 ok, 1 failure, 2 usage, 3 auth, 4 not found).
Next
Build it with your coding agent is the same loop from the Codex side: describe the job, create the two files, test them on input built to break them, then change exactly one file and go again. Last modified on September 5, 2026
