Connect AI (MCP) — run your account from Claude or ChatGPT

The Build with AI page makes your assistant able to write code against WeZend. Connect AI goes further: your assistant operates your account directly — no code, just conversation.

What it can do

Read & diagnose — plan & usage, contacts (search), segments, journeys, campaigns, templates, forms, flows, integrations, senders, email domains, analytics, ROI, deliverability, budget — and explain_message: "why did message X fail?"

Understand your CDP data — which events are flowing in (types, volumes, sample properties), any contact's unified profile (identity, custom fields, lifecycle stage, engagement score, churn risk, predicted CLV, recent events), computed traits, and behavioural analytics: funnels between event steps and weekly retention cohorts.

Configure — create segments (explicit rules or a plain-English description we translate to rules), add contacts (JSON array or raw pasted CSV), migrate from Klaviyo/Mailchimp/Brevo (suppressions + contacts, consent intact), create templates, campaign drafts, journey drafts and lead forms, request sender IDs, add + verify email domains (SPF/DKIM/DMARC), set sending policy, set budget caps.

Act — confirm-gated — send_campaign, launch_journey and send_test are real, billable actions. They refuse to run unless the call carries confirm: true, so your assistant must explicitly confirm before anything is sent. Confirmed or not, every dashboard guard still applies: suppression lists, quota, budget caps, card-on-file and the audit log.

Deliberately excluded — connecting integrations, WhatsApp/Voice/Push credentials and billing. Anything involving secrets or money stays in the dashboard, behind your login.

In total: 44 tools, each mapped 1:1 to the same customer-scoped services the dashboard uses. The account identity always comes from your API key — never from the model.

Get your key

Dashboard → Connect AI (/connect-ai). Create a key there; you can revoke it at any time. Treat it like a password.

Connect from Claude

claude.ai / Claude Desktop (remote connector): add a custom connector pointing at

https://api.wezend.com/v1/mcp

with your API key as the X-API-Key header.

Claude Desktop / Claude Code (stdio bridge): if your client prefers a local MCP server, use the npm bridge:

{
  "mcpServers": {
    "wezend": {
      "command": "npx",
      "args": ["-y", "@wezend/mcp"],
      "env": { "WEZEND_API_KEY": "zc_live_sk_..." }
    }
  }
}

The bridge speaks MCP over stdio and forwards to /v1/mcp (override with WEZEND_MCP_URL for staging).

Connect from ChatGPT

Create a GPT → Actions → Import from URL:

https://api.wezend.com/v1/mcp/openapi.json

That spec describes a single endpoint, POST /v1/mcp/act, taking { "tool": "...", "arguments": { ... } } — with the full tool list embedded so the model knows what it can call. Set authentication to an API key in the X-API-Key header.

Try it

Ask your assistant, in your own words:

• "What plan am I on and how much of my quota is left this month?"
• "Create a segment of customers who haven't opened anything in 60 days."
• "Here's a CSV of leads from our fair — import them and add them to a 'Fair 2026' list." (paste the CSV)
• "I'm moving from Klaviyo — here's my suppression export, then my profile export." (paste both, in that order)
• "Draft a two-step win-back journey for that segment — don't activate it yet."
• "What events are we actually receiving, and what do they contain?"
• "Show me the full profile for anna@example.com — is she churn-risk?"
• "Create an ltv trait that sums order revenue, then a segment of everyone above 5,000."
• "How does our signup → first purchase funnel look over the last 30 days?"
• "Why did message msg_1a2b fail?"
• "Send campaign X." → the assistant will be asked to confirm before anything leaves.

Migrate from Klaviyo, Mailchimp or Brevo — in chat

Two source-aware tools reuse the same mapping engine as the migration wizard, so field mapping, lists and consent survive the move:

1. import_migration_suppressions(source, csv) — always first. Imports the unsubscribe/suppression export, so no one who opted out at your old provider can ever be mailed from WeZend.
2. import_migration_contacts(source, csv, list_name?) — then the profile export, with the source's field mapping and consent applied.

The tools enforce the order: contact import for a source is refused until its suppressions have been imported. Paste each export straight into the chat — for very large files, use the migration wizard in the dashboard instead.

Understand & shape your CDP data

Six read tools and two configuration tools cover the CDP:

• list_event_types() — the event types your account receives, with volumes and sample properties, so the assistant knows what your data actually looks like before building on it.
• get_events(contact?, event_type?, limit?) — the recent event stream, filterable.
• get_profile(contact) — one contact's unified profile: identity, custom fields, lists, consent, lifecycle stage, engagement score, churn risk, predicted CLV and the latest events.
• list_computed_traits() / create_computed_trait(key, source, agg, event_type?, field?) / refresh_traits() — traits aggregate events, messages or orders per contact (count, sum, avg, max, min or days_since). "Create an ltv trait summing order revenue" or "add days_since_purchase" — then segment on them immediately.
• get_funnel(steps, days?) — conversion between event steps, e.g. product_viewed → checkout_started → order_completed.
• get_retention(weeks?) — weekly cohort retention.

Ask "what does our signup-to-purchase funnel look like?", get the numbers, then say "create a segment of everyone stuck at checkout and draft a nudge campaign" — the assistant chains it end to end.

The 44 tools

get_plan_usage, list_segments, list_journeys, list_campaigns, get_recent_messages, list_contacts, list_templates, list_forms, list_flows, list_integrations, list_senders, list_email_domains, list_migration_sources, get_analytics, get_roi, get_deliverability, get_budget, explain_message, list_event_types, get_events, get_profile, list_computed_traits, get_funnel, get_retention — read.

create_segment, add_contacts, import_contacts_csv, import_migration_suppressions, import_migration_contacts, create_computed_trait, refresh_traits, create_template, create_form, create_journey, create_campaign, create_sender, add_email_domain, verify_email_domain, set_sending_policy, set_budget, pause_campaign — configure.

send_campaign, launch_journey, send_test — act, confirm required.