Was that email delivered, and how did the last campaign do?
Mailtrap connects Memtro to your email delivery and testing. It reads sent-email logs with status and delivery events, sending stats, sending domains and their verification, suppressed addresses, campaigns and their stats, marketing contacts and lists, templates, sandbox test inboxes and inbound inboxes. When asked, and once an administrator has granted the action by name, it can send email, send a test into a sandbox, reply to or forward an inbound message, manage contacts, lists, templates and suppressions, and start, schedule, cancel or stop a campaign. 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 Mailtrap tool, reads what it needs, and answers with the source cited.
These tools change something in Mailtrap. 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 Mailtrap for you. Each event can start a job, with the event as its input. Mailtrap signs every delivery, and one whose signature does not check out is refused before it is read.
Events and webhooksOnce Mailtrap 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.
Was the password reset to priya@acme.example delivered?
What was our bounce rate by mailbox provider last week?
How did the October newsletter campaign perform?
Is our sending domain verified?
Cancel the scheduled November newsletter
Dan Fletcher, support engineer at Acme Ltd, asked whether a customer's password reset had gone out. Memtro found it in the sent-email logs with status not_delivered and a bounce event, and named the address as suppressed after a hard bounce.
Priya Sharma, marketing manager at Northwind, spotted a wrong date in the scheduled newsletter and asked Memtro to stop it. Memtro cancelled the scheduled campaign in Mailtrap, which put it back to draft. Nobody was emailed.
The teams that lean on Mailtrap most, a question each of them asks, and what they connect beside it.
A record in Mailtrap 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
MailerSend
InfobipIn mailtrap.io, open Settings → API Tokens → Add Token and name it Memtro.
Grant access to the account, sending domains, sandboxes or projects it should see: Viewer to read, Admin for sends, suppressions, contacts, templates and campaign changes. Copy the token.
In Memtro, open Connections → Mailtrap and paste it into API token.
Ask your first question: was the password reset to priya@acme.example delivered?
Chat in the dashboard, the OpenAI-compatible API, scheduled jobs, and any MCP client: Claude Code, OpenCode, Cursor, Claude Desktop. The Mailtrap tools are the same everywhere.
Only when you ask, and only what it has been granted: send an email through the transactional or bulk stream (billed, reaches real recipients); send a test email into a sandbox inbox (captured, not delivered); reply to, reply-all or forward an inbound message (reaches real recipients); create, update or delete a marketing contact; create a contact list; suppress an address so no more mail goes to it, or lift a suppression; create, update or delete an email template; start, schedule, cancel or terminate an email 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 token. In mailtrap.io, open Settings → API Tokens → Add Token and name it Memtro.
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 Mailtrap 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
