Because the tools are generated from Mailgun's API, the coverage is unusually complete — sending is one tool among domains, routes, templates, suppression lists and analytics — so an assistant can both send mail and manage the account around it. The tradeoff is the naming: tools carry their HTTP path (post-v3-domain-messages), so the model leans on the descriptions rather than friendly names, but the analytics and suppression coverage is what a bare SMTP send cannot give you.
Mailgun's official server, generated from its API: 74 tools covering sending, domains and their tracking, webhooks, routes, mailing lists, templates, suppression lists, and analytics. Tool names follow the HTTP verb and API path (for example post-v3-domain-messages sends an email).
- Sending and retrieval: post-v3-domain-messages sends an email, get-v3-domains-domain-messages-storage_key retrieves a stored one, and post-v3-domains-domain-messages-storage_key resends it
- Domain management: get-v4-domains and get-v4-domains-name, put-v4-domains-name-verify to verify a domain, and get-v3-domains-name-sending_queues for queue status
- Tracking configured per domain — get-v3-domains-name-tracking plus put-v3-domains-name-tracking-click, -open and -unsubscribe
- Webhooks and routes: create and read domain webhooks by type, and get-v3-routes, get-v3-routes-id and put-v3-routes-id to manage inbound routing
- Deliverability hygiene: read and manage bounces, unsubscribes, complaints and whitelists (get-v3-domain-bounces, get-v3-domain-unsubscribes, get-v3-domain-complaints, get-v3-domain-whitelists) by address or in full
- Analytics and stats: get-v3-stats-total and the filtered and per-domain variants, aggregates by provider, device and country, and the v1 analytics endpoints post-v1-analytics-metrics, post-v1-analytics-usage-metrics and post-v1-analytics-logs
- Templates versioned: get and create domain templates, and get/create/update their versions
- Mailing lists: get-v3-lists, post-v3-lists to create one, and the list-member tools, plus tag stats and IP management
- Address validation via the validate tool
A Mailgun account and API key in MAILGUN_API_KEY from your API security settings. Node, run as npx @mailgun/mcp-server over stdio. If your account is in Mailgun's EU region, set MAILGUN_API_REGION=eu; it defaults to us.
One command plus a key — npx -y @mailgun/mcp-server, then supply credentials
