Mailgun MCP server
Mailgun in any MCP client, through Memtro: Mailgun does not publish this server. Memtro's Mailgun connector reads Mailgun through its API with the credentials you connect, and one endpoint hands those tools, every other system you connect and Memtro's memory tools to Claude Code, Cursor, Claude Desktop or anything else that speaks Streamable HTTP, as you.
What the model can do
Mailgun: the account's sending domains with their state, the addresses each domain has bounced with the error and date, and its mailing lists. Can send an email, create or delete a mailing list, add, update or remove a list member, clear a bounce, record an unsubscribe, and store a template.
Reads
mailgun_list_domainsThe Mailgun account's sending domains: name, state (active, unverified, disabled), type (custom or sandbox), whether disabled, and when created.mailgun_list_bouncesAddresses a Mailgun sending domain has bounced, and so will not send to again: address, SMTP code, error and when.mailgun_list_mailing_listsThe account's Mailgun mailing lists: address, name, description, access level (readonly, members, everyone), member count and when created.
Acts, when you ask
These change something in Mailgun. The model is told to use them only when you ask for exactly that, and each one is granted by name: per team on a shared connection, by the owner on a personal one.
mailgun_send_emailSends an email through Mailgun from one of the account's sending domains; every to, cc and bcc recipient receives it (at send_at if given…mailgun_create_mailing_listCreates a Mailgun mailing list at an address on one of the account's domains; mail sent to that address later goes to every subscribed member.mailgun_delete_mailing_listPermanently deletes a Mailgun mailing list and its member list; mail to the list address stops being delivered to them, and it cannot be undone.mailgun_add_list_memberAdds one person to a Mailgun mailing list, subscribed unless subscribed is false; from then on they receive whatever is sent to the list.mailgun_update_list_memberRenames a Mailgun list member or unsubscribes or resubscribes them on that list; nothing else about them changes.mailgun_remove_list_memberRemoves one person from a Mailgun mailing list, so they stop receiving its mail; their name and per-member values on that list are lost.mailgun_remove_bounceClears one address from a Mailgun domain's bounce list, so the domain sends to it again until it bounces again.mailgun_add_unsubscribeRecords one address as unsubscribed on a Mailgun domain, so the domain stops sending to it: all mail by default, or only mail carrying the given tag.mailgun_create_templateStores a new email template on a Mailgun domain (with content, as its active version)…
Connect it
First connect Mailgun on Dashboard → Connections, then add Memtro to your client once. The Mailgun tools appear alongside the tools of everything else you have connected; nothing is configured per connector.
Claude Code
The Memtro plugin registers the server and a skill for when to use it; the tools are then available in every session.
claude plugin marketplace add memtro-org/claude-memtro
claude plugin install memtro@memtro --config api_key=sk-memtro-...Cursor
Add the server to .cursor/mcp.json in the project, or to the global file under ~/.cursor/.
{
"mcpServers": {
"memtro": {
"url": "https://platform.memtro.com/api/mcp",
"headers": {
"Authorization": "Bearer sk-memtro-..."
}
}
}
}Claude Desktop
Create a personal API key on Dashboard → Profile → API keys. In Claude Desktop add an MCP server of type HTTP with URL https://platform.memtro.com/api/mcp and the header Authorization: Bearer sk-memtro-…
OpenCode
A remote server in opencode.json.
{
"mcp": {
"memtro": {
"type": "remote",
"url": "https://platform.memtro.com/api/mcp",
"headers": {
"Authorization": "Bearer sk-memtro-..."
}
}
}
}Pi
One command: pi mcp add memtro --url https://platform.memtro.com/api/mcp --bearer-token-env-var MEMTRO_API_KEY. Tools arrive as mcp__memtro__*. The pi-memtro extension registers it for you, alongside Memtro as the model.
Any other client
Add an MCP server of type HTTP (Streamable HTTP, stateless) at https://platform.memtro.com/api/mcp with the header Authorization: Bearer sk-memtro-.... Codex, Zed, Windsurf, Cline and the SDKs all take a remote server this way.
Who may use it
The key identifies the person, and the server offers that person the tools they may use everywhere else in Memtro. A shared Mailgun connection is used by the teams an administrator granted it to, tool by tool, on the Permissions page; a personal connection is used by its owner alone, and its tools that act stay off until the owner allows them. See Teams and permissions and Connectors.
Ask it like this
- › 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
Questions
- Is this an official Mailgun MCP server?
- No. It is Memtro's MCP server with Memtro's Mailgun connector behind it: the connector reads Mailgun through its API with the credentials you connect on Dashboard → Connections, and Mailgun publishes nothing here. The same endpoint carries every other system you connect and Memtro's memory tools.
- What does it cost?
- Nothing on top of Memtro. One price per organisation by its number of users, from $50 a month for up to 10 users after a 7-day free trial, with every connector, the MCP server, jobs and memory included. You bring your own model keys.
- Can it change anything in Mailgun?
- 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. An administrator grants each acting tool by name per team, and a personal connection acts only after its owner allows it.
- Which clients work?
- Any MCP client that speaks Streamable HTTP: Claude Code, Cursor, Claude Desktop, OpenCode, Codex, Zed, Windsurf, Cline and the Anthropic and OpenAI SDKs. There is no local process to run; the server is remote and authenticated with your key.