Skip to main content

Braze

Braze's official MCP server lets agents work in Braze as the signed-in Braze user: read campaigns, Canvases, segments and analytics, manage templates, Content Blocks, catalogs and media, export and update users, and — unlike the REST API — create, edit, stop and archive campaigns and use BrazeAI Operator. Braze hosts it at https://mcp.braze.com/mcp (US) or https://mcp.braze.eu/mcp (EU); either endpoint reaches any Braze cluster. It uses OAuth, so each person signs in with their own Braze account.

It is in the Willow catalog as the Braze card with the Official badge. Willow also has a built-in Braze connector, which calls Braze's REST API with a shared key.

Official server or built-in connector​

The two expose different tools and sign in differently. You can add both.

Official MCP serverBuilt-in connector
ToolsFull Braze MCP toolset, including creating, editing, stopping and archiving campaigns, and Operator~50 REST tools; no campaign or segment create/edit, no Operator
Braze identityEach user's own Braze account (OAuth)One shared REST API key
Auth in WillowOAuth sign-in (per-user)API key (shared)
PermissionsEach user's own Braze dashboard permissionsWhatever the API key was given

Use the official server when people should act with their own Braze permissions, or need campaign editing or Operator. Use the built-in connector for shared, key-scoped REST access, such as read-only reporting from a signed-out context.

Before you start​

  • A paid Braze account. The MCP server is not available on free trial accounts.
  • A Braze company admin to enable MCP OAuth, approve Willow, and grant access.
  • The "Use MCP Server" permission for every person who connects. It is off by default. An agent's access mirrors that user's Braze dashboard permissions.
  • Your endpoint: https://mcp.braze.com/mcp (US) or https://mcp.braze.eu/mcp (EU).

See Braze's Set up the Braze MCP server for the authoritative prerequisites.

Set up Braze​

A Braze company admin does this once.

1. Turn on MCP OAuth​

In Braze, go to Settings → Admin Settings → External Connections and enable MCP OAuth access. See Manage OAuth settings.

2. Approve Willow​

In Settings → Admin Settings → External Connections → MCP Clients, either approve a verified client by name, or add Willow's redirect URI to the approved list. Willow shows the exact redirect URI on the server's Setup tab when you add it (see below) — copy it from there, since Braze requires an exact match.

  • For SaaS deployments it looks like https://{org}.withwillow.ai/{org}/api/auth/callback.
  • For on-premise deployments it is {connectUrl}/{org}/api/auth/callback.

3. Grant "Use MCP Server"​

Give the "Use MCP Server" permission to the people who should connect. To revoke a person's access, remove the permission; to cut off everyone at once (for example a leaked token), revoke all MCP OAuth tokens in External Connections. OAuth connections are recorded in Braze's security event report.

Set up Willow​

1. Add the server​

  1. Go to MCP Servers → + Add MCP server, find the Braze card with the Official badge, and click + Use.
  2. Under Authentication, keep OAuth sign-in. Willow registers its own OAuth client, so you don't paste a client ID or secret.
  3. Copy the redirect URI shown in the setup step and give it to the Braze admin for step 2 above (unless they approved Willow as a verified MCP client by name).

2. Test and publish​

  1. Click Check connection and sign in with your Braze account.
  2. Sync the tools, assign groups, and Publish.

Everyone else signs in with their own Braze account the first time they use the server.

What agents can do​

The server exposes read and write tools; most map to Braze REST API endpoints, and some are available only through the MCP server. Call get_workspaces first — each workspace id is the app_group_id other tools need.

  • Read: campaigns, Canvases, segments and their analytics; templates and Content Blocks; KPIs, custom events, purchases and sessions; catalogs; user exports.
  • Write: create, edit, stop, archive and duplicate campaigns and their messages and variations; create and edit templates, Content Blocks and catalogs; upload media; update users.
  • Operator and other beta tools, when your account is in the matching beta program.

Each tool respects the signed-in user's Braze permissions. See Braze's available MCP functions for the full list.

Troubleshooting​

"OAuth Discovery Failed" / HTTP 400 on connect​

Cause: Braze rejected Willow's client registration because its redirect URI (or client) is not approved.

Solution: In Braze, approve Willow under External Connections → MCP Clients — approve the verified client, or add the exact redirect URI from Willow's Setup tab. Confirm MCP OAuth is enabled.

HTTP 403 "IP address is not whitelisted"​

Cause: The Braze workspace restricts access by IP, and the MCP call reached Braze from an IP outside the allowlist.

Solution: Use Braze's MCP IP-allowlisting support so MCP calls are allowed, or have a Braze admin adjust the allowlist. This is a Braze-side control; Willow cannot bypass it.

A user can't connect, or a tool returns a permission error​

Cause: The user lacks the "Use MCP Server" permission or the specific Braze permission for that tool, or the account is on a free trial. Operator and other beta tools need the matching beta program.

Solution: Grant the missing permission in Braze, confirm the account is paid, and ask your Braze account manager about beta access if needed.

Additional Resources​