Add the Scoped Cloud MCP endpoint
In a Codex environment with MCP support, add the public Scoped Cloud endpoint and then start the login:
codex mcp add scoped --url https://app.scoped.ai/mcpcodex mcp login scopedFor a local or operator-run Scoped deployment, replace the public origin with that deployment’s application origin and keep the /mcp path. Do not send a production credential to a different origin.
Sign in, select one workspace, and approve scopes
Codex starts the OAuth flow and Scoped opens the authorization step. The person connecting signs in, chooses a workspace they can access, and reviews the requested permissions. Registration alone grants no project access; the signed consent creates the workspace-bound grant.
The token carries the authorizing person’s identity and cannot be retargeted by switching the browser to another workspace. Connect and approve the second workspace separately if the work genuinely needs it.
Codex works through the tools allowed by its grant
Depending on approved scopes, Codex can search work, retrieve issue or resume context, update permitted fields, and add comments. Scoped checks the required scope when each call arrives and exposes only the tools the grant can use.
A write becomes part of the same project record people use in Scoped. MCP activity keeps the authorizing person and the Codex connection source. See the concrete handoff-comment example before using write access on consequential work.
Scoped does not run the Codex session
Codex continues to run in its own environment. Scoped does not choose its model, write its prompt, start a run, or authorize tools outside Scoped. The MCP grant covers only the selected Scoped workspace, resource, and approved scopes.
Inspect or revoke the connection in Scoped when it should no longer have access. Revocation stops future use of that grant but preserves accepted project changes and their activity record. Read the full agent execution boundary and shared MCP model, or return to the integration index.
Questions about connecting Codex
What Scoped URL should I add to Codex?+
Use https://app.scoped.ai/mcp for Scoped Cloud. A local or operator-run Scoped deployment uses its own application origin followed by /mcp.
Who approves Codex access to a Scoped workspace?+
The person connecting Codex signs in through Scoped, chooses an accessible workspace, and approves the requested permissions. The resulting grant remains tied to that person and workspace.
Does Codex run inside Scoped after it is connected?+
No. Codex continues to run in its own environment. The connection lets it read or update permitted Scoped records; Scoped does not start, host, or supervise the Codex session.
Need a workspace first? Create one in Scoped Cloud.