This guide is for marketers, agencies and developers who already use the official Mailercloud MCP server and want more from it: chaining steps, working precisely with IDs and dry runs, and combining Mailercloud with other connectors in the same chat. For the full list of tools, see the Mailercloud MCP tool reference.
Last updated: 26 October 2026
Use IDs once you have them. Every Mailercloud list, campaign, template, segment and contact has an ID, shown in the assistant's answers. "Use list ID AbC123" is never ambiguous; "the newsletter list" can be.
Ask for a dry run. Add "dry run first" to a create or update request. You see exactly what would be saved, and nothing changes.
Approve previews yourself. Sending, scheduling, deleting, blocking addresses, removing tags, pausing webhooks, editing saved designs and changing segments always show a preview. Reply yes in your next message; don't tell the assistant to skip previews.
Read results back. After a change, ask the assistant to fetch the item again ("show me the segment now") to confirm it saved as you meant.
Yes. Ask for the whole job in one message; the assistant does the steps in order and stops for your approval where needed.
Re-engage inactive subscribers
"Make a segment of contacts on the Newsletter list who haven't opened any of the last five campaigns. Then draft a win-back campaign to that segment with the subject 'Still want to hear from us?', one button to https://www.example-shop.com/preferences, and our address in the footer. Audit the draft and send me a test."
Repeat a winning campaign
"Find my best campaign of the last 90 days by click rate. Make a new draft from the same template for the Customers list, with a fresh subject line. Show me three subject options first."
Weekly report
"Compare the campaigns sent this week with last week: opens, clicks, unsubscribes and bounces. Show a table, flag anything worse than usual, and suggest one test for next week."
Mailercloud segments combine rules with "match all" or "match any", across one or more lists or your whole audience. Rules can use:
Tags: tagged or not tagged, with any or all of the tags you name.
Campaign activity: opened, clicked, not opened or not clicked, for example in the last month or the last five campaigns.
Contact details: built-in fields such as country, city or job title (equal to, contains, is known and so on), and mailbox provider such as Gmail.
To change one part of a segment, name only that part: "switch the VIP segment to match any" keeps its rules and lists. Replacing the rules shows the old and new rules before saving. Segments on custom fields are built in Mailercloud under Audience > Segments for now.
Yes, in any saved drag-and-drop template or draft campaign, including ones you built yourself in the editor:
"List the blocks in my Diwali draft." You get each row and block with its text, buttons and images.
"Change the second button's link to https://www.example-shop.com/new and replace the hero image with https://cdn.example.com/hero.png."
Approve the preview, then open the email in Mailercloud to check it.
Images must be at a public https address. The assistant can copy one from a public link into your Mailercloud image library; for a file on your computer, upload it in the editor's Image block.
Where | Write it like |
Campaigns and templates |
|
Transactional and personalised API sends |
|
An empty field prints nothing, so avoid a merge tag on its own in a heading. Before saving, Mailercloud checks for real links, alt text, a postal address, an unsubscribe link and a size under 102 KB.
Yes, if you use Mailercloud's API Platform: for example an order update, or one email to a short list of recipients with their own values.
"Send a personalised email from [email protected] to these three customers, with subject 'Your order {{order_id}} has shipped' and their order numbers: …"
You see the recipients, sender and content before anything is sent. The sender must be on a verified domain. For marketing to a list, use a campaign instead.
Yes. Webhooks send Mailercloud events, such as opens, clicks, unsubscribes or new contacts, to your own system or to tools like Zapier and Make.
"Create a webhook that sends unsubscribes to https://hooks.example.com/mc, then send a test event."
"List my webhooks and pause the one that's failing."
Yes. Your AI app can use several connectors in one chat:
Google Sheets or Drive: "Read the sign-ups in my 'Webinar leads' sheet and add them to the Webinar list in Mailercloud, tagged webinar-oct."
Slack: "Summarise this week's Mailercloud campaign results and post them to #marketing."
Your CRM or store: "Find customers who bought in the last 30 days and tag them as recent-buyers in Mailercloud."
Web research: "Look up next month's UK holidays, suggest a campaign calendar, then draft the first one in Mailercloud."
Only add contacts who agreed to hear from you, and check the preview before you approve.
Give the goal, the audience and the deadline: "for the Customers list, before Friday".
Ask for a table when comparing campaigns or contacts.
Say "don't change anything yet" when you only want analysis.
For thousands of contacts, use Import in Mailercloud rather than chat.
If the assistant picks the wrong item, correct it with the exact ID.
Automations can be viewed from chat but are built in Mailercloud.
Senders, reply addresses and webforms are added in Mailercloud; the assistant can list them.
Campaigns can't be deleted from chat, and billing and account settings stay in the app.
New contacts and changes can take a few minutes to show up in lookups and lists.
The connector acts with the access of the API key you connected. Use a separate key per app, and delete a key to stop its access.
If you ask for something the connector can't do, the assistant can pass the request to the Mailercloud team so we know what to add next. More: the official guide · setup for each AI app · Help: [email protected]
