Fire

Provides a write-enabled MCP server to manage Braze workspaces and trigger campaigns for demos and POCs.

python

GitHub Stars

python

Language

5 months ago

First Indexed

2 months ago

Catalog Refreshed

Documentation & install

Readme and setup notes from the catalogue, plus a client-ready config you can copy for your MCP host.

Installation

Add the following to your MCP client configuration file.

Configuration

View docs

{
  "mcpServers": {
    "saarkia-firemcp": {
      "command": "python",
      "args": [
        "-m",
        "braze_mcp_write.main"
      ],
      "env": {
        "BRAZE_API_KEY": "YOUR_API_KEY",
        "BRAZE_BASE_URL": "https://rest.iad-01.braze.com",
        "BRAZE_WRITE_ENABLED": "true",
        "BRAZE_DRY_RUN_DEFAULT": "false",
        "BRAZE_ALLOW_PRODUCTION": "true",
        "BRAZE_ALLOWED_WORKSPACES": "demo-,poc-,test-",
        "BRAZE_MAX_SENDS_PER_HOUR": "1000",
        "BRAZE_MAX_CATALOG_UPDATES_PER_MIN": "100"
      }
    }
  }
}

This MCP server provides a write-enabled extension to Braze MCP, allowing you to manage user data, trigger campaigns and canvases, and coordinate test environments. It includes safety features to prevent unintended production changes, supports dry runs for testing, and logs all activities for auditing. Use it to build realistic demo environments and validate your Braze integrations before moving to production.

How to use

Set up your MCP client to connect to the braze_write server and perform write-enabled operations. You can update user attributes, track events, trigger campaigns and canvases, manage catalog items and content blocks, and delete or identify users. Start with dry runs to validate your actions, then enable real writes only after you confirm the workspace configuration and safety settings.

How to install

# Prerequisites
Recommended: Python 3.8+ and a working Braze workspace with a demo/POC/test prefix

# Install the MCP package in editable mode
pip install -e .

# Optional: install with UV tooling if you prefer uvx
uv pip install -e .

Configuration and safety

Configure environment variables to control access, workspace safety, and operation limits. You will set your API key, Braze base URL, and safety preferences before starting the MCP server.

# Required API and base URL
BRAZE_API_KEY=your-api-key-here
BRAZE_BASE_URL=https://rest.iad-01.braze.com

# Safety configuration
BRAZE_WRITE_ENABLED=true                    # Enable write operations
BRAZE_ALLOW_PRODUCTION=false                # Block production workspaces
BRAZE_ALLOWED_WORKSPACES=demo-,poc-,test-  # Allowed workspace patterns
BRAZE_DRY_RUN_DEFAULT=false                 # Default dry run mode

# Rate limits
BRAZE_MAX_SENDS_PER_HOUR=1000              # Max campaign/canvas sends per hour
BRAZE_MAX_CATALOG_UPDATES_PER_MIN=100      # Max catalog updates per minute

Usage examples

Use the MCP client to perform write operations against Braze workspaces you’ve configured as allowed. Start with dry runs to validate parameters and safety checks, then run real operations after confirming workspace safety.

Available tools

update_user_attributes

Update user profile attributes and related data for a given external_id or user identifier.

track_event

Record custom events with properties for analytics and campaign triggers.

send_campaign

Trigger or manage campaigns and ensure delivery to specified recipients.

trigger_canvas

Trigger and manage canvas-driven journeys for targeted user cohorts.

manage_catalogs

Update catalog items and related catalog data.

manage_content_blocks

Create or update content blocks used in messaging or canvases.

delete_user

Delete a user or revoke identification in a controlled manner.

Built by

VeilStrat

AI signals for GTM teams