01 · Records and state owned
Campaigns, Canvases, segments, custom attributes, aggregated analytics and reports, email templates, content blocks, and media-library assets; user-profile data is excluded.
Braze
Braze
Braze is included for a first-party remote MCP that lets authorized dashboard users inspect non-PII campaign, Canvas, segment, custom-attribute, and analytics data and create selected content from supported AI clients.
Marketing automation, lifecycle & CDPSystem of engagementBYO-UI-ready platform
Concrete capability record
Data, retrieval, actions, identity, and operating limits
A field-by-field summary of what the reviewed first-party references actually support. Publisher update dates and BYO-UI review dates are shown separately below.
02 · Data you can retrieve
Read non-PII campaign and Canvas performance, aggregated analytics, segments, custom attributes, and report context across workspaces the connected dashboard user can access.
03 · Actions and write paths
Create selected non-PII content such as email templates, content blocks, and media-library assets, and perform other exposed changes only when the connected dashboard user's permissions allow them.
04 · Authentication and permissions
The remote service uses Braze account OAuth rather than an API key and mirrors the connected dashboard user's current permissions. One connection can reach authorized workspaces, with workspace context selected per request; permission changes apply on the next request.
05 · Monitoring, approval, and recovery
Do not use automatic action mode. Verify summaries against the Braze dashboard and review every proposed change before execution, because Braze receives the client-generated tool call rather than the user's original natural-language prompt.
06 · Limits and caveats
Remote MCP access is Early Access by request. User-level PII tools are unavailable, IP-allowlisting customers cannot participate, and authentication may be blocked for clients outside Braze's supported-domain allowlist. The old local server remains usable but deprecated and unmaintained.
Agent access
MCP support
Official MCP serverBraze-hosted remote MCP in Early Access; prior local beta deprecatedRemote service in Early Access by request; local beta deprecated and unmaintained
Support: Official MCP server
Read scope: Read non-PII campaign and Canvas analytics, segments, custom attributes, reports, and related workspace context allowed by the dashboard user.
Write scope: Create selected non-PII email templates, content blocks, and media-library assets, with any additional exposed change constrained by current dashboard permissions.
Authentication: OAuth sign-in to the Braze-hosted US or EU MCP endpoint using a Braze dashboard account; no Braze API key is required for remote MCP.
Approval boundary: Show the selected workspace, object identity, intended content or change, and expected effect before every write; require explicit confirmation and avoid client auto-mode.
Protocol does not erase product boundaries.
Confirm the current tool catalog, plan, region, scopes, rate limits, terms, and write behavior before implementation.
Editorial assessment
Access-maturity dimensions
A comparative architecture lens—not a quality score, market ranking, or buying recommendation. Scale: 1–5.
Data access4
Action access4
Event access4
Identity4
Governance4
Agent access3
UI extensibility3
Portability4
Observability3
Documentation4
Proposed customer-shaped experiences
What customers could create on top.
The output could be an export, report, graph, artifact, application, agent, workflow, or downstream feed. These proposals are derived from documented access—not claims that Braze ships them.
Single-platform patterns
- Lifecycle campaign, Canvas, and content operations room
- Lifecycle journey debugger
- Audience activation workbench
- Campaign QA and approval room
Multi-platform compositions
- Braze + CRM or commerce system: lifecycle journey debugger
- Braze + warehouse or CDP + content-production platform: cross-system decision workspace
Evidence and dates
First-party references, with publisher and review dates separated
“Publisher updated” is shown only when the page exposes an update date. “BYO-UI reviewed” records when this research checked the reference. A missing publisher date is reported as missing—not replaced with the review date.
4 recorded sources
MCP / agent-role validationRepresentative source
https://www.braze.com/docs/user_guide/brazeai/mcp_server ↗Official Braze docs say the local beta will continue to work but is no longer supported, while the OAuth-based remote server is forthcoming in Early Access. Profile must not describe the remote server as GA, must…
- Publisher updated
- Not stated by publisher
- BYO-UI reviewed
- Jul 12, 2026
Targeted first-party MCP/agent-role review; broader API inventory retained
APISource inventory
https://www.braze.com/docs/api/home ↗First-party API reference or API overview recorded for this platform.
- Publisher updated
- Not stated by publisher
- BYO-UI reviewed
- Jul 10, 2026
Inventory source: structurally normalized; content was not individually reopened in this pass.
HomepageSource inventory
https://www.braze.com/ ↗First-party product homepage used to confirm product identity and current positioning.
- Publisher updated
- Not stated by publisher
- BYO-UI reviewed
- Jul 10, 2026
Inventory source: structurally normalized; content was not individually reopened in this pass.
Webhooks / extensionsSource inventory
https://www.braze.com/docs/user_guide/channels/webhooks/ ↗First-party webhook, event, SDK, embedded-app, or extension documentation.
- Publisher updated
- Not stated by publisher
- BYO-UI reviewed
- Jul 12, 2026
Full-profile first-party re-verification on 2026-07-12; see the private audit ledger.
Verified fact
Tied to cited first-party evidence reviewed for this profile.
Source inventory
Official links recorded for deeper research but not necessarily reopened endpoint by endpoint.
Editorial assessment
System role, maturity interpretation, and architectural boundary.
Proposed design
Interface patterns and compositions—not vendor product claims.