Connect Codex

Codex speaks remote Streamable HTTP natively. Configure it in ~/.codex/config.toml (or a project’s .codex/config.toml), or with codex mcp add. Codex connects with an API key - there’s no browser OAuth Connect here (for that, see Connect Claude). Create a key under Settings → API keys in the app; every plan has them, starting with pay-as-you-go (start free, no card needed). A call without a key is refused with 401.

With an API key

Codex reads the bearer token from an environment variable:

[mcp_servers.reechee]
url = "https://mcp.reechee.io/mcp"
bearer_token_env_var = "REECHEE_API_KEY"

export REECHEE_API_KEY=rch_live_YOUR_KEY
# or: codex mcp add reechee --url https://mcp.reechee.io/mcp --bearer-token-env-var REECHEE_API_KEY

Codex sends it as Authorization: Bearer <value>. To inline a literal header instead, use http_headers:

[mcp_servers.reechee]
url = "https://mcp.reechee.io/mcp"
http_headers = { "Authorization" = "Bearer rch_live_YOUR_KEY" }

Don’t set both bearer_token_env_var and an Authorization entry in http_headers - they collide.

Try it

Start Codex and ask:

What are people unhappy about with Zendesk lately?

Codex can then chain the full toolset - opportunities, watchlist, and triage.

Get started

MCP

Guides

With an API key

Try it

​With an API key

​Try it

With an API key

Try it