Braze MCP Server Integration
What Braze's remote MCP server offers, how access works, and the approval rules we propose before any write tool is switched on.
Lifecycle teams want to ask an AI client how a campaign performed, which segments exist or what a Canvas does, and sometimes to make changes. Braze runs its own MCP server for this. It belongs to Braze; GeekMidst helps you set it up, decide which tools to allow and put approval rules around writes. This page summarises Braze's documentation and our proposed controls.
The official Braze MCP server
- Status: generally available, per a Braze article dated 23 July 2026.
- Endpoints: remote, at
https://mcp.braze.com/mcp(US) andhttps://mcp.braze.eu/mcp(EU); either can reach any cluster. - Data: read and write tools. Tools that expose user-level PII are not available.
- Authentication: OAuth with the user's Braze dashboard login, with SSO and SAML supported and no API key needed. An admin enables MCP OAuth access, approves client redirect URIs and grants the "Use MCP Server" permission, which is off by default.
- Verified clients: Claude, ChatGPT, Cursor, OpenAI Codex, Claude Code and VS Code. Braze allowlists client domains.
- Limitation: MCP cannot be used if IP Allowlisting is enabled on the account.
- Legacy local server: released in August 2025 and labelled beta, it is now deprecated and gets no further updates. It needed a dedicated read-only API key. Plan to move off it.
What the tools cover
Braze MCP tools by group, per Braze's documentation
| Group | Examples | Read/write | Status |
|---|---|---|---|
| Analytics and catalogue reads | Campaigns, Canvases, segments, KPIs (DAU, MAU, new users, uninstalls), events, purchases, sends, sessions, custom attributes, templates, content blocks, catalogs, CDI integrations | Read | Part of the GA server |
| Non-beta writes | duplicate_campaign; catalog create, edit and delete; create_media_library_asset; email template and content block create and update; trigger_integration_sync | Write | Part of the GA server |
| Beta writes | Create, edit, launch, stop and archive campaigns and messages; create and edit segments | Write | Beta, needs beta programme enrolment |
| Operator tools | send_operator_prompt, get_operator_result, cancel_operator_job | Write | Beta |
| Canvas | List, details, data series and summary | Read only | Canvas tools are read-only |
Campaign edits are attributed to the signed-in user in edit history. Braze also notes that it sees tool calls but not the user's prompts, and it advises against client "auto-mode".
Proposed approval rules for write tools
Braze's server applies the user's dashboard permissions. Our proposed rules add a confirmation step in the MCP host, so no write runs on a model's decision alone. This is a proposed design; we validate the APIs, edition and permissions for each implementation.
Proposed tool policy
| Tool | Purpose | Read/write | Approval needed |
|---|---|---|---|
| Campaign, Canvas and segment reads | Performance questions and documentation | Read | No |
| KPI and event reads | Trend questions | Read | No |
| duplicate_campaign | Start a variant from a known campaign | Write | Yes, campaign owner |
| Template and content block create or update | Draft content changes | Write | Yes, content owner plus brand review |
| Catalog create or edit | Update product or offer data | Write | Yes, catalogue owner |
| Catalog delete | Remove a catalog | Write, destructive | Not enabled in the first phase |
| trigger_integration_sync | Start a CDI sync | Write | Yes, data owner |
| Beta launch, stop or archive | Change live messaging | Write | Not enabled until a separate review |
| Operator tools | Hand work to BrazeAI Operator | Write | Not enabled until a separate review |
Authentication and access control
Grant the "Use MCP Server" permission only to a pilot group, approve only the redirect URIs of clients you use, and keep each user's dashboard role as narrow as their job. Admins can revoke all MCP tokens, which belongs in your incident runbook. Never share a Braze login with an AI client set up for someone else.
Where a custom adapter might help
We only propose a GeekMidst adapter for real gaps, and none exists today. Examples: one tool that joins Salesforce account context with Braze campaign results, or a tighter tool list than your MCP host can enforce. For accounts that require IP Allowlisting, we would check with you whether a server-side integration calling Braze's REST API from an allowlisted address meets your security policy; that is a design question, not a feature of the MCP server. Cross-platform patterns are in Salesforce and Braze architecture.
Privacy, limits and auditability
User-level PII tools are not available on the server, but campaign names and content can still be sensitive; agree what may be discussed with an AI client and check with your legal adviser on the rules that apply to you. Braze's documentation, as summarised in our sources, states no MCP rate limits, so check Braze's limits. OAuth connections are logged to Braze's security event report, and edits appear in edit history under the user's name.
Errors, environments and testing
Test in a non-production Braze workspace where you have one, with a pilot user whose permissions you know. Check that a user without "Use MCP Server" is refused, that write tools wait for confirmation, and that failed calls report the reason.
Available today vs proposed
| Item | Status |
|---|---|
| Braze MCP server (remote) | Generally available per Braze, 23 Jul 2026 |
| Beta write and Operator tools | Beta, enrolment required |
| Legacy local Braze MCP server | Deprecated |
| GeekMidst approval rules and adapter | Proposed design |
Related
Braze consulting
Braze strategy, set-up and governance
→Braze implementation
Workspace, data and channel set-up
→Salesforce Braze integration
Connecting CRM data and Braze
→MCP security and governance
Our checklist for MCP access
→MCP integration overview
All vendor servers and their status
→Questions we hear
Does Braze have an official MCP server?
Do we need an API key?
Can the AI launch a campaign?
Why can't we connect?
Sources
Set up Braze MCP with clear rules
Tell us which teams want to use Braze through an AI client. We can plan permissions, allowed tools and approvals with you.
