Connect Braze to Claude Code

Let Claude draft email content and trigger campaigns in Braze. From the terminal, inside the sessions where you already work.

Build my connector Talk to us

How do you connect Braze to Claude Code?

Claude Code reaches outside tools through MCP servers. To connect Braze, you add a Braze MCP server: a small hosted service that exposes Braze's data and actions over the Model Context Protocol. With a custom connector we build for you, that is one command in the terminal, then an OAuth sign-in with your own Braze account. No API keys pasted into config files.

claude mcp add --transport http braze https://your-connector-url/mcp

Then run /mcp inside a Claude Code session to sign in. Add it with --scope project and the connector is checked into the repo for your whole team.

What can Claude Code do in Braze once connected?

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

One connector, every Claude surface

The connector we build is a remote MCP server, which is the same standard claude.ai and Claude Desktop use. Add it once and the same Braze access works in Claude Code for you, in claude.ai for the rest of the team, and in Claude Desktop. One build, one set of permissions, one monthly plan covering all of them.

Build it yourself, or have it built?

If you live in the terminal, you can absolutely write your own MCP server against the Braze API. The protocol is open. What you take on is everything around the happy path: OAuth token refresh, hosting, monitoring, keeping up when Braze changes its API and when the MCP spec itself moves, and scoping write actions so an agent can never do more than you intended. We build Braze connectors with separated read and write tools and approval gates on destructive actions, then host and maintain them so they keep working while you work.

Frequently asked questions

Does the same Braze connector work in claude.ai and Claude Code?

Yes. It is one remote MCP server. Claude Code adds it with a single "claude mcp add" command; claude.ai and Claude Desktop add it as a custom connector in Settings. Each person signs in with their own Braze account, so access always matches what that person can already see and do.

Do I need to host or maintain anything myself?

No. The connector runs as a hosted service we operate: we handle uptime, token health, API changes on Braze's side, and MCP spec migrations under the monthly plan. Your side is one command in the terminal and an OAuth sign-in.

Is it safe to give a coding agent write access to Braze?

Write access is scoped, not blanket. Read tools and write tools are separated, destructive actions like deleting or sending are gated behind your explicit approval, and the connector can never exceed the permissions of the Braze account it signs in with. Revoking access is one click in Braze.

More on the Braze connector

Braze connector for claude.ai Iterable + Claude Code Customer.io + Claude Code Brevo + Claude Code

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.

Build my connector Talk to us