Connect Codex to Scoped

Before you start

You need Codex CLI with MCP support, a Scoped account, and membership in the workspace you intend to authorize. Scoped Cloud requires a verified email. Open Agents in Scoped to confirm the endpoint. A separately operated Connect deployment has its own address.

Add the MCP server

For Scoped Cloud, run these commands in your terminal:

codex mcp add scoped --url https://app.scoped.ai/mcp
codex mcp login scoped

If you use Connect, replace the URL with the endpoint shown by that deployment. If a server named scoped is already configured, inspect its URL before trying to add it again.

Authorize your workspace

1. Complete the browser sign-in opened by Codex.
2. Choose the workspace that contains the work you want to use.
3. Read the requested permissions and approve only if they match your intended use.
4. Return to the terminal and confirm that login completed.

Check the connection

Start a Codex session with the connection available and make a read-only request:

Find the project handoff issue in my Scoped workspace and summarize its current status. Do not change anything.

Use an issue that actually exists in your workspace. Compare the result with Scoped. Then, if desired, explicitly ask for a comment or issue update and check its activity in the app.

Troubleshooting

If the browser flow fails, confirm your email is verified and that the server URL is correct. If Codex has stale authorization, reconnect and select the intended workspace again. A change of workspace in the Scoped browser does not retarget an existing agent connection.

If tools are unavailable, review the approved permissions. If login still fails, send support the error and approximate time, excluding tokens and authorization codes. You can review or revoke access at any time.