> ## Documentation Index
> Fetch the complete documentation index at: https://docs.reechee.io/llms.txt
> Use this file to discover all available pages before exploring further.

# Connect Codex

> Add the Reechee MCP server to the OpenAI Codex CLI.

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 anonymously or with an API key - there's no browser OAuth Connect here (for
that, see [Connect Claude](/mcp/connect-claude)). Use a key for the full toolset.

## Anonymous

```toml theme={null}
[mcp_servers.reechee]
url = "https://mcp.reechee.io/mcp"
```

Or:

```bash theme={null}
codex mcp add reechee --url https://mcp.reechee.io/mcp
```

## With an API key

Codex reads the bearer token from an environment variable:

```toml theme={null}
[mcp_servers.reechee]
url = "https://mcp.reechee.io/mcp"
bearer_token_env_var = "REECHEE_API_KEY"
```

```bash theme={null}
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`:

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

<Warning>
  Don't set both `bearer_token_env_var` and an `Authorization` entry in `http_headers` -
  they collide.
</Warning>

## Try it

Start Codex and ask:

> What are people unhappy about with Zendesk lately?

With a key, Codex can chain the [full toolset](/mcp/overview) - opportunities, watchlist,
and triage.