Did our password reset email reach the customer, and if not, why?
MailerSend connects Memtro to your transactional email. It reads the account's plan, quota and limits, sending domains with their DNS status, and the sending log for a domain with sender, recipient, subject, status, opens and clicks, and why an email was rejected. It also reads one email's delivery events, templates and scheduled messages. When asked, and once an administrator has granted the action by name, it can send an email, which reaches real people, cancel a scheduled one, manage templates and add addresses to a suppression list. Message bodies are never returned.
Ask in plain English from chat, your editor, a scheduled job or your own agent. The model picks the right MailerSend tool, reads what it needs, and answers with the source cited.
These tools change something in MailerSend. 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.
Turn events on in the connection's Events tab on the Connections page, choose the kinds you want, and Memtro registers its address with MailerSend for you. Each event can start a job, with the event as its input. MailerSend signs every delivery, and one whose signature does not check out is refused before it is read.
Events and webhooksOnce MailerSend 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.
MailerSend + MemtroDid the password reset email to priya@acme.example arrive?
Why were emails rejected on our domain yesterday?
How many emails have we sent this cycle against our limit?
Is our sending domain's DKIM verified?
Add bounced@bigco.example to the blocklist
Tom Reilly, support lead at Acme Ltd, asked whether a customer's receipt email had been delivered. Memtro found the email in the sending log and listed its delivery events, which showed a hard bounce, with the reason MailerSend gave.
Maya Okafor, product engineer at Northwind, asked Memtro to stop sending to an address that kept bouncing. Memtro added it to the hard bounces suppression list in MailerSend, so later emails to it are not sent. Removing it again has to be done in MailerSend.
The teams that lean on MailerSend most, a question each of them asks, and what they connect beside it.
A record in MailerSend 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.
AgentMail
Fireflies.ai
SendGrid
Avoma
Missive
tl;dv
Grain
Fathom Video
ClickSend
OneSignal
Bird
MeetGeek
Sinch
Telnyx
Textmagic
SMTP2GO
InfobipIn MailerSend, open Integrations → API tokens → Generate new token, name it Memtro and choose the domain.
Choose custom access: Domains and Activity read for the log, Templates full to list templates, and Email or Suppressions full only if Memtro may send or suppress. Copy the token, which is shown once.
In Memtro, open Connections → MailerSend and paste it into API token.
Ask your first question: did the password reset email to priya@acme.example arrive?
Chat in the dashboard, the OpenAI-compatible API, scheduled jobs, and any MCP client: Claude Code, OpenCode, Cursor, Claude Desktop. The MailerSend tools are the same everywhere.
Only when you ask, and only what it has been granted: send an email (billed against the plan, reaches real people); cancel a scheduled email; create an email template; edit an email template; delete an email template; add addresses to a suppression list (they stop receiving mail). 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 token. In MailerSend, open Integrations → API tokens → Generate new token, name it Memtro and choose the domain.
Yes. Turn events on in the connection's Events tab on the Connections page, choose the kinds you want, and Memtro registers its address with MailerSend for you. A job set to start "When an event arrives" then runs once for each matching event, with the event as its input. The run treats the event as outside data, never as instructions, and anything the run remembers is kept as unverified.
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
