On this page

Integration Layer

Tajo’s integration layer connects platforms to Brevo through Claude + MCP. Instead of building custom integrations, you wire multiple MCP servers together and let AI agents orchestrate the data flow.

How It Works

┌─────────────────────┐     ┌─────────────────────┐
│   Source Platform    │     │   Brevo (Engagement) │
│                     │     │                     │
│  Shopify MCP        │     │  Brevo MCP          │
│  HubSpot MCP        │◄───►│  27 modules:        │
│  Stripe MCP         │     │  contacts, email,   │
│  Custom API         │     │  SMS, WhatsApp, CRM │
└─────────────────────┘     └─────────────────────┘
           ▲                         ▲
           │                         │
           └──────────┬──────────────┘
                      │
              ┌───────▼───────┐
              │  Claude + AI   │
              │  Agent         │
              │                │
              │  Reads both    │
              │  MCP servers,  │
              │  orchestrates  │
              │  the flow      │
              └────────────────┘

The pattern is always the same:

Connect the source platform’s MCP server to Claude
Connect Brevo’s MCP server to Claude
Define an agent that bridges them, reads data from source, triggers engagement in Brevo
Run on events, schedules, or natural language prompts

Supported Platforms

Official MCP Servers

These platforms have official, maintained MCP servers:

Platform	MCP Server	Auth	What It Exposes
Brevo	`mcp.brevo.com`	Token	Contacts, email, SMS, WhatsApp, CRM, campaigns (27 modules)
Shopify	`@shopify/dev-mcp`	None (dev)	API schemas, docs, GraphQL introspection
Shopify Storefront	Storefront MCP server	App auth	Products, cart, customers, orders, policies
HubSpot	`mcp.hubspot.com`	OAuth/PKCE	Contacts, companies, deals, tickets, products, orders (read-only)
Stripe	`@stripe/mcp`	API key	Payments, subscriptions, customers, invoices, knowledge base

Community & REST API MCP Servers

Platform	MCP Server	Auth	What It Exposes
Salesforce Commerce Cloud	`@anthropic/salesforce-mcp`	OAuth	Customer records, orders, products, custom objects via SOQL
BigCommerce	`bigcommerce-mcp-server`	API token (V3)	Customers, orders, products, carts, channels
WooCommerce	`woocommerce-mcp-server`	Consumer Key/Secret	Customers, orders, products, coupons, reports
Webflow	`webflow/mcp-server`	OAuth	Sites, forms, submissions, CMS collections, analytics

For platforms not listed here, build a connector agent that calls their REST API directly through Claude’s built-in HTTP tools.

Integration Guides

Shopify + Brevo

Sync Shopify customers and orders to Brevo. Trigger post-purchase emails, cart recovery, and loyalty campaigns from store events.

HubSpot + Brevo

Bridge HubSpot CRM data to Brevo’s engagement layer. Sync contacts, enrich segments, and trigger campaigns from deal stage changes.

Stripe + Brevo

Connect payment events to engagement. Subscription renewals, failed payments, refunds, each triggers the right message at the right time.

Webflow + Brevo

Capture Webflow form leads into Brevo contacts. Trigger nurture sequences based on form type and page context, sync CMS content for dynamic campaigns.

Salesforce Commerce Cloud + Brevo

Connect SFCC storefront data to Brevo. Customer sync, order lifecycle campaigns, and behavioral retargeting for enterprise commerce.

BigCommerce + Brevo

Sync BigCommerce customers and orders to Brevo. Post-purchase sequences, abandoned cart recovery, and loyalty campaigns.

WooCommerce + Brevo

Connect WooCommerce store data to Brevo. Customer sync, order-driven campaigns, cart recovery with auto-generated coupons, and review requests.

Custom API + Brevo

Build your own connector agent for any platform with a REST API. Template for Magento, Zendesk, or proprietary systems.

The Multi-MCP Pattern

Every integration follows this Claude configuration pattern, multiple MCP servers connected simultaneously:

{
  "mcpServers": {
    "brevo": {
      "command": "npx",
      "args": [
        "mcp-remote",
        "https://mcp.brevo.com/v1/brevo/mcp",
        "--header",
        "Authorization: Bearer ${BREVO_MCP_TOKEN}"
      ],
      "env": {
        "BREVO_MCP_TOKEN": "your-brevo-token"
      }
    },
    "shopify-dev-mcp": {
      "command": "npx",
      "args": ["-y", "@shopify/dev-mcp@latest"]
    }
  }
}

With both servers connected, Claude can:

Read product data from Shopify
Create contacts and campaigns in Brevo
Orchestrate the flow in a single conversation

Why This Approach?

Traditional Integration	Tajo MCP Integration
Build custom middleware	Connect MCP servers to Claude
Months of development	Minutes of configuration
Rigid, predefined workflows	Flexible, AI-orchestrated flows
Breaks when APIs change	MCP servers maintained by platform vendors
One sync direction	AI decides what to sync based on context
Per-integration maintenance	One pattern, any platform

Next Steps

Shopify + Brevo, Most common integration
Brevo MCP Server Setup, Configure Brevo’s 27 MCP modules
Building Agents, Build agents that bridge platforms
Agent Specification, Define multi-MCP agents