SCOPED GUIDE
Connect Codex to Scoped
Add the Scoped MCP server to Codex, sign in, choose a workspace, and verify the connection with a read-only request.
Codex CLI; Scoped Cloud and Connect
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 see the address to use.
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 scopedIn Scoped Connect, use the address shown on its Agents page instead. If a server named scoped is already configured, check its address before adding it again.
Authorize your workspace
- Complete the browser sign-in opened by Codex.
- Choose the workspace that contains the work you want to use.
- Read the requested permissions and approve only if they match your intended use.
- 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 address is correct. If Codex’s sign-in has expired, reconnect and choose the intended workspace again. Switching workspaces in your browser doesn’t move an existing connection to the other workspace.
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.