Why mail to an address is bouncing, and which Mailgun sending domains are verified.
Connect Mailgun with the private API key and your region, and Memtro reads the account's sending domains with their state, the addresses each domain has bounced with the SMTP code and error, and the mailing lists with access level and member count. It reads on demand and there is no hourly sync. When you ask, and once an administrator has granted the action by name, it can send an email, manage mailing lists and their members, clear a bounce, record an unsubscribe and store a template. A sent email reaches its recipients at once and cannot be recalled.
Ask in plain English from chat, your editor, a scheduled job or your own agent. The model picks the right Mailgun tool, reads what it needs, and answers with the source cited.
These tools change something in Mailgun. 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 Mailgun for you. Each event can start a job, with the event as its input. Mailgun signs every delivery, and one whose signature does not check out is refused before it is read.
Events and webhooksOnce Mailgun 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.
Why is priya@acme.com not getting our emails?
Is our sending domain verified?
Which addresses has mg.brightwave.co.uk bounced this week?
How many members are on the customers mailing list?
Clear priya@acme.com from the bounce list now her mailbox is fixed
Support hears that a customer at Brightwave Ltd has had no password reset emails. They ask Memtro, which reads the sending domain's bounces and finds the address with a 550 code and a mailbox-not-found error from last Tuesday, so support asks for a corrected address.
Dan Fletcher at Northwind says his mailbox is fixed, and support asks Memtro to let mail through again. Memtro checks the bounce list, finds his address, and clears it, so the domain sends to him again until it next bounces.
The teams that lean on Mailgun most, a question each of them asks, and what they connect beside it.
A record in Mailgun 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 app.mailgun.com open Settings → API Security and copy the Private API key, or create one, since a sending key or domain-scoped key cannot read the account
Choose the Region your domains were created in, US or EU, since a key that works but shows no domains usually means the other region
In Memtro open Connections → Mailgun, paste the Private API key, set the Region, optionally add a Default sending domain with no https://, and connect
Ask why mail to a customer's address is bouncing
Chat in the dashboard, the OpenAI-compatible API, scheduled jobs, and any MCP client: Claude Code, OpenCode, Cursor, Claude Desktop. The Mailgun tools are the same everywhere.
Only when you ask, and only what it has been granted: send an email from a Mailgun sending domain; create a Mailgun mailing list; delete a Mailgun mailing list; add a member to a Mailgun mailing list; rename, unsubscribe or resubscribe a Mailgun list member; remove a member from a Mailgun mailing list; clear an address from a Mailgun domain's bounce list; record an address as unsubscribed on a Mailgun domain; store a new Mailgun email template. 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.
Private API key and region. In app.mailgun.com open Settings → API Security and copy the Private API key, or create one, since a sending key or domain-scoped key cannot read the account.
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 Mailgun 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
