Last updated Oct 8, 2026
MCP
MCP configuration for connecting Brev to Claude, Cursor, and other MCP clients.
MCP is a per-user entry in the Settings → AI & agents sidebar group (it was 'AI & automation' under Account until the September 2026 settings redesign), split out of Profile. The page route is /settings/mcp.
MCP server #
The page opens with the MCP switch: 'Allow external MCP clients (Claude, Cursor, and others) to access your Brev workspace.' It is on by default and it is yours alone: it covers the clients you connected, not anyone else's. Turning it off asks you to confirm in Turn off MCP access?, because every client you have already connected stops working at once (most clients report it as being unable to reach the server). Turning it back on needs no confirmation. It does not affect the Brev Operator inside the product, which is not an MCP client you connected and keeps working with the switch off.
Below the switch is the Brev MCP server URL (https://mcp.brev.io/mcp in production), with a Copy button. Everyone in your workspace sees the same address: the client's sign-in decides whose workspace it reaches. That bare URL is all modern clients (Claude Cowork, Claude Desktop, Cursor) need, since they wrap it and run the authorization flow themselves. For clients that read a config file (Cursor, Claude Code, Windsurf), 'Using a file-based client? Show .mcp.json' reveals a ready-made .mcp.json snippet with its own Copy button. See MCP authorization for the consent flow that follows.
Was this page helpful?
Related
- Profile
Your profile, Appearance (when dark mode is on for you), Log out and Mock user, plus how to get around Settings, including on a phone. Notifications, MCP, API keys and the CLI each have their own sidebar entry.
- MCP authorization
Landing page in the OAuth flow that connects an MCP-compatible client (Claude Desktop, Cursor, your own) to your Brev workspace.