Codex is the one client that still needs a token. Its browser sign-in for remote servers is not reliable yet, so you create a token in Redreach and paste it into the config. The easiest way is to let Codex do the writing for you.
Step 1: Create a token
In Redreach, go to Account Settings → MCP and scroll to Connected clients & tokens at the bottom of the page, then create a token. Name it something like "Codex on my laptop".
Copy the token straight away. It starts with rr_ and it is only shown once.
Step 2: Let Codex configure itself
Paste this prompt into any Codex session, with your own token swapped in:
Install the Redreach MCP server for me. Add this block to ~/.codex/config.toml,
then confirm it shows up in "codex mcp list":
[mcp_servers.redreach]
url = "https://connect.redreach.ai/mcp"
http_headers = { "Authorization" = "Bearer rr_YOUR_API_KEY" }Codex edits its own config file and confirms the server is registered.
Step 3: Restart and test
Restart Codex so it picks up the new server, then ask:
List my Redreach projects
If your projects come back, you are connected.
Prefer to edit it yourself?
Add this block to ~/.codex/config.toml directly:
[mcp_servers.redreach]
url = "https://connect.redreach.ai/mcp"
http_headers = { "Authorization" = "Bearer rr_YOUR_API_KEY" }Then restart Codex.
Your token sits in a plain text file with this setup, so treat ~/.codex/config.toml the way you would any file holding a password. Never commit it to a repository. If it ends up somewhere public, delete that token in Redreach and create a new one, it takes seconds and costs nothing.
What's next?
→ Next: What you can ask Redreach in your AI assistant for prompts that work.
Something not working? See Fixing a Redreach MCP connection that won't work. With Codex the usual cause is a truncated token or a missing Bearer in front of it.
Powered by