A Mailchimp MCP where creating a campaign never sends an email
Connect one API key and Mailchimp audiences, members, tags, segments, campaigns, and reports become workflow steps for visual automations and AI agents. The server address is read from the key itself, members are addressed by plain email, and campaigns are created as drafts: the two nodes that send real email say so on the label and stay behind whatever gate you choose.
What the Mailchimp MCP connector does
The Mailchimp connector for Mattering Automations is 39 nodes across the Marketing API v3: audiences (list, get, create, update), the member lifecycle (add, upsert by email, update, archive, search), tags and static segments, the campaign loop (draft, settings, content, test send, send, schedule, unschedule), templates and their editable sections, campaign reports down to per-recipient email activity and per-link click details, and the merge field reference that member updates depend on.
Every node speaks MCP, the open protocol for connecting AI assistants to tools, so Claude, ChatGPT, and any MCP-capable assistant can use them, alongside Matter, the AI assistant built into the platform. An assistant can answer whether an address is already subscribed, which link in last week's campaign was clicked most, and how a draft reads before anyone schedules it, without opening the Mailchimp dashboard.
Because Mattering is a work platform rather than middleware, email marketing work lands somewhere useful by default: form leads can upsert into an audience with the right tags the moment they arrive, and a scheduled report sweep can turn open and click rates into tasks in Mattering Productivity or records in a Mattering database, all on one canvas next to the rest of the work.
The send boundary is loud by design. Campaigns are created as drafts, and nothing in the create, content, or settings nodes emails anyone. Mailchimp: Send Campaign (Sends Real Email) and Mailchimp: Schedule Campaign (Sends Real Email at the Scheduled Time) are the two nodes that commit a real send, both flagged so a workflow has to mean it. Mailchimp: Unschedule Campaign is the undo for a scheduled send until the send time arrives, and Mailchimp: Send Test Email is the safe preview path, honest that the listed test inboxes do receive real mail.
One connection, three surfaces
- Visual automations. Drag Mailchimp nodes onto the canvas and wire them to triggers, conditions, and other apps.
- AI agents, yours or ours. These nodes speak MCP, the open protocol, so Claude, ChatGPT, and any MCP-capable assistant can use them, and Matter, the agent built into the platform, uses them natively.
- The whole platform. Combine with native tasks, projects, and other connectors, no middleware in between.
Every Mailchimp node, ready to drop on the canvas
39 nodes, generated from the connector itself so this list always matches what ships. Expand a category to browse.
Read and query nodes 22
Mailchimp: Get Audience
Get one audience's full settings and stats: contact info, campaign defaults, permission reminder, double opt-in flag, and member counts (data.stats.member_count and friends).
Mailchimp: Get Campaign
Get one campaign's full details: status, recipients, settings (subject line, from name, reply-to), tracking options, and send_time. data.status tells an automation whether the campaign is still a draft (save) or already sent.
Mailchimp: Get Campaign Click Details
Per-URL click report for a sent campaign: every tracked link with its total and unique clicks and click percentages. Answers which link in the email actually performed.
Mailchimp: Get Campaign Content
Get the HTML and plain-text content of a campaign (data.html and data.plain_text). Useful for auditing a draft before send or feeding campaign copy into another step.
Mailchimp: Get Campaign Email Activity
Per-recipient activity for a sent campaign: each member's opens, clicks, and bounces with timestamps. The raw feed for engagement scoring or a clicked-but-did-not-convert follow-up automation. Large campaigns return many rows; page with count and offset.
Mailchimp: Get Campaign Report
Get the full report for one sent campaign: opens, clicks, bounces, unsubscribes, abuse complaints, and timing. The key numbers live at data.opens.open_rate and data.clicks.click_rate.
Mailchimp: Get Member
Look up one contact in an audience by email address and return their full profile: status, merge fields, tags, and engagement stats. A contact not in the audience returns a 404, which makes this the standard exists-check before an add or update step.
Mailchimp: Get Segment
Get one segment's details: name, type, member_count, and for saved segments the matching conditions.
Mailchimp: Get Template
Get one template's details (name, type, category, creation info).
Mailchimp: Get Template Default Content
Get a template's editable sections and their default content (data.sections). The section names are the keys to fill in Set Campaign Content's template reference.
Mailchimp: List Audiences
List the audiences (lists) in the Mailchimp account, with their ids, settings, and stats (member_count, open_rate, click_rate). Audience ids from data.lists[].id feed every other Mailchimp node.
Mailchimp: List Campaign Reports
List summary reports for sent campaigns: emails_sent, opens, clicks, bounces, and unsubscribes per campaign. The feed for a recurring performance digest automation.
Mailchimp: List Campaigns
List campaigns in the account with filters for status, type, audience, and send window. Campaign ids from data.campaigns[].id feed the get/update/send/content/report nodes.
Mailchimp: List Member Tags
List the tags currently on one contact, looked up by email address. Returns data.tags[] with id, name, and date_added.
Mailchimp: List Members
List the contacts in an audience, optionally filtered by subscription status. Each member carries email, status, merge fields, tags, and engagement stats. Member outputs contain personal data (names, emails) that persists in execution records.
Mailchimp: List Merge Fields
List an audience's merge fields (custom contact attributes): tag, name, type, and required flag. The tags returned here (FNAME, LNAME, ...) are the keys to use in the member nodes' merge_fields objects.
Mailchimp: List Segment Members
List the contacts currently in a segment (works for saved and static segments, including tag membership via the tag's segment id). Member outputs contain personal data that persists in execution records.
Mailchimp: List Segments
List an audience's segments with their ids, type (saved, static, or fuzzy), and member counts. Tags appear here as static segments, so this also enumerates tag membership counts.
Mailchimp: List Templates
List the account's email templates with ids, names, and types. Template ids from data.templates[].id plug into Set Campaign Content's template reference.
Mailchimp: Ping (Health Check)
Mailchimp's documented API health check: confirms the API key and its data center are wired correctly without returning any account data. Returns data.health_status on success; a bad key returns a 401. Use this as the first node when debugging a Mailchimp connection.
Mailchimp: Search Members
Search for contacts across the whole account (or one audience) by name, email, or other profile text. Returns exact_matches and full_search result groups, each holding member objects. Handy when an automation has an email but not the audience id.
Mailchimp: Search Tags
Search an audience's tags by name, or list every tag on the audience when the name is left blank. Returns data.tags[] with id and name.
Action nodes 17
Mailchimp: Add Member
Add a NEW contact to an audience. Fails with a 400 if the email already exists in the audience; use Mailchimp: Add or Update Member (upsert) when the contact may already be there. Status 'pending' sends a confirmation email (double opt-in); 'subscribed' adds them directly and requires that you already have their consent.
Mailchimp: Add or Remove Member Tags
Add and/or remove tags on one contact in a single call, looked up by email address. Each tag entry sets status active (add) or inactive (remove); a tag that does not exist yet is created when added. Fully reversible by flipping the statuses back. Returns 204 with an empty body.
Mailchimp: Add or Update Member (Upsert)
Add a contact if the email is new to the audience, or update them if it already exists (Mailchimp's PUT upsert). The idempotent workhorse for sync automations: safe to run repeatedly for the same address. The email field drives both the lookup hash and the stored email_address.
Mailchimp: Add/Remove Segment Members (Batch)
Batch add and/or remove audience members in a STATIC segment by email address. The response reports members_added, members_removed, and per-email errors (e.g. addresses that are not in the audience). Reversible: run again with the lists swapped.
Mailchimp: Archive Member
Archive a contact by email address (Mailchimp's DELETE on a member). This is the RECOVERABLE removal: the contact's history is kept, they stop counting toward the audience, and re-adding the same email (e.g. via the upsert node) restores them. Mailchimp's permanent PII delete is deliberately not offered as a node. Returns 204 with an empty body.
Mailchimp: Cancel Campaign Send (Pro Only)
Emergency stop: cancel a campaign that is CURRENTLY SENDING. Documented as included with Mailchimp Pro only; other plans get an error. The stop is permanent: a canceled campaign cannot resume, so recipients already processed keep the email and the rest never get it. Returns 204 with an empty body.
Mailchimp: Create Audience
Create a new audience (list). Mailchimp requires the sender contact block and campaign defaults up front because they appear in the footer of every email sent to the audience. Note that most plans cap the number of audiences; reusing one audience with tags is Mailchimp's own recommendation.
Mailchimp: Create Campaign (Draft)
Create a campaign DRAFT. Nothing is emailed by this node: the campaign sits in save status until content is set and a separate send or schedule node fires it. The returned data.id feeds Set Campaign Content and the send/schedule nodes.
Mailchimp: Create Static Segment
Create a STATIC segment (fixed membership you control, the same mechanism behind tags) in an audience, optionally seeding it with member emails. Emails that are not already audience members are skipped by Mailchimp and reported in the response. This node always sends static_segment, so it creates static segments only; rule-based saved segments are built in the Mailchimp UI.
Mailchimp: Schedule Campaign (Sends Real Email at the Scheduled Time)
Schedule the campaign to SEND REAL EMAIL to its full audience at the given UTC time. Flagged destructive because it commits an actual send; the undo is Mailchimp: Unschedule Campaign, which works only until the send time arrives. Mailchimp requires the time to fall on a quarter hour (:00, :15, :30, :45). Returns 204 with an empty body.
Mailchimp: Send Campaign (Sends Real Email)
SENDS THE CAMPAIGN NOW to its entire selected audience or segment. This delivers real email to real recipients immediately and cannot be undone once sending completes (cancel-send exists only on Mailchimp Pro, and only while the send is in flight). Verify the draft with Get Campaign and Send Test Email first. The campaign must have content and complete settings or Mailchimp returns a 400. Returns 204 with an empty body on success.
Mailchimp: Send Test Email
Send a TEST version of the campaign to the listed addresses only. This is the safe way to preview a campaign from an automation before the real send, but it does deliver actual email to those test inboxes, so point it at your own addresses. Returns 204 with an empty body.
Mailchimp: Set Campaign Content
Set a draft campaign's content: raw HTML (Mailchimp auto-generates the plain-text version unless you provide one), or a template reference via extra_body, e.g. {"template": {"id": 2000123, "sections": {"body": "<p>Hello</p>"}}}. Run this between Create Campaign and Send/Schedule.
Mailchimp: Unschedule Campaign
Cancel a SCHEDULED campaign that has not started sending yet, returning it to draft. This is the safety valve for the schedule node; it cannot stop a campaign that is already sending. Returns 204 with an empty body.
Mailchimp: Update Audience
Update an audience's settings. Only the fields you fill are changed; everything else keeps its current value. Use extra_body for other documented settings such as contact or double_optin.
Mailchimp: Update Campaign Settings
Update a draft campaign's settings (subject line, from name, reply-to, title) and/or its recipients. Only the objects you fill are sent; within settings, include every field you want to keep, as Mailchimp replaces the provided object's values.
Mailchimp: Update Member
Update an EXISTING contact's profile or status by email address. Only the fields you fill are changed. Fails with a 404 if the email is not in the audience; use the upsert node when it might not be. Setting status to unsubscribed is how an automation opts a contact out.
Connecting Mailchimp takes one credential
Mailchimp issues API keys under Account > Extras > API keys, on every plan. A key belongs to your account's data center and ends with its name (a key ending in us21 lives at us21.api.mailchimp.com), which is why there is no server or data center field to fill in: the connector reads the data center from the key's own suffix and authenticates the way Mailchimp documents. Store the key exactly as issued, suffix and all.
In Mailchimp, open Account > Extras > API keys and create a new key. Copy it exactly as issued, including everything after the last hyphen: that suffix names your data center.
In Mattering Automations, open Connectors, click Add Connector, choose Mailchimp, and create a credential with the key.
Click Test Connection. Mattering derives the data center from the key's suffix and runs Mailchimp's own ping health check against it, confirming the key and the server routing in one call without returning any account data.
All 39 Mailchimp nodes appear in the canvas palette. Run Mailchimp: List Audiences first: the audience ids it returns feed nearly every other node.
Common uses for the Mailchimp MCP
Form leads that land subscribed and tagged
Mailchimp: Add or Update Member (Upsert) takes a plain email address plus merge fields and is safe to run repeatedly for the same contact, and Mailchimp: Add or Remove Member Tags applies the campaign source or interest as tags, creating any tag that does not exist yet. No hashes and no exists-checks required: the upsert is idempotent by construction, which is exactly what a lead capture loop needs.
Contact questions an agent can answer
Mailchimp: Get Member returns one contact's status, merge fields, tags, and engagement stats from a plain email address, Mailchimp: Search Members finds a contact when the audience is unknown, and Mailchimp: List Member Tags shows how they are labeled. All read-only, which makes them the safest Mailchimp surface to hand an assistant.
Campaign drafts assembled and previewed without sending
Mailchimp: Create Campaign (Draft) creates a campaign that sits in save status and emails nobody, Mailchimp: Set Campaign Content fills in the HTML or a template's editable sections, and Mailchimp: Send Test Email delivers a preview to the addresses you list and no one else. The full-audience send stays a separate, flagged step for a person or a gated branch to fire.
Reports that become tasks and records
Run Mailchimp: List Campaign Reports on a schedule and route the numbers into Mattering Productivity tasks or a Mattering database: emails sent, opens, clicks, bounces, and unsubscribes per campaign, with Mailchimp: Get Campaign Report adding the full detail for any single send.
Engagement follow-up from real click data
Mailchimp: Get Campaign Email Activity lists each recipient's opens, clicks, and bounces with timestamps, and Mailchimp: Get Campaign Click Details shows which links in the email actually performed. Together they feed a clicked-but-did-not-convert follow-up or an engagement score without exporting anything from the dashboard.
Segment housekeeping in batches
Mailchimp: Create Static Segment builds a fixed-membership segment, optionally seeded with member emails, and Mailchimp: Add/Remove Segment Members (Batch) moves members in and out in one call, reporting per-email errors. Mailchimp: List Segments also exposes tag membership counts, since tags are static segments under the hood.
Example: A form lead lands subscribed and tagged, and no path in the flow can send a campaign
Built on the Automations canvas in a few minutes, or described in plain language to Matter and built for you.
Trigger: a form submission delivers an email address, a first name, and a product interest.
Mailchimp: Get Member looks up the address in the audience; a 404 tells the workflow this is a brand new contact, which can branch a welcome path.
Mailchimp: Add or Update Member (Upsert) writes the contact with their name in the merge fields. The node takes the plain email and computes Mailchimp's subscriber hash itself, so the same step is safe for new and existing contacts alike.
Mailchimp: Add or Remove Member Tags applies the product interest as a tag; a tag that does not exist yet is created on add.
A record lands in a Mattering database so the team sees the signup next to the rest of the pipeline.
Nothing in this flow can email the audience: the only nodes that deliver to one are Mailchimp: Send Campaign (Sends Real Email) and Mailchimp: Schedule Campaign (Sends Real Email at the Scheduled Time), and neither appears here.
Mailchimp MCP questions, answered
What Mailchimp operations are supported?
39 nodes on the Marketing API v3: audiences (list, get, create, update), members (add, upsert, update, archive, search, plus a status-filtered list), member tags, static segments with batch add and remove, campaigns (draft, settings, content, test send, send, schedule, unschedule, and a Pro-only cancel), templates and their default section content, reports (per-campaign summary, per-recipient email activity, per-link click details), merge fields, and the documented ping health check. Deliberately not shipped: permanent member deletes and audience deletes, Batch Operations, Customer Journeys, e-commerce, and webhook management.
Does this work with Claude, ChatGPT, or other AI assistants?
Yes. Mattering exposes these nodes over MCP, an open protocol for connecting AI assistants to tools, so any MCP-capable assistant, including Claude and ChatGPT, can connect to your workspace and use them. Matter, the assistant built into the platform, uses the same nodes natively.
Can this connector send real email by accident?
It is built so that it cannot do so silently. Campaigns are created as drafts and stay in save status through content and settings changes; nothing in that path emails anyone. Mailchimp: Send Campaign (Sends Real Email) delivers to the entire selected audience immediately and cannot be undone once sending completes, and Mailchimp: Schedule Campaign (Sends Real Email at the Scheduled Time) is flagged just as loudly because it commits a real send on a timer; its undo, Mailchimp: Unschedule Campaign, works only until the send time arrives. Put a condition, an approval step, or a manual run in front of both. Mailchimp: Send Test Email is the safe preview, though the listed test inboxes do receive actual mail.
Can this permanently delete a subscriber?
No, by design. Mailchimp's permanent delete destroys all of a contact's personally identifiable information and permanently blocks the same address from being re-imported, which makes it a console-grade decision rather than an automation step, so it is not shipped as a node. Mailchimp: Archive Member is the removal that is offered: the contact stops counting toward the audience, their history is kept, and re-adding the same email restores them. Deleting a whole audience is omitted for the same reason.
Why is there no server or data center field?
Because the key already says. Mailchimp routes every API call to a data-center-specific server, and the data center's name is the suffix on the API key itself: a key ending in us21 belongs to us21.api.mailchimp.com. The connector reads that suffix and derives the server, so the only thing to configure is the key, stored exactly as issued. The connection test then runs Mailchimp's own ping health check against the derived server, proving the key and the routing in one call.
What is the subscriber hash, and do I need to compute it?
You never touch it. Mailchimp's API addresses a contact by the MD5 hash of their lowercased email address rather than by the address itself. Every member node here takes a plain email field and computes that hash for you, and the upsert node uses the same single field for both the lookup and the stored address, so a workflow only ever handles the email a person actually typed.
Can a Mailchimp event trigger a workflow?
Not as a trigger node in this connector: there is no inbound Mailchimp trigger, and webhook management is not part of this node set. The honest pattern today is polling: run Mailchimp: List Campaign Reports or Mailchimp: List Members on a schedule, filter for what changed, and act on it.
Should I use Add Member or the upsert?
Use the upsert unless you specifically want new-only behavior. Mailchimp: Add Member is a strict create that fails with a 400 when the email already exists in the audience, which makes it the right node when a duplicate should stop the flow. Mailchimp: Add or Update Member (Upsert) adds the contact if new and updates them if not, so it is the idempotent workhorse for sync loops. Either way, adding with status pending sends the double opt-in confirmation email, while status subscribed adds directly and requires that you already have the contact's consent.
Put Mailchimp to work inside your workspace
Connect once, then use every node in visual automations and AI agent workflows across the Mattering platform.
All product names, logos, and brands are property of their respective owners and are used for identification purposes only. Use of these names, logos, and brands does not imply endorsement or affiliation. Mailchimp is a product of its respective owner; Mattering is an independent platform.