Skip to main content
The Codex CLI, the IDE extension and the desktop app share one configuration, ~/.codex/config.toml, so setting AdLoop up once covers all three (checked 2026-10-10). Codex in ChatGPT on the web doesn’t read that file; it uses plugins instead, see ChatGPT.

​
Sign in with AdLoop (OAuth)

Codex detects that AdLoop supports OAuth and starts the sign-in straight away: your browser opens AdLoop’s consent page, you choose Allow access, and the browser hands the token back to Codex. If it expires or you want to switch workspaces later:

​
API key

Keep the key in an environment variable rather than in the config file:
That writes this to ~/.codex/config.toml, which you can also edit by hand:
Codex sends the variable’s value as Authorization: Bearer …. A key can be restricted to read-only, single clients or chosen toolsets.

​
IDE extension

In the Codex panel: gear menu → MCP servers → Add server, choose Streamable HTTP, enter https://mcp.getadloop.com/mcp, save and restart the extension. Click Authenticate next to AdLoop to sign in. A server you added with the CLI shows up here too.

​
Verify

Or type /mcp in a Codex session. Then ask: “Run the AdLoop health check.”

​
Notes

  • AdLoop answers some reports in more than ten seconds. If Codex gives up on long calls, raise tool_timeout_sec under [mcp_servers.adloop] (default 60).
  • Every write goes through the preview and confirm flow, so an agent running unattended can’t apply a change without you.
Your AI can read these docs too. Add https://docs.getadloop.com/mcp as an additional MCP server and your assistant can search this documentation while it works: setup answers, troubleshooting, and tool guidance on demand.