Codex CLI, the Codex IDE extension and the Codex app share MCP configuration. Add the server URL, complete OAuth, and never paste or commit an API key.

If Codex has a persistent writable shell, the default setup at [/start](https://scrollport.com/start) uses the Scrollport CLI. Follow this page when you deliberately want a Codex-scoped Remote MCP connection instead.

## Connect

1. **Add the server**

   Run:

   ```bash
   codex mcp add scrollport --url https://mcp.scrollport.com/ --oauth-resource https://mcp.scrollport.com/
   ```

2. **Start OAuth**

   Run:

   ```bash
   codex mcp login scrollport --scopes discover,inspect,run,wallet,apps
   ```

3. **Sign in and authorize**

   Codex opens Scrollport in the browser. Sign in with Google, then review the connection and separately select **Authorise connection**.

4. **Check and verify**

   Return to Codex and run `codex mcp list`. Start a new Codex task or restart the current Codex surface, then call the free `wallet` tool.

This configuration is available to Codex surfaces using the same user configuration. Project-level `.codex/config.toml` may describe the server when your team intends that, but must never contain a bearer token, authorization code or refresh token. See OpenAI's [Model Context Protocol guide](https://developers.openai.com/codex/mcp) for current configuration locations and OAuth commands.

## Disconnect and revoke

Clear the saved OAuth login with `codex mcp logout scrollport`, then remove or disable the `scrollport` MCP server in Codex configuration.

Then open **Agent access** in Scrollport and revoke the matching **MCP connection**. Revocation affects only that connection and immediately prevents its access token from reaching the five control tools.

Return to the [Remote MCP overview](https://scrollport.com/docs/mcp) for the canonical endpoint and all supported clients.