Codex

Connect Codex (the CLI, the IDE extension and the ChatGPT desktop app) to Currents with one command and a browser sign-in

Codex connects to the Currents MCP server at https://mcp.currents.dev/mcp. The Codex CLI, the Codex IDE extension and the ChatGPT desktop app read the same configuration, so adding Currents once makes it available in all three.

Add the server

codex mcp add currents --url https://mcp.currents.dev/mcp

This writes an entry to ~/.codex/config.toml:

[mcp_servers.currents]
url = "https://mcp.currents.dev/mcp"

To share the server with everyone working in a repository, put the same table in .codex/config.toml at the repository root instead. Codex reads project configuration from trusted projects only. The file holds no credential: each person signs in as themselves.

Sign in

codex mcp login currents

A browser window opens. Sign in to Currents, choose the organization Codex will work in, and approve the permissions it asks for. See Sign in once for what each screen shows.

Codex renews the connection on its own from then on. To revoke it everywhere, remove it under Account → Connected Applications in Currents.

Check the connection

Run codex mcp list to see the configured servers, or type /mcp inside a codex session to see the active ones. Then ask something only Currents can answer:

Which tests in <project> were flakiest on main this week, and why?

Ask before writes

Every Currents tool says whether it only reads. Have Codex ask you before any tool that does not:

[mcp_servers.currents]
url = "https://mcp.currents.dev/mcp"
default_tools_approval_mode = "writes"

With this, Codex runs the read tools on its own and stops for writes such as currents-delete-run, which permanently deletes a run. enabled_tools and disabled_tools narrow the list further. See the Codex MCP documentation.

Use an API key instead

For a CI job or anywhere no one can complete the browser sign-in, send a Currents API key from an environment variable:

codex mcp add currents --url https://mcp.currents.dev/mcp \
  --bearer-token-env-var CURRENTS_API_KEY

[mcp_servers.currents]
url = "https://mcp.currents.dev/mcp"
bearer_token_env_var = "CURRENTS_API_KEY"

A key acts as the organization, not as a person. See Connect with an API key for what a key can reach and how to revoke it.

Troubleshooting

What you see	What to do
Currents tools fail with 401	Run codex mcp login currents.
The wrong organization's data	Revoke the connection in Currents, run codex mcp login currents again, and choose the other organization.

For other errors, see Troubleshooting.