# Best email marketing tools with MCP support: campaigns, automations, and analytics compared Canonical: https://brew.new/blog/best-email-marketing-tools-with-mcp-support-campaigns-automations-and-analytics-compared Author: Philip Sørensen Published: 2026-09-22 Updated: 2026-09-29 Brew publishes this comparison. We reviewed the linked product documentation on September 28, 2026; this is a documentation comparison, not a claim of hands-on testing of every platform. Check current plan limits on the vendor's pricing page. You connect your email platform's MCP server to Claude and ask for a win-back automation. Claude pulls last month's campaign report without trouble, but nothing in the tool list creates an automation, so you build the flow by hand in the dashboard. A lot of email platforms now say they "support MCP," but what that means varies. On some platforms an agent can read reports. On others it can build a draft. On a few it can create an automation, publish it and send a campaign to your list. This guide compares nine email platforms by what their MCP servers let an agent do, then walks through connecting Brew to Claude Code. ## Key takeaways - Sort MCP servers by the job they can finish: read analytics, draft a campaign, build an automation, or send. - Several vendors now expose most of their API through MCP. Customer.io, Klaviyo, Brevo and Resend are examples. Most of the difference is in guardrails and in the underlying platform. - Check the default permissions. Customer.io starts read-only. Brew requires confirmation on OAuth and organization connections; brand API-key clients need their own approval policy. - Mailbox providers apply the same [inbox rules](/blog/agent-email-deliverability) whether you or an agent sends from your domain. ## How we compared them We read each vendor's MCP documentation on September 28, 2026 and compared them on four questions: 1. Can the agent create and send, or schedule, a campaign? 2. Can it create or edit an automation, and can it publish one? 3. Can it read campaign or automation analytics? 4. How does it authenticate, and what stops an accidental send? We did not run the same task through each server. We only mark a tool as able to do something if its own documentation describes it. ## MCP support at a glance | Platform | Campaigns | Automations | Analytics | Auth and guardrails | | --- | --- | --- | --- | --- | | Brew | Create, edit, test, send, schedule | Create triggers and graphs, test, publish, fire | Campaign and automation reports | OAuth or API key; sends pause for confirmation on OAuth and organization connections | | Klaviyo | Create, send (`send_campaign`) | Flow tools | Reporting tools | OAuth or private API key | | Customer.io | Create, update, delete via the Journeys API | Campaigns (Customer.io's name for automations) | Delivery metrics readable | Read-only by default; live data protected unless an admin enables it | | HubSpot | Drafts; changelog adds send setup, scheduling and publishing | Not covered in the pages we read | Post-send email analytics | OAuth with PKCE through an MCP auth app | | Brevo | Create and manage | Not listed | Campaign analytics | MCP key as a Bearer token | | Loops | Create and manage | Create and manage workflows | Not listed | OAuth | | Sequenzy | Draft, edit, schedule | Build sequences | Campaign and sequence metrics | OAuth remote server or local API key | | Resend | Broadcasts | Automations | Logs and metrics | API key | | Mailchimp | Claude connector builds and launches campaigns; a separate MCP server sends Transactional (Mandrill) email | Check the connector's tool list | Campaign data through the Claude connector | Connector sign-in; Transactional server uses an API key with the AI Agents permission group | ## Brew Brew's server is at `https://brew.new/api/mcp`. You connect with OAuth, choosing one brand or your whole organization, or with an API key. The [tool catalog](https://docs.brew.new/api-reference/mcp/tools) has tools in five groups: - Design: `create_email`, `edit_email`, `import_email` (HTML, MJML, React Email or a Figma frame) and `export_email` to a connected ESP. - Sending: `send_email` for tests and campaigns. It takes a `scheduledAt` value for scheduled sends. `control_email_send` pauses, resumes or cancels a send. - Automations: `save_trigger`, `save_automation`, `test_automation`, `fire_trigger_event` and `list_automation_runs`. - Audiences and analytics: `create_audience`, `search_contacts`, `get_email_analytics`, and `list_automations` with performance data. - Deliverability: `test_email_rendering`, `create_inbox_placement_test` and `get_domain_health`. Brew's [agent recipe](https://docs.brew.new/recipes/run-brew-from-an-ai-agent) recommends reviewing irreversible sends. OAuth and organization connections require confirmation before a live `send_email`; brand API-key clients need their own approval policy. Brew is also the sending platform, so the agent works with the same domains, audiences and suppression lists your team uses. Brew is email only. It has no SMS or push channels. ## Klaviyo Klaviyo's [MCP server](https://developers.klaviyo.com/en/docs/klaviyo_mcp_server) connects over OAuth or a private API key, either as a hosted remote server or locally. Its [tool list](https://developers.klaviyo.com/en/docs/klaviyo_mcp_server_available_tools) covers campaigns, flows, templates, reporting, profiles, catalogs and more. It includes a `send_campaign` tool that sends a campaign to its configured audience. Klaviyo's [Claude announcement](https://www.klaviyo.com/blog/agentic-marketing-workflows-with-klaviyo-anthropic-claude) focuses on reporting, flow audits and briefs. Klaviyo fits ecommerce teams whose customer and order data already live there. ## Customer.io Customer.io's [MCP server](https://docs.customer.io/ai/mcp/get-started/) has US and EU endpoints and gives the agent access to the Journeys UI API and the Data Pipelines API. It exposes separate tools for reads (`cio_read_api`), writes (`cio_write_api`) and deletes (`cio_delete_api`), so you can approve each kind of action separately. A new connection gets read scope only, and it cannot edit live data or delete people unless an admin enables that. Customer.io is multi-channel, so the same connection can reach SMS, push and in-app messages. It suits teams that already model their product data in Customer.io. ## HubSpot HubSpot's remote server runs at `mcp.hubspot.com`. You create an MCP auth app inside HubSpot, then connect any client that supports OAuth with PKCE. The [setup documentation](https://developers.hubspot.com/docs/apps/developer-platform/build-apps/integrate-with-the-remote-hubspot-mcp-server) covers marketing email drafts through `manage_marketing_email`, along with CRM records. HubSpot's [Fall 2026 changelog](https://developers.hubspot.com/changelog/fall-2026-spotlight), dated September 15, 2026, adds send configuration, scheduling, publishing and post-send analytics for marketing email. It fits teams whose CRM and marketing email both already live in HubSpot. ## Brevo Brevo's [MCP server](https://developers.brevo.com/docs/mcp-protocol) combines 27 modules behind one endpoint and generates its tools from the Brevo OpenAPI spec. It covers email campaigns, contacts, CRM deals, SMS and WhatsApp campaigns, transactional templates and campaign analytics. You authenticate with a dedicated MCP key. ## Loops The [Loops MCP server](https://loops.so/docs/mcp-server) at `https://mcp.loops.so` manages contacts and mailing lists and sends events and published transactional emails. It also creates and manages campaigns and workflows, and it can edit email content. The docs do not list analytics. Loops fits SaaS teams that want a simple platform their agent can manage over MCP. ## Sequenzy [Sequenzy's MCP](https://docs.sequenzy.com/concepts/mcp) covers subscribers, lists and segments. It also drafts, edits and schedules campaigns, builds sequences with branches and wait-for-event steps, generates AI content and reads analytics. Sequenzy's docs note that some setup, billing, destructive actions and final send decisions may still need the dashboard or a human review. ## Resend Resend's [agent tooling](https://resend.com/agents) includes a hosted MCP server at `mcp.resend.com/mcp`, which you authenticate with an API key. It covers sending, contacts, broadcasts, automations and templates. Resend's [Automations](https://resend.com/blog/introducing-automations) became generally available in April 2026. It suits developer teams that already send transactional email through Resend. ## Mailchimp Mailchimp has two entry points for agents. Its official MCP server is for [Mailchimp Transactional](https://mailchimp.com/developer/transactional/guides/how-to-use-mailchimps-transactional-messaging-mcp/), the product formerly called Mandrill. A separate [Claude connector](https://mailchimp.com/resources/connect-mailchimp-to-claude/) works from your Mailchimp data, and Mailchimp's page describes building, refining and launching campaigns from the conversation. Check the connector's current tool list for exactly what it can save, schedule or send. ## How to choose | If your agent needs to... | Look at | | --- | --- | | Design an on-brand email, test it and send or schedule it | Brew | | Build and publish an event-triggered automation | Brew, Loops, Resend, Sequenzy | | Report on ecommerce campaigns and flows | Klaviyo | | Work across email, SMS and push with separate read and write approval | Customer.io | | Stay inside your CRM | HubSpot | Before you give an agent write access, [brief it](/blog/how-to-brief-an-email-agent) the way you would brief a new coordinator, and send the first campaign to a seed list before the real audience. ## Use the same tools from Claude Code Add Brew's hosted server using Claude Code's [HTTP MCP setup](https://code.claude.com/docs/en/mcp): ```bash claude mcp add --transport http brew https://brew.new/api/mcp ``` Open Claude Code, run `/mcp`, and authenticate the Brew connection. Select the brand you intend to use. Ask Claude to call `get_brew_capabilities` before campaign work so it reads the current tool contract. Start with a draft and a test recipient: ```text Create a product-update email for the connected brand about our new CSV import. Link the main button to https://example.com/import. Show me the draft, subject, sender domain, and audience before scheduling. Send a test only to my approved test address after I provide it. ``` Review the preview and links, then inspect the test in your inbox. For the live send, give Claude the saved audience, exact date, time, and time zone. Review the confirmation details before approval. Save the returned send ID so you can check status or cancel the scheduled send with `control_email_send`. For repeatable backend jobs, use a typed API client or CLI. Keep credentials in the client configuration or environment, not in prompts or committed files. Brew's [CLI guide](https://docs.brew.new/api-reference/cli/agents) covers terminal workflows. The [MCP versus REST guide](/blog/mcp-vs-rest-api-for-email-marketing-which-workflow-should-you-use) explains how to split interactive campaign work from production event handling. ## Frequently asked questions ### What is an MCP server for email marketing? It is an endpoint that exposes a platform's actions as tools an AI assistant can call. Claude, ChatGPT and Cursor are common clients. The assistant reads the tool list and decides which tool to call for your request. ### Can an MCP agent send a campaign without my approval? It depends on the platform and your client settings. Brew requires confirmation for live sends on OAuth and organization connections. Brand API-key clients need their own approval policy. Customer.io starts read-only. Other servers rely on your MCP client to ask before each tool call, so check both sides. ### Do I need a developer to connect one? Usually not. Brew, Loops, Klaviyo and HubSpot support OAuth, so you paste a server URL and sign in. API keys are the fallback for clients without an OAuth screen. ### Does MCP change deliverability or compliance? No. Mailbox providers score your domain and complaint rate. [Gmail's sender requirements](https://support.google.com/mail/answer/81126) and [CAN-SPAM](https://www.ftc.gov/business-guidance/resources/can-spam-act-compliance-guide-business) apply however a send was started. ## Next step The [Brew MCP page](/mcp) has the server URL and client setup. Connect it, then ask for your next campaign as a test send.