How to Connect Braze to Cursor via MCP

💡 No install? Use cloud.anythingmcp.com directly. Sign in, click Connectors → Braze, paste your credentials, mint an MCP API key and you're done. No Docker, no git clone, no local server.

Braze + Cursor

Let your AI work with Braze: review campaigns, Canvases and their results, check segments, daily active users and revenue, look up user profiles and subscriptions, record attributes and events, and trigger API campaigns after you confirm.

Prerequisites

See the full setup instructions baked into the connector (visible in the in-app store when you select the connector). The required environment variables for this connector are:

BRAZE_REST_ENDPOINT, BRAZE_REST_API_KEY

Step 1 — Get credentials

1. In Braze open Settings → APIs and Identifiers → API Keys and click Create API Key. A key belongs to one workspace.
2. Name it and tick the permissions the tools need. For reading: campaigns.list, campaigns.details, campaigns.data_series, sends.data_series, canvas.list, canvas.details, canvas.data_summary, segments.list, segments.details, segments.data_series, kpi.dau.data_series, kpi.mau.data_series, kpi.new_users.data_series, kpi.uninstalls.data_series, events.list, events.data_series, purchases.product_list, purchases.quantity_series, purchases.revenue_series, subscription.status.get, subscription.groups.get, users.export.ids. For writing add users.track, campaigns.trigger.send, canvas.trigger.send, and users.delete only if the delete tool will be switched on. A key's permissions cannot be changed later: create a new key instead.
3. Copy the key into BRAZE_REST_API_KEY, without a Bearer prefix.
4. Copy the REST endpoint shown on the same page into BRAZE_REST_ENDPOINT. It depends on your Braze instance and matches your dashboard address: dashboard-01.braze.com uses https://rest.iad-01.braze.com, dashboard-01.braze.eu uses https://rest.fra-01.braze.eu, and so on. US instances run on rest.iad-01 to rest.iad-08 and rest.us-10 (.braze.com), EU instances on rest.fra-01 and rest.fra-02 (.braze.eu), and others on rest.au-01, rest.id-01, rest.jp-01 and rest.kr-01 (.braze.com). A key only works on its own instance.
5. Install the connector. The connection check lists your campaigns, so the key needs campaigns.list.

Who sees what: the key acts for the whole workspace, not for one person. Whoever uses the connector sees what the key can read, including user profiles. Share the MCP server only with people allowed to see that.

What it reads: campaigns and Canvases with their setup, messages and daily results (sends, deliveries, opens, clicks, conversions, revenue), the results of one API-triggered send (kept 14 days), segments with their estimated size (for segments with analytics tracking), daily and monthly active users, new users and uninstalls, custom events, purchases and revenue, user profiles by external id, alias, braze_id, email or phone, and subscription group states. Series cover 1 to 100 days, Canvas summaries 1 to 14.

Confirm first: braze_track_users records attributes, custom events and purchases, up to 75 per call, and can move users into segments and start Canvases, so the AI shows you the changes and waits for your confirmation. braze_send_campaign and braze_send_canvas trigger API campaigns and Canvases that send real messages to real people: the AI shows the campaign or Canvas, the channel and exactly who will receive it, and for a broadcast or more than one recipient it waits for an explicit "yes, send". braze_delete_users is switched off at install.

Limits: most endpoints allow 250,000 requests an hour. Reading user profiles allows 250 calls a minute for workspaces onboarded since August 2024 (2,500 before), the lists of custom events and products share 1,000 an hour, and the send endpoints allow 250 broadcast calls a minute and 10 a minute per audience. Braze answers 429 when a limit is reached.

Common errors: 401 "Invalid API key": the key is wrong or belongs to another instance; check that the REST endpoint matches your dashboard. 403 "Access Denied": the key lacks the permission for this endpoint, so create a key that has it. 400: a parameter is missing or invalid, for example a length out of range or an unknown campaign id. 429: a rate limit is reached; wait and retry once.

The connector does not cover content blocks and templates, catalogs, email lists and hard bounces, scheduled messages, preference centers, SCIM, the user alias and identify endpoints, segment exports to cloud storage or Currents.

Step 2 — Install the adapter

curl -fsSL https://raw.githubusercontent.com/HelpCode-ai/anythingmcp/main/docker-compose.quickstart.yml -o docker-compose.yml
printf 'JWT_SECRET=%s\nENCRYPTION_KEY=%s\n' "$(openssl rand -hex 32)" "$(openssl rand -hex 32)" > .env
docker compose up -d

Step 3 — Add the connector in Cursor

Your server URL: in AnythingMCP, open MCP Servers → the server this connector is on, and copy its URL (https://cloud.anythingmcp.com/mcp/…). Use it wherever this guide shows YOUR_SERVER_ID.

Cursor reads MCP servers from ~/.cursor/mcp.json. Add this entry:

{
  "mcpServers": {
    "anythingmcp": {
      "url": "https://cloud.anythingmcp.com/mcp/YOUR_SERVER_ID",
      "headers": { "X-API-Key": "YOUR_MCP_API_KEY" }
    }
  }
}

1. Create an MCP API key in AnythingMCP under MCP Servers → your server → API keys, and paste it in place of YOUR_MCP_API_KEY.
2. Save the file and restart Cursor.
3. Open Cursor → Settings → MCP and check that anythingmcp is listed and connected.
4. Start chatting: the agent can now call the Braze tools.

Available tools

Example prompts

• "Which campaigns did we send in the last 30 days, and which one had the best open and click rates?"
• "How many users entered our onboarding Canvas last week, and how many converted at each step?"
• "Show me daily active users and new users for the last 60 days."
• "Record the custom event webinar_attended for the user with external_id 4821, and show me what you will write before you do it."

FAQ

Does Cursor support custom MCP servers on the free tier? Yes, MCP is available on Hobby, Pro and Business plans.

Next steps

• Connector landing page
• Connect to Claude
• Connect to ChatGPT