Skip to Content
Caura / docs
Integrations

Codex

Connect OpenAI's Codex (CLI and desktop app) to Caura.

Codex supports remote MCP servers with sign-in. Two minutes total.

Connect by signing in

Add Caura without a key:

codex mcp add caura --url https://caura.ai/mcp

Then sign in:

codex mcp login caura

Your browser opens Caura: sign in, choose the tenant Codex works in, and approve. Codex keeps the sign-in and renews it itself; no key is written to your config.

Codex gets its own agent in that tenant, named after you (for example codex-dana), at trust level 1: it reads the team's memories, writes its own, and follows the team's keystone rules. It can't delete other agents' memories or author rules unless an admin raises its trust. On this connection the memory and document tools come split by effect: caura_memory_read, caura_memory_update and caura_memory_delete, and caura_doc_read, caura_doc_write and caura_doc_delete.

The connection appears in Connect › Keys as "OAuth: Codex"; revoke it there to disconnect. Changing or resetting your password also ends it, and Codex asks you to sign in again (codex mcp login caura).

Connect with a key

To use an mc_ key instead (from Connect › Get started), put it in an environment variable and point Codex's config at it, in ~/.codex/config.toml:

[mcp_servers.caura]
url = "https://caura.ai/mcp/"
bearer_token_env_var = "CAURA_API_KEY"

Codex sends the key as Authorization: Bearer, which the MCP server accepts as it does X-API-Key. For a fleet of agents, give each its own agent-scoped key: see Per-agent keys.

Using it

Just ask:

What did we decide about the billing schema?

Remember that this repo deploys with make release, not npm publish.

Codex lists the caura_* tools under /mcp.