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?"

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: 36 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 Code (CLI): one command, same endpoint:

claude mcp add --transport http wezend https://api.wezend.com/v1/mcp \
  --header "X-API-Key: wz_live_sk_..."

The endpoint speaks JSON-RPC over HTTP — one request, one response — so any client with remote MCP support connects to it directly. There is nothing to install.

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."
• "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. migrate_import_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. migrate_import_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.

The 36 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 — read.

create_segment, add_contacts, import_contacts_csv, migrate_import_suppressions, migrate_import_contacts, 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.