MCP authorization

MCP is the protocol Claude Desktop, Cursor, and other AI clients use to talk to external tools. Brev's MCP server exposes your goals, KPIs, teams, cadences, check-ins, and actions as tools the client can read and write, scoped to your account, gated by the OAuth flow that lands here.

Where the client config lives #

The Brev MCP server URL, with a Copy button, is shown in MCP settings. Paste that URL straight into a GUI client (Claude Cowork, Claude Desktop, Cursor) and authorize when prompted. For clients that read a config file, expand 'Using a file-based client?' to copy the wrapped .mcp.json instead. They read:

https://mcp.brev.io/mcp

What you'll actually see during a real install #

When your client sends you here, sign in to Brev if asked and you land back on this page. It shows a card titled Connect <client> to Brev:

• The client's name and icon, and the Brev organization it wants to work with. Brev shows the Claude mark for Claude and the OpenAI mark for ChatGPT when it can confirm the app from where it sends you back, and a plug icon for any other client.
• What the client will be able to do. See your work in Brev covers goals, check-ins, teams, tags, and billing details; Make updates for you covers creating or editing goals, check-ins, teams, and tags.
• Approve and Cancel. Click Approve only if you started this flow yourself. Cancel (or the close button) sends you back to the client without connecting.

Check-ins a connected client writes show where they came from in the goal's check-in history: "via Claude" or "via ChatGPT" when Brev can confirm the app from its connection, otherwise "via MCP".

If the client asks for a permission this version of Brev can't describe, the card lists it as Unrecognized permission, says why, and Approve stays disabled. Cancel and start the connection again from your client, or contact support if it keeps happening.

If the card says Authorization expired, the request is no longer valid (it timed out or the link was changed). Start the connection again from your client.

If MCP access is turned off #

If the MCP switch in MCP settings is off, the consent card says so and the button reads Enable MCP & Approve: approving turns MCP back on for your account as part of connecting. Cancel instead if that isn't what you want; nothing changes. When the card also shows an Unrecognized permission, that warning takes its place and you can't approve.

Disconnecting a client #

Brev doesn't list your connected MCP clients, so there is no per-client disconnect inside Brev. To stop one client, remove the Brev connector in that client's own connector settings. To cut off every MCP client at once, turn off the MCP switch in MCP settings. That is a switch, not a revoke: turning it back on lets the clients you already connected reach Brev again.