Curated anchor platform in cross-channel customer engagement with material relevance to the Marcom operating stack and a first-party developer surface.
Concrete capability record
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.
Retrieve non-PII campaign, Canvas, segment, custom-attribute and analytics data; with individually granted API-key permissions, create or update selected non-PII content such as media assets, email templates and content blocks
Retrieve non-PII campaign, Canvas, segment, custom-attribute and analytics data; with individually granted API-key permissions, create or update selected non-PII content such as media assets, email templates and content blocks
Braze's first-party MCP/agent surface includes state-changing tools in the documented capability area: Retrieve non-PII campaign, Canvas, segment, custom-attribute and analytics data; with individually granted API-key permissions, create or update selected non-PII content such as media assets, email templates and content blocks. The audit did not enumerate every mutation; verify the current tool catalog and require explicit confirmation for consequential actions.
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 exclude profile PII, and must expose read/write permissions separately.
Profile must not describe the remote server as GA, must exclude profile PII, and must expose read/write permissions separately. 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 exclude profile PII, and must expose read/write permissions separately.
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 exclude profile PII, and must expose read/write permissions separately.
Agent access
Role: provider
Read scope: Retrieve non-PII campaign, Canvas, segment, custom-attribute and analytics data; with individually granted API-key permissions, create or update selected non-PII content such as media assets, email templates and content blocks
Write scope: State-changing tools are present in the documented scope; review the official tool catalog and require confirmation for consequential actions.
Authentication: 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.
Approval boundary: Profile must not describe the remote server as GA, must exclude profile PII, and must expose read/write permissions separately.
Confirm the current tool catalog, plan, region, scopes, rate limits, terms, and write behavior before implementation.
Editorial assessment
A comparative architecture lens—not a quality score, market ranking, or buying recommendation. Scale: 1–5.
Proposed interfaces
These are design proposals derived from documented access—not claims that Braze ships these experiences.
Evidence and dates
“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.
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…
Targeted first-party MCP/agent-role review; broader API inventory retained
First-party MCP documentation or product announcement recorded for this platform.
Inventory source: structurally normalized; content was not individually reopened in this pass.
First-party API reference or API overview recorded for this platform.
Inventory source: structurally normalized; content was not individually reopened in this pass.
First-party webhook, event, SDK, embedded-app, or extension documentation.
Inventory source: structurally normalized; content was not individually reopened in this pass.
First-party product homepage used to confirm product identity and current positioning.
Inventory source: structurally normalized; content was not individually reopened in this pass.
Tied to the representative first-party source or targeted access review.
Official links recorded for deeper research but not necessarily reopened endpoint by endpoint.
System role, maturity interpretation, and architectural boundary.
Interface patterns and compositions—not vendor product claims.