MCP Braze
Click on "Install Server".
Wait a few minutes for the server to deploy. Once ready, it will show a "Started" state.
In the chat, type
@followed by the MCP server name and your instructions, e.g., "@MCP Brazelist my campaigns"
That's it! The server will respond to your query, and you can continue using it as needed.
Here is a step-by-step guide with screenshots.
MCP Braze
Production-ready MCP server for Braze customer engagement
Built with the MCP SDK — Works with Claude Desktop & Claude.ai
Overview
A comprehensive MCP server enabling AI assistants to interact with Braze's customer engagement platform. Features 92 tools covering user management, messaging, campaigns, analytics, email/SMS operations, catalogs, and SCIM provisioning—built for production reliability.
Related MCP server: GHL MCP Server
Δ Capabilities
Core
92 Tools — Users, messaging, campaigns, analytics Multi-Channel — Push, email, SMS, in-app, webhooks Header Auth — Multi-tenant ready architecture
Reliability
Circuit Breaker — Cascading failure prevention Auto-Retry — Exponential backoff with jitter Health Checks — K8s liveness & readiness probes
Security
Input Validation — Zod schemas everywhere Injection Prevention — XSS & path attacks blocked Rate Limiting — Token bucket algorithm
Performance
Request Queue — Concurrency control (10 max) Request Deduplication — Shares concurrent results Response Caching — TTL-based with LRU eviction
Quick Start
npm install && npm run build
node dist/index.jsConfiguration
{
"mcpServers": {
"braze": {
"command": "node",
"args": ["/path/to/mcp-braze/dist/index.js"],
"env": {
"BRAZE_API_KEY": "your-api-key",
"BRAZE_REST_ENDPOINT": "https://rest.iad-01.braze.com"
}
}
}
}{
"mcpServers": {
"braze": {
"command": "npx",
"args": [
"-y", "mcp-remote",
"https://your-server.com/mcp",
"--header", "x-braze-api-key:your-api-key",
"--header", "x-braze-rest-endpoint:https://rest.iad-01.braze.com"
]
}
}
}Deploy server with HTTP transport
Claude.ai → Settings → Connectors
Add URL:
https://your-server.com/mcpAdd headers:
x-braze-api-key,x-braze-rest-endpoint
Platform | Config Path |
macOS |
|
Windows |
|
β Tools
Category | Tools |
Users |
|
Messaging |
|
Scheduling |
|
Exports |
|
| |
SMS |
|
Subscriptions |
|
Templates |
|
Catalogs |
|
Preferences |
|
SCIM |
|
° Deprecated — use email_blocklist instead
Usage
"Track a purchase event for user123 with amount $99.99"
"Send the welcome campaign to users who signed up today"
"Get campaign analytics for the last 30 days"
"List all users in the Premium segment"
"Create a new email template for order confirmations"Authentication
Priority | API Key | REST Endpoint |
1 |
|
|
2 |
|
|
3 |
|
|
4 |
| — |
Braze REST Endpoints
Region | Endpoint |
US-01 |
|
US-02 |
|
US-03 |
|
US-04 |
|
US-05 |
|
US-06 |
|
US-07 |
|
US-08 |
|
EU-01 |
|
EU-02 |
|
Find your endpoint in Braze Dashboard → Settings → APIs and Identifiers
Stability & Resilience
Auto-retries on HTTP 429, 500, 502, 503, 504
Handles network errors (ECONNRESET, ETIMEDOUT, ECONNREFUSED)
Respects
Retry-AfterheadersConfigurable max retries, delays, jitter
Prevents cascading failures:
CLOSED — Normal operation
OPEN — Fast-fail mode (5 failures trigger)
HALF_OPEN — Recovery testing
Timeout: 30s default (AbortController)
Deduplication: Shares identical concurrent requests
Queue: Limits to 10 concurrent requests
Rate Limiting: Token bucket algorithm
Kubernetes-ready probes:
health— Full status reportliveness— Alive checkreadiness— Traffic ready
Deployment
FROM node:20-alpine
WORKDIR /app
COPY package*.json ./
RUN npm ci --production
COPY dist ./dist
EXPOSE 3000
CMD ["node", "dist/index.js"]docker build -t mcp-braze .
docker run -p 3000:3000 \
-e BRAZE_API_KEY=your-key \
-e BRAZE_REST_ENDPOINT=https://rest.iad-01.braze.com \
mcp-braze# Server
PORT=3000
NODE_ENV=production
# Auth (prefer headers in production)
BRAZE_API_KEY=
BRAZE_REST_ENDPOINT=
BRAZE_APP_ID=
# Rate Limiting
RATE_LIMIT_ENABLED=true
RATE_LIMIT_REQUESTS_PER_SECOND=10
# Caching
CACHE_ENABLED=true
CACHE_TTL_SECONDS=300
CACHE_MAX_SIZE=1000
# Circuit Breaker
CIRCUIT_BREAKER_ENABLED=true
CIRCUIT_BREAKER_THRESHOLD=5
CIRCUIT_BREAKER_RESET_TIMEOUT=60000
# Logging
LOG_LEVEL=info
# Sentry (Optional)
SENTRY_DSN=
SENTRY_ENVIRONMENT=productionArchitecture
src/
├── index.ts # Entry point
├── server.ts # MCP server init
├── tools/ # 92 tools
│ ├── users.ts
│ ├── messaging.ts
│ ├── scheduling.ts
│ ├── exports.ts
│ ├── email.ts
│ ├── sms.ts
│ ├── subscriptions.ts
│ ├── templates.ts
│ ├── catalogs.ts
│ ├── preference-center.ts
│ └── scim.ts
└── lib/ # Core utilities
├── auth.ts # API key extraction
├── client.ts # Braze HTTP client
├── validation.ts # Zod schemas
├── errors.ts # Error handling
├── retry.ts # Backoff
├── circuit-breaker.ts # Failure prevention
├── rate-limiter.ts # Token bucket
├── cache.ts # TTL cache
├── request-queue.ts # Concurrency
├── deduplication.ts # Request dedup
├── idempotency.ts # Safe retries
├── health.ts # K8s probes
├── logger.ts # Structured logging
└── sentry.ts # Error tracking~3,500 lines · 154 unit tests · 126 e2e tests
References
MCP Specification | |
MCP SDK | |
mcp-remote | |
Braze API |
MIT License
DELTΔ & βETΑ
From Change to What's Next
This server cannot be installed
Maintenance
Resources
Unclaimed servers have limited discoverability.
Looking for Admin?
If you are the server author, to access and configure the admin panel.
Latest Blog Posts
- Your AI Chatbot Just Exposed Your CEO's Salary to an InternBy Om-Shree-0709 on .Agent IdentityMCP SecurityOAuth Delegation
- Why MCP Servers Need Execution Sandboxing (And Why Your Current Stack Isn't Enough)By Om-Shree-0709 on .Agentic AiPrompt InjectionWebAssembly
MCP directory API
We provide all the information about MCP servers via our MCP API.
curl -X GET 'https://glama.ai/api/mcp/v1/servers/delta-and-beta/mcp-braze'
If you have feedback or need assistance with the MCP directory API, please join our Discord server