Ask how the last Moosend newsletter performed, and whether a subscriber is still on a list.
Connect Moosend, now Sitecore Send, with an API key and Memtro reads mailing lists with active, unsubscribed, bounced and removed member counts, a list's subscribers by status, one subscriber by email, and campaigns with sends, opens, clicks, bounces, unsubscribes and complaints. It reads on demand and there is no hourly sync. When asked, and once an administrator has granted the action by name, it can add, unsubscribe or remove subscribers, create lists, create or clone draft campaigns, send a test, send a campaign to every active subscriber, which cannot be recalled, and permanently delete a campaign.
Ask in plain English from chat, your editor, a scheduled job or your own agent. The model picks the right Moosend tool, reads what it needs, and answers with the source cited.
These tools change something in Moosend. The model is told to use them only when you ask for exactly that, and an administrator grants each one by name to the teams that may use it; a personal connection acts only after its owner allows it.
Once Moosend is connected, these are the kinds of things people ask. Plain questions, no syntax. If the answer lives partly in another system you have connected, Memtro looks there too.
Moosend + MemtroHow did last month's newsletter do on opens and clicks?
Is dan@northwind.example still subscribed to the customers list?
Which campaign had the most bounces this quarter?
Unsubscribe priya@brightwave.example from the product updates list
Send a test of the June newsletter draft to me
The marketing lead asks how Tuesday's newsletter went. Memtro reads the campaign's result summary: 4,120 sends, 1,610 opens, 233 clicks, 18 bounces and 9 unsubscribes, and compares it with the previous campaign's figures from the list.
Support passes on that Priya Sharma at Brightwave Ltd no longer wants product updates. Dan Fletcher asks Memtro to take her off that list, and Memtro unsubscribes her address from the product updates list in Moosend, so its campaigns stop reaching her and nothing is sent to her.
The teams that lean on Moosend most, a question each of them asks, and what they connect beside it.
A record in Moosend is rarely the whole story. Connect the systems that hold the rest and Memtro checks them together, then remembers what it learned so the next question starts further along.
Using something else for the same job, or both? Each connector has its own tools; connect as many as you like.
ActiveCampaign
Klaviyo
MailerLite
GetResponse
Instantly
lemlist
Drip
Omnisend
Mailjet
Smartlead
Iterable
Dotdigital
Flodesk
LoyaltyLion
Benchmark Email
Braze
Sender
Rewardful
Mailshake
SurveySparrow
RetentlyIn Moosend find or generate the API key under Settings → API key. The exact menu and which plans include the API were not confirmed
The key acts for the whole account, so anyone holding it can send campaigns: keep it for Memtro alone
In Memtro open Connections → Moosend, paste the API key and connect
Ask how the last newsletter performed
Chat in the dashboard, the OpenAI-compatible API, scheduled jobs, and any MCP client: Claude Code, OpenCode, Cursor, Claude Desktop. The Moosend tools are the same everywhere.
Only when you ask, and only what it has been granted: add a new subscriber to a mailing list (refused when already a member); unsubscribe a subscriber from a mailing list; remove a subscriber from a mailing list; create a mailing list; create a draft campaign; clone a campaign as a new draft; send a test of a campaign; send a campaign; delete a campaign. Every other tool reads, searches or lists. The Connections page labels the tools that act, an administrator grants each one by name to the teams that may use it, and a personal connection acts only after its owner allows it.
A personal connection serves only your own requests. A shared connection serves the organisation: everyone, or only the teams an admin chooses. Admins can always add shared connections; other members need the permission.
Credentials are encrypted at rest. Tool results are cached briefly so agent loops do not repeat identical calls, and the facts the model extracts are saved to your organisation's memory with provenance (system, record and link) so they can be checked and superseded.
API key. In Moosend find or generate the API key under Settings → API key. The exact menu and which plans include the API were not confirmed.
Seven-day free trial, then one monthly price per organisation. Connectors, jobs and memory are never metered.
Sign in, add a provider key, create an API key and point your tools at Memtro. It takes about five minutes.
7-day free trial · card on file, nothing charged until it ends · cancel any time