Codex CLI
Codex CLI connects to the MCP server over HTTP. It does not use mcp-remote. Both OAuth and API key authentication are supported.
Requirements
- Codex CLI installed and signed in.
- The
codex mcp addcommand with the--urloption. Runcodex mcp add --helpto confirm. Update Codex CLI if the option is missing. - An Ada dashboard account. Available tools depend on your role. See Permissions.
Option 1: OAuth (recommended)
-
Run this command. Replace
acme-corp.ada.supportwith your Ada instance domain: -
Codex CLI detects OAuth support and opens a browser window. Log in with your Ada credentials.
-
If the browser window does not open, run:
-
Run
codex mcp list. Confirm thatadashows OAuth in the Auth column. -
Start a new Codex CLI session to load the tools.
Pass the URL with the --url option. If you omit --url, Codex CLI registers the URL as a local command. The command reports success, but the connection fails.
Option 2: API key
API key authentication uses a token generated from your Ada dashboard. Use it for automated setups or when browser-based login is not available.
Codex CLI reads the key from an environment variable when it starts. The key is not written to the configuration file.
-
Generate an API key from Config > PLATFORM > API keys in your Ada dashboard.
-
Set the API key as an environment variable in the shell that launches Codex CLI:
-
Run this command. Replace
acme-corp.ada.supportwith your Ada instance domain: -
Run
codex mcp list. Confirm thatadashows Bearer token in the Auth column. -
Start a new Codex CLI session to load the tools.
Configuration file
Both commands write to ~/.codex/config.toml. The connection applies to every project. You can also edit the file directly:
For API key authentication, use the /api/mcp URL and add bearer_token_env_var = "ADA_API_KEY".
Next steps
- Try a prompt from the prompt library.
- Review data privacy settings.
- Connect additional AI Agents: see Connecting multiple Agents.