Skip to content

OAuth and MCP access in a workspace

Company-wide OAuth policy is configured in Admin settings. In a workspace, you grant individual users permission to use the MCP server.

What’s company-wide versus per-workspace

Control Company-wide Per workspace
MCP OAuth access Yes. This toggle is in Settings > Admin Settings > External Connections under Global access controls. No. Workspace admins can’t override the company setting.
MCP Clients page Yes. Approving or removing a verified client applies to every workspace. No.
Approved redirect URIs Yes. Approved and blocked URIs apply to every workspace. No.
Revoke MCP OAuth tokens Yes. Revocation invalidates every MCP OAuth token in every workspace. No. Workspace admins can’t revoke tokens for one workspace.
“Use MCP Server” permission No. Yes. Grant this permission for each workspace the user should access through the MCP server.
Dashboard permissions mirrored by MCP No. Yes. The MCP client can use only the Braze features the user can already access in that workspace.

If MCP OAuth access is off for the company

When MCP OAuth access is off, Braze denies MCP OAuth for every workspace. You can’t turn MCP OAuth access on or off for one workspace, and you can’t maintain a separate MCP client or redirect URI allowlist per workspace. Users with the “Use MCP Server” permission still can’t connect, and there is no workspace-level setting to turn MCP OAuth access back on.

Users who try to connect may see a message that remote MCP access hasn’t been turned on for the company. A company admin can turn on MCP OAuth access in Settings > Admin Settings > External Connections.

Redirect URI records remain on the company External Connections page so you can keep or update the allowlist while MCP OAuth access is off.

For information about company-level MCP OAuth access, the MCP Clients tab, redirect URIs, token revocation, and who can change those settings, see Manage OAuth settings.

New Stuff!