Estratos

Codex

Codex connects to Estratos as a remote MCP server — there's no plugin to install. One command registers the server in Codex's shared configuration, and the OAuth sign-in that follows binds it to your workspace. The same configuration is read by the Codex CLI, the IDE extension, and the desktop app.

Add the server

In a terminal, run:

codex mcp add estratos-memory --url https://estratos.ai/mcp

Copy the exact command for your deployment from the Codex card on Connect › Configure agents.

Codex detects OAuth support and starts the sign-in right away: your browser opens the Estratos consent screen, where you pick which workspace to connect (if you belong to more than one) and click Allow. That's it — new Codex sessions load the memory tools.

To check the connection, run codex mcp list; to re-authenticate later (for example after a token is revoked), run codex mcp login estratos-memory.

Or configure by hand

codex mcp add writes this entry to ~/.codex/config.toml — add it yourself if you prefer editing the file:

[mcp_servers.estratos-memory]
url = "https://estratos.ai/mcp"

Then run codex mcp login estratos-memory to sign in.

Headless or CI? Use an API key

For a non-interactive setup — a build agent, a shared server, a cron job — skip OAuth and authenticate with a workspace API key instead:

  1. A workspace Owner creates a key under API Keys in the sidebar, granting it the memory scopes (memories:read, memories:write, and memories:delete as needed). The key is shown once at creation.
  2. Export it as an environment variable and point Codex at it:
   export ESTRATOS_API_KEY="<your key>"
   codex mcp add estratos-memory --url https://estratos.ai/mcp --bearer-token-env-var ESTRATOS_API_KEY

Codex then sends the key as a Bearer token on every call — no browser step. Note the trade-off: an API key acts as the workspace connection itself rather than as an individual member, it's long-lived, and it can be revoked at any time from the API Keys page. For teammates' day-to-day use, prefer the OAuth sign-in — each person's agent then acts with their own role.

What you get

The six Estratos memory tools — retrieval, recording, hierarchy, and naming — over streamable HTTP. Codex reads the server's built-in tool descriptions; there is no separate skills bundle for Codex.

Rollout

Setup is per user: each teammate runs the add command once and signs in on first use. Because tokens are per person, each member's agent acts with that member's role — a Basic user's writes go through review.

Try it

Once connected, ask Codex things like:

  • "What does my memory hierarchy look like?"
  • "Remember that this client is on the VAT flat-rate scheme, under the VAT service scope."
  • "Pull up everything we know about the Pennine Joinery year-end engagement."

If it doesn't connect

See troubleshooting for reconnecting, token expiry, and testing your connection. For protocol-level details — endpoints, scopes, discovery documents — see the MCP reference.