Connect your agent to the shared record.
Scoped exposes customers, deals, projects, and issues through an MCP server with OAuth. Your agent keeps running where it runs today; Scoped supplies the context and records the updates you permit.
codex mcp add scoped --url https://app.scoped.ai/mcp codex mcp login scoped
The connection, in four lines
- Endpoint
https://app.scoped.ai/mcpStreamable HTTP. A local or operator-run deployment uses its own origin followed by /mcp.- Authorization
OAuth, one workspace per grantThe person connecting signs in, picks a workspace, and approves the requested permissions.- Attribution
Person and connection sourceAn accepted change records who authorized the connection and the client it came through.- Revocation
Stops future accessRevoking a grant blocks future calls, including refresh. Accepted activity stays in the record.
Named setup paths, maintained and tested.
A client is named here only when Scoped maintains its setup steps. Other clients that support the same MCP and OAuth standards may work; they are not listed without a maintained path.
How the boundary works.
What an agent can read and change, how its changes are recorded, and what Scoped never does.
Put a workspace behind your agent.
Create a free workspace, add a few customers and jobs, then connect your client and ask it something read-only first.