CRM & email integration
MailPoet MCP
MailPoet keeps subscribers, their list and tag memberships, custom fields, newsletters and automations in its own tables. WP MCP Pro reads all of it (a setup summary, subscribers filtered by list, tag and status, one subscriber with its lists, tags and field values, lists, tags, custom fields, campaigns and automations) and runs every write through MailPoet's public API, so its confirmation emails, welcome emails, hooks and automation triggers run. A new subscriber's status follows MailPoet's own sign-up confirmation setting, an email that already belongs to a subscriber is refused rather than merged, and because MailPoet's own subscribe call would resubscribe someone who had unsubscribed, a contact that is suppressed or has left one of the lists is refused before it runs. It tags and untags subscribers, adds and removes them from the default lists (MailPoet's WordPress and WooCommerce user lists are read-only), manages lists and tags, imports subscribers, and creates, updates, duplicates, tests and sends standard newsletters whose body is the op's HTML with MailPoet's unsubscribe footer added. A delete moves the subscriber to MailPoet's trash the way its admin does. Every write is snapshotted as a CRM rows image for an exact rollback, except a send, which cannot be unsent; sending is off until a site enables it.
In practice
How MailPoet work goes with an agent.
MailPoet's data model has quirks an agent has to respect. A subscriber has one of five statuses (subscribed, unconfirmed, unsubscribed, inactive, bounced), list membership has its own status per list, and the WordPress Users and WooCommerce Customers lists are MailPoet's own and not writable. Custom fields are named cf_ plus an id, and a newsletter has no title, only a subject. WP MCP reads those tables and writes through MailPoet's public API, so confirmation emails, welcome emails and automation triggers run exactly as they do from MailPoet's forms.
How are new MailPoet subscribers confirmed on this site, and how many are unconfirmed?
Runs mailpoet-summary for counts by status, lists, tags, newsletters and automations and the opt-in rule. Nothing is written, and a new subscriber's status follows MailPoet's own sign-up confirmation setting.
List subscribers on list 3 who are still unconfirmed.
Runs mailpoet-list-contacts with list_id 3 and status unconfirmed, up to 100 per page. mailpoet-get-contact reads one with its lists, tags and cf_ field values.
Add subscriber 88 to the Weekly Digest list and tag them VIP.
Runs mailpoet-update-contact-lists and mailpoet-update-contact-tags, each snapshotted. The list add is refused before MailPoet is called if the subscriber is suppressed or has left that list, since MailPoet would resubscribe them.
Create a newsletter from this HTML and send a preview to me.
Runs mailpoet-create-campaign, which saves a standard newsletter with the HTML as its body and MailPoet's unsubscribe footer added, then mailpoet-send-test-campaign to the current user only. The test cannot be unsent.
What your AI can do
Real MailPoet operations, every write reversible.
- Read subscribers, lists, tags, custom fields, newsletters and automations
- Create, update and delete (trash) a subscriber, confirmation rules respected
- Tag and untag subscribers and add or remove them from default lists
- Manage lists and tags, and import subscribers
- Create, update, duplicate, test and send or schedule a standard newsletter
- Set an automation's status
- Roll back any write exactly, except a send, which cannot be unsent
Example prompts
Example MailPoet prompts.
Add these new subscribers to the Weekly Digest list.
Draft a newsletter from this HTML and send me a preview.
Tag everyone on the Customers list with "VIP".
Under the hood
The MailPoet calls, under the hood.
plugin-data-read({ integration: "mailpoet", operation: "mailpoet-list-contacts", args: { list_id: 3, status: "subscribed" } }), queried from MailPoet's tables
plugin-data-write({ integration: "mailpoet", operation: "mailpoet-send-campaign", args: {…} }), off until opt-in; cannot be unsent
Safety and access
What can be undone on MailPoet, and what costs what.
Recoverable on MailPoet
- Subscriber, list, tag, newsletter-draft and automation-status writes are snapshotted as CRM rows images, and rollback-operation restores them exactly.
- A subscriber delete goes to MailPoet's trash, as its admin does, and rollback puts the subscriber back with their memberships.
- rollback-session undoes a whole mailpoet-import-contacts run.
- Rollback never sets anyone back to a mailable status.
MailPoet limits and opt-ins
- mailpoet-send-campaign is off until a site enables it with the wpmcp_enable_crm_send filter, confirms the recipient count first, and cannot be undone.
- mailpoet-set-automation-status takes active, deactivating or draft. MailPoet cancels pending runs when an active automation goes straight to draft, and an undo does not bring those runs back.
- Only the default lists can be written. The WordPress Users and WooCommerce Customers lists stay read only.
- mailpoet-import-contacts takes up to 100 per call, and an existing email is refused, not merged, unless update_existing is passed.
Free or Pro: MailPoet support is Pro, on the plugin-data pair. Reads and the everyday writes need only a licence and MailPoet's own capabilities, such as mailpoet_manage_subscribers, mailpoet_manage_segments and mailpoet_manage_emails. Sending is the one opt-in, behind wpmcp_enable_crm_send. Deleting a subscriber, a list or a tag is destructive and asks for confirm:true.
Part of WP MCP Pro
The MailPoet integration is part of WP MCP Pro.
One Pro licence unlocks the MailPoet tools and every other Pro integration on this site: Elementor deep editing, the other page builders, the forms adapter pack and more, 133 Pro tools in all. The free plugin still covers the rest of WordPress and the full snapshot and undo engine, so you can try the safety model before you buy.
Frequently asked
MailPoet MCP: questions, answered.
Will the MailPoet integration resubscribe people who opted out?
No. MailPoet's own subscribe call would, so this integration refuses a contact that is suppressed or has left one of the lists before it runs. A new subscriber's status follows MailPoet's own sign-up confirmation setting.
Which lists can it write to?
The default MailPoet lists. The WordPress Users and WooCommerce Customers lists are MailPoet's own and stay read-only, so membership in them is never changed here.
What does the newsletter body look like?
A body is the HTML you pass, written into one text block of a standard newsletter, with MailPoet's unsubscribe footer added unless your HTML already has an unsubscribe link. Other newsletter types, such as welcome or automation emails, are not created here. MailPoet names a newsletter by its subject, so there is no separate title.
What happens when I delete a subscriber?
The subscriber is moved to MailPoet's trash, the way MailPoet's own admin deletes one, not erased. It is snapshotted, so rollback-operation restores the subscriber with their list and tag memberships. Deleting is a destructive op and needs confirm:true, as does deleting a list or a tag.
Can the MailPoet integration read subscribers who sit on the WordPress Users list?
Yes, reads include them, and list counts show them. Writes are different: MailPoet's WordPress Users and WooCommerce Customers lists are its own, so adding or removing a contact there is not offered. Writes go to default lists, plus tags, which are separate from lists.
How are custom fields handled?
mailpoet-list-custom-fields returns the definitions, keyed by the name create-contact and update-contact accept, which MailPoet's API calls cf_ plus the field id. An unknown field is refused with unknown_field and the list of valid ones, before any snapshot or write.
Related integrations
More integrations for the same agent.
MCP for FluentCRM
ProCRM & email, 2 tools.
MCP for FunnelKit
ProFunnels, 2 tools.
MCP for WooCommerce
FreeE-commerce, 9 tools.
MCP for Forminator
FreeForms, 5 tools.
MCP for WP Mail SMTP
FreeOperations, 2 tools.
MCP for Elementor
ProPage builders, 14 tools.
Browse the full Integrations hub, or read more on the WordPress MCP plugin.