Skip to content
Custom Connectors

Full read-write Claude connector for Braze

Let Claude draft email content and trigger campaigns in Braze

Stop pulling audience data into spreadsheets and drafting content in the dashboard. Claude reads segment and campaign data, drafts email templates and content blocks, and updates user attributes where the work already lives, while scheduling and sends wait for your approval.

Braze is a customer engagement platform that teams use to run cross-channel messaging across email, push, in-app, and SMS. People want Claude to do more than pull campaign stats: to build segments, draft message variants, and stage campaigns where they already live.

What is a Braze MCP server?

A Braze MCP server is a small hosted service that exposes Braze's data and actions to Claude over the Model Context Protocol, so Claude can campaigns, lists, and audiences inside your own account. We build it as a custom connector with separate read and write tools, and destructive actions stay gated behind your approval.

What can Braze's current connector do today?

Braze ships an official MCP server in Claude's connector directory, but it exposes a fixed, standard set of tools: mostly analytics reads plus a few writes like templates and content blocks. A custom connector wraps the rest of the REST API, so Claude can read segment membership, draft email content as templates and content blocks, schedule and trigger existing campaigns, and update attributes scoped to your workflow.

What does full read-write Braze access unlock?

Full read-write Braze access lets Claude pull segment and campaign data, author email templates and content blocks, schedule and trigger existing API-driven campaigns and Canvases, and update user attributes and custom events once you approve. The content drafting and audience analysis that used to live in spreadsheets and the dashboard happen where the work belongs.

  • List segments and export the users in a segment for analysis
  • Draft email content as a reusable template or content block for review
  • Schedule or trigger a send of an existing dashboard campaign after you approve
  • Update user attributes or custom events through the API
  • Trigger an API-campaign send to a defined audience
  • Export campaign and Canvas performance for analysis

Can Claude work with Braze segments, not just read reports?

Partly. Segments are built in the dashboard, so the Braze API cannot create them. Claude reads segment membership and analytics, helps you draft the filter logic, and updates the user attributes and custom events those filters rely on, scoped to the segment and user endpoints you approve.

Can Claude draft message variants and stage a campaign in Braze?

Claude can draft email content as reusable templates or content blocks, ready for review. It can update user attributes and custom events through the API too. Scheduling or triggering a send of an existing dashboard campaign is a separate, gated action that runs only after you confirm it.

Will Claude send a Braze campaign without my approval?

No. Sending and triggering an existing campaign are gated actions kept apart from drafting content. Claude can prepare email templates and content blocks and update user data freely, but an actual send or schedule only happens once you approve it, so nothing leaves your Braze instance by surprise.

How a Braze connector works

We build a small MCP server that authenticates to Braze with a scoped REST API key restricted to the endpoints the work needs. Read tools (segment and user export, campaign and Canvas data) and write tools (draft, schedule, trigger send) are kept separate, and outbound actions like sending require your confirmation. Claude never has more access than the API key you provision, and we can lock the server to allowlisted IPs against your Braze instance.

Frequently asked questions

Can Claude work with Braze segments, not just read reports?
Partly. Braze segments are built in the dashboard, so the API cannot create them. A custom connector reads segment membership and analytics, helps you draft the filter logic, and updates the user attributes and custom events those filters rely on, scoped to the segment and user endpoints you approve.
Will Claude send a Braze campaign without my approval?
No. Sending and triggering messages are separate, gated write actions. Claude can draft email templates and content blocks, but an actual send or trigger of an existing campaign only happens after you approve it. You decide which steps run automatically and which always require a confirmation.
Does the Braze connector get more access than my API key allows?
No. The connector authenticates with a Braze REST API key you provision, scoped to specific endpoint permissions. It never exceeds what that key grants, and we can restrict the server to allowlisted IPs. Provisioning a narrow key for reads and a separate gated key for writes keeps the surface tight.

Tell us what you run. We'll build the connector.

Pick your tool, choose what Claude should do, and get an instant scope and price. No call required.