19 marketing MCP servers, compared (2026)

Strengths

• Eight generic tools reach the full Journeys UI and Data Pipelines APIs: automations, segments, people, content and delivery metrics, with skills that guide multi-step tasks.
• A connection starts with the read scope; writing drafts, sending and configuring are separate scopes, an account admin must turn MCP on, and live data and sensitive attributes stay closed until an admin opens them. Tools support dry-run previews.

Watch-outs

• Each user manages their own sessions: account admins can't view or revoke another user's MCP connection.

Strengths

• Read and write tools for campaign and Canvas analytics, segments, custom attributes, email templates, content blocks, catalogs and media; Canvases are read-only.
• Access follows your Braze dashboard permissions and ends when your dashboard access does; no tool returns user-level PII, and Braze advises against your client's auto-mode.

Watch-outs

• Workspaces that use IP allowlisting can't use the remote server, and Braze keeps an allowlist of supported clients, so others may be blocked at sign-in.

Strengths

• Tools map to Iterable's API: campaigns, templates, lists, catalogs, snippets, users and events, with journeys and campaigns that can be triggered once sends are on.
• Setup starts read-only, with no PII, writes or sends; each is a flag saved per API key, sends need writes, and keys can differ from one project to the next.

Watch-outs

• In beta and local only, and creating a blast campaign schedules it for delivery: the API has no draft campaign.

Strengths

• Over 260 tools, from creating campaigns and flows to updating profiles and reading campaign and flow reports; a core-tools-only setting trims it to about 40 for clients with small context windows.
• read-only=true turns off every tool that writes, tools that read user-generated content can be switched off, and toolsets limits the server to the API scopes you choose. The remote server needs an Owner, Admin or Manager role.

Watch-outs

• With writes on, send_campaign can send a campaign to its whole audience; for analysis, connect with read-only=true.

Strengths

• Reads CRM records, activities, campaigns, content and email analytics; creates and edits records, campaigns, static segments and marketing email drafts, and can publish landing pages, website pages and blog posts.
• Every action follows the user's HubSpot permissions and the scopes granted at install; when Sensitive Data is on, activities and conversations are blocked from the MCP server.

Watch-outs

• Some writes go live at once: it can publish landing pages, website pages and blog posts.

Strengths

• Tools for contacts, tags, lists, custom fields, deals and pipelines, custom objects and email activity; it reads campaigns and edits a campaign's message content.
• Each account has its own private MCP URL, and connecting means signing in to ActiveCampaign and approving the connection.

Watch-outs

• Adding a contact to an automation starts that automation's steps for them, and no read-only mode is documented.

Strengths

• 27 modules: contacts, lists, segments, email campaigns, campaign analytics, templates, SMS and WhatsApp campaigns, CRM deals and tasks, senders and domains, users and webhooks.
• You connect with an MCP token created among your API keys, and single-module endpoints, such as contacts only, give an agent a smaller set of tools.

Watch-outs

• Its MCP page documents no read-only mode.

Strengths

• Finds, creates and updates contacts and their properties, manages mailing-list membership, sends events, creates and manages campaigns and workflows, and edits email content.
• Each client is authorized by signing in to Loops in your browser; the MCP page documents no other safeguard.

Watch-outs

• Events can start published workflows, so an agent that sends events can trigger messages too.

Strengths

• Covers subscribers, lists, tags, segments, campaigns, sequences, templates, transactional email, analytics, SMS and push, with presets that range from read-only to full access.
• The default preset can draft but can't deliver, delete, change the team or create API keys; sending needs a sender preset or scopes, and the workspace role still applies.

Watch-outs

• A removed permission can take up to five minutes to apply, while a widened one applies at once.

Strengths

• Maps Kit's v4 API one to one: subscribers, tags, segments, custom fields, sequences, broadcasts and stats, including composing, scheduling and sending broadcasts.
• Every tool carries an annotation, and Kit says sending broadcasts and deleting data always require explicit user confirmation; each token is limited to 120 requests a minute.

Watch-outs

• Paid plans only: Creator and Creator Pro.

Strengths

• Sends and schedules emails, creates and sends broadcasts, builds automations, publishes templates, and manages contacts, segments, topics, domains, webhooks and API keys.
• The hosted server asks you to sign in and approve access, or takes an API key for headless clients; the open-source local server can limit which folders it reads attachments from.

Watch-outs

• No read-only mode is documented, and the same connection can create API keys.

Strengths

• 24 tools: single sends and batches of up to 500 messages, template management, message search, bounces and suppressions, delivery stats and webhooks.
• Tools carry read-only and destructive annotations, so a client can run reads freely and ask before a send or a delete; the token limits it to one Postmark server.

Watch-outs

• Local only, and one batch call can send up to 500 emails.

Strengths

• Nine tools: build a template, list, describe and call any Transactional API endpoint, diagnose a failed send, check the account and get onboarding and integration help.
• What the server can do follows the API key: a key restricted to certain calls needs its AI Agents group enabled to use the MCP.

Watch-outs

• Transactional only: Mailchimp documents no MCP server for its marketing platform's account data.

Strengths

• 43 tools: send a push notification, email or SMS, manage users, subscriptions, segments and templates, export audiences, and check deliverability and email warm-up.
• send_message is flagged high-impact so clients can ask before running it; targeting and inputs are validated before a send, calls are rate-limited, and any client can be revoked from Connected apps.

Watch-outs

• In open beta: an app may need access enabled before tools other than the utilities work.

Strengths

• Creates workflows and their email, SMS, push, chat and in-app steps, manages users, tenants and objects, triggers workflows, and can hand complex tasks to the Knock agent.
• At sign-in you choose which capabilities to enable, with data management and debugging off by default, and the server ships no delete tools, to prevent accidental deletions.

Watch-outs

• A service token skips the consent screen and turns every capability on.

Strengths

• 14 tools: search and read conversations, contacts and companies, create and update Help Center articles, and add internal notes to conversations.
• The OAuth flow shows a consent screen listing what the client may do, and internal notes are visible to teammates only: no tool sends a reply a customer can see.

Watch-outs

• Support data rather than marketing campaigns, and workspaces in Intercom's Australian region aren't supported yet.

Strengths

• Tools across every PostHog product: queries and dashboards, cohorts and persons, feature flags and experiments, surveys, and Workflows that draft broadcasts, publish workflows and run batch sends.
• A header or query parameter limits a session to read-only tools, filters narrow it to chosen features, and a batch send needs the audience count and a confirm token the API checks, valid for 15 minutes.

Watch-outs

• The full server covers all of PostHog, from SQL to deleting persons: filter it to the tools a task needs.

Strengths

• Reads and writes charts, dashboards, notebooks, experiments, cohorts, feature flags, metrics and the tracking plan's events and properties; guides and surveys are read-only.
• The server uses your Amplitude permissions, and admins can turn it off or scope it with read and write role actions, project by project, which apply even to org admins.

Watch-outs

• MCP access is on for every user in an organization until an admin restricts it.

Strengths

• 59 tools, shared with the built-in assistant, for segments, journeys, templates, tracking and analytics; a journey is created as a draft, with every node, in one call. MCP calls are never metered.
• A journey your AI builds stays a draft until it is published, and publishing, pausing or deleting through an agent takes a confirmation step in your AI client.

Watch-outs

• AI actions can change a live journey without a confirmation step: update_journey can set or clear a published journey's exit condition, which takes effect on the next event, and other edits, such as changes to a segment or a template, apply when saved. fromHello Cloud is in early access through the waitlist.