Add Scoped with Claude Code’s HTTP transport
Add the public Scoped Cloud endpoint to Claude Code, then begin the login:
claude mcp add --transport http scoped https://app.scoped.ai/mcpclaude mcp login scopedYou can also use /mcp inside a Claude Code session to manage the connection and start sign-in. For a local or operator-run Scoped deployment, use that deployment’s application origin followed by /mcp.
Scoped consent selects the workspace and permissions
The person connecting signs in to Scoped, chooses an accessible workspace, and reviews the scopes Claude Code requests. Dynamic client registration identifies the client, but it grants no project access on its own. Access begins only after explicit consent.
The grant stays bound to the authorizing person, selected workspace, Scoped MCP resource, and approved scopes. Changing the active workspace in a browser does not move that connection.
Claude Code starts from current Scoped work
With read scopes, Claude Code can search projects and issues and retrieve current context. With the corresponding write scope, it can submit permitted changes such as updating an issue or adding a comment. A prompt cannot create a permission the OAuth grant does not contain.
Accepted MCP changes join the project record and activity keeps the authorizing person and Claude Code connection source. Review the authorized MCP update example to see how a handoff note moves from an external client into the shared plan.
Claude Code remains the execution environment
Scoped does not host Claude Code, select its model, schedule its session, or supervise tools it uses outside Scoped. Scoped stores the plan and enforces the MCP boundary; Claude Code runs the agent.
Revoke the connection in Scoped to block future use of its workspace grant. Accepted comments and issue changes remain in the record. Read what Scoped does not run, the shared MCP model, or return to the integration index.
Questions about connecting Claude Code
What transport should Claude Code use for Scoped?+
Use Claude Code’s HTTP transport and point it at https://app.scoped.ai/mcp for Scoped Cloud. A local or operator-run deployment uses its own application origin followed by /mcp.
Does Claude Code receive access to every Scoped workspace?+
No. The OAuth consent flow binds Claude Code to the one workspace selected for that grant and to the permissions approved there. Another workspace requires its own authorization.
Does Scoped run Claude Code?+
No. Claude Code runs outside Scoped. Scoped supplies current project context and accepts permitted MCP actions, while the model, prompt, and external tool execution stay in Claude Code’s environment.
Need a workspace first? Create one in Scoped Cloud.