Operator Connect

With Operator Connect, you write the brief in the AI tool you already use—Claude, Cursor, or another MCP client—and BrazeAI Operator^TM builds it in your Braze dashboard.

important

Operator Connect is currently in beta and is available to select customers. Contact your customer success manager to request access.

Before you start

Operator Connect does not use per-step approvals

Operator Connect asks for fewer explicit approvals than BrazeAI Operator in the dashboard. It still respects the permissions of the signed-in dashboard user, so it can only take actions that user is allowed to take in the dashboard. Review those permissions before you use Operator Connect: the agent has that same access.

Operator cannot currently launch campaigns or Canvases.

To limit what Operator can change, create a dedicated Braze user with scoped permissions for Operator Connect. For help setting this up, see Manage company users. This also makes Operator’s changes easier to identify in the dashboard. If your team requires per-step approval, use BrazeAI Operator in the dashboard instead.

Use Operator Connect for agentic, judgment-heavy work

Use it for things like building a campaign from a brief, restructuring a Canvas, or answering a complex question about your workspace. Operator Connect is not the right tool for high-volume, high-frequency programmatic operations. For those workflows, use the Braze REST API.

Prerequisites

Before you use Operator Connect, confirm the following:

Prerequisite	Description
Hosted Braze MCP server	Operator Connect is exposed through the hosted, OAuth-based Braze MCP server only. Customers on the local API-key MCP server must migrate to the remote-hosted server first. See Set up the Braze MCP server.
Operator enabled for your workspace	BrazeAI Operator must be active for your workspace.
Use MCP Server permission	Your dashboard user needs the “Use MCP Server” permission.

Remove and re-add the MCP server after access is enabled

When Braze enables Operator Connect on your account, your existing MCP connection does not automatically pick up the new scope. After Braze confirms your access is enabled, remove and re-add the Braze MCP server in your client. For help, see Troubleshooting.

What you can do with Operator Connect

Operator Connect can take the same actions as BrazeAI Operator in the dashboard, including:

Build and edit campaigns and Canvases
Create and update segments
Draft email, SMS, push, and in-app message copy and templates
Manage Content Blocks
Generate reports and answer questions grounded in your workspace data

For the full list of capabilities, see What you can do with Operator.

How Operator Connect works

Write your prompt in natural language. Your MCP client typically chooses Operator Connect from the brief, without you naming Operator or its tools.

If the client skips Operator Connect for a task Operator can complete, you can add more explicit instructions to use Operator Connect.

When you send a prompt, your client submits it to Operator and retrieves the result automatically. Three tools on the hosted Braze MCP server handle this:

ask_operator — Submits a natural-language prompt and returns a job ID. Operator runs the job asynchronously.
get_operator_result — Retrieves the result for a given job ID.
cancel_operator_job — Stops a running job.

Example prompts

Start with a natural-language brief. Here are a few examples:

Build a three-step welcome Canvas for new loyalty members—email on day 1, push on day 3, and an in-app message on day 7. Save it as a draft in the Production workspace.

Review the Subject Line and Preheader of the 'Summer Sale Email' campaign in the Production workspace and suggest improvements for better open rates.

Create a segment for users who have made a purchase in the last 30 days but haven't opened a push notification in the last 14 days.

What were our top five email campaigns by click rate last quarter? Summarize the key differences between them.

What to expect

Operator Connect works differently from a synchronous API call. Here’s what to plan for.

Async responses

Responses take a few minutes, not seconds. Operator Connect runs each job as a full agentic session—roughly as long as doing the equivalent work in the dashboard. Set expectations accordingly if you’re sharing Operator Connect outputs with other people or downstream systems. If you’re building a custom agent that calls these tools directly, design it to poll get_operator_result rather than expecting an immediate response. Responses return as text with no structured output format.

No observability view

There is no dedicated dashboard UI, session log, or observability view for Operator Connect usage in this beta. Actions taken by Operator appear in the dashboard under normal attribution for the acting dashboard user.

Authentication and permissions

Operator Connect uses the same sign-in as the Braze MCP server—your normal Braze credentials, with no separate login. Operator Connect ties access to your dashboard user account, not a shared API key. This means:

Operator acts with that user’s exact dashboard permissions. It cannot perform actions the user could not perform directly.
The dashboard attributes all changes to the signed-in user. For easier auditing, use a dedicated Braze account for Operator Connect. See Before you start.
When a user loses access to Braze, they also lose access to Operator Connect.

Pricing

For the beta, Operator Connect usage counts against the same company-wide daily Operator cost cap as dashboard usage. Because programmatic use typically consumes more than interactive use, beta participants receive a temporarily raised daily cap for the duration of the program.

The raised cap applies only for the duration of the beta program and is subject to change.
Braze cannot guarantee you stay within the cap. If you hit it, contact your customer success manager.

Operator Connect is expected to be a paid feature at general availability. Participation in the beta is free, but does not reflect future pricing.

Data privacy and security

Operator Connect follows the same privacy and security model as BrazeAI Operator^TM, including the same data processor relationships. For more information, see Data privacy and security for BrazeAI Operator.

Troubleshooting

Operator tools do not appear after access is enabled

When Braze enables Operator Connect on your account, your existing MCP client connection may not automatically pick up the updated access permissions. If you submit a prompt and receive an authentication error, or if the Operator tools do not appear in your client:

In your MCP client, remove the Braze MCP server connection.
Re-add the Braze MCP server using your endpoint URL (https://mcp.braze.com/mcp for US, https://mcp.braze.eu/mcp for EU).
Complete the OAuth sign-in flow again.

After re-adding, your client registers with the updated access permissions, including Operator Connect. If the issue continues, contact your customer success manager.

Next steps

Set up the Braze MCP server (prerequisite for Operator Connect)
BrazeAI Operator
What you can do with Operator

New Stuff!