Mailgun MCP. Audit DNS records, manage bounces, and send verified emails.
Gemini Works with every AI agent you already use
…and any MCP-compatible client
Just plug in your AI agents and start using Vinkius.
Mailgun (Transactional Email & Domains) lets your AI client manage complex email infrastructure. You can send high-priority transactional messages, audit domain health via DNS records (SPF/DKIM), and track delivery failures.
It also monitors bounce lists and unsubscribes so you know exactly where your emails are going wrong.
What your AI agents can do
Delete bounce
Permanently removes a bounced email address from your domain's suppression list.
Get domain
Fetches the full DNS records and specific details for any configured Mailgun domain.
Get stats
Retrieves key analytics data, including open rates and click-through rates, for a specified Mailgun domain.
Retrieves the full set of DNS records (SPF, DKIM, MX) for a specified Mailgun domain to verify proper setup.
Sends emails using your configured domains and templates, ensuring high deliverability by routing through the secure sending mechanism.
Queries raw event logs to provide a chronological record of deliveries, opens, bounces, or any other anomalous traffic spike.
Lists and audits bounced emails and unsubscribes. You can also delete specific suppressions to retry sending an address.
Uses the dedicated Mailgun API endpoint to check if a target email address is technically valid and deliverable, preventing hard bounces upfront.
Ask AI about this MCP
Supported MCP Clients
OAuth 2.0 Compatible Gemini Waiting for input…
Mailgun (Transactional Email & Domains) MCP Server: 10 Tools for Email Infrastructure
These tools give you command-line access to every function in Mailgun—from sending emails and validating addresses to auditing DNS records and managing bounce lists.
Make your AI actually useful.
Add this MCP to Claude, Cursor, or Windsurf and your AI stops guessing. It gets real tools to look things up, take action, and handle the stuff you keep doing by hand.
Start using Mailgun (Transactional Email & Domains) on Vinkius019d75ccdelete bounce
Permanently removes a bounced email address from your domain's suppression list.
019d75ccget domain
Fetches the full DNS records and specific details for any configured Mailgun domain.
019d75ccget stats
Retrieves key analytics data, including open rates and click-through rates, for a specified Mailgun domain.
019d75ccget templates
Lists all stored HTML Handlebars templates associated with your domain, so you know what content is available to send.
019d75cclist bounces
Checks the suppression list for bounced emails and unsubscribes across a specific domain.
019d75cclist domains
Returns a complete list of every domain currently configured on your Mailgun account.
019d75cclist logs
Gets raw event logs, tracking all deliveries, opens, drops, and bounces for a given domain over time.
019d75cclist unsubscribes
Lists every email address that has explicitly unsubscribed from receiving mail for your domain.
019d75ccsend email
Sends a transactional or marketing email to a target recipient using the Mailgun API.
019d75ccvalidate email
Checks whether a provided email address is valid and deliverable through the dedicated Mailgun validation endpoint.
Choose How to Get Started
Build a custom MCP for your own tools, or connect a ready-made integration from our catalog.
Build Your Own
Turn any API into an MCP. Import a spec, define Agent Skills, or deploy with MCPFusion.
- Import from OpenAPI, Swagger, or YAML specs
- Create Agent Skills with progressive disclosure
- Deploy to edge with MCPFusion framework
- Built in DLP, auth, and compliance on every call
- Real time usage dashboard and cost metering
- Publish to catalog or keep private
Make Your AI Do More
Start with Mailgun (Transactional Email & Domains), then connect any of our 4,800+ other servers whenever your AI needs more. One click, no limits.
- Use this MCP plus 4,800+ others, all in one place
- Add new capabilities to your AI anytime you want
- Every connection is secured and compliant automatically
- Track usage and costs across all your servers
- Works with Claude, ChatGPT, Cursor, and more
- New servers added to the catalog every week
Independent Platform Disclaimer: Vinkius is an independent platform and is not affiliated with, endorsed by, sponsored by, verified by, or otherwise authorized by Mailgun. All third-party trademarks, logos, and brand names are the property of their respective owners. Their use on this website is strictly for informational purposes to identify service compatibility and interoperability.
VINKIUS INFRASTRUCTURE
Cloud Hosted
Managed infra
V8 Isolated
Sandboxed per request
Zero-Trust Proxy
No stored credentials
DLP Enforced
Policy on every call
GDPR Compliant
EU data residency
Token Compression
~60% cost reduction
Works with Claude, ChatGPT, Cursor, and more
The Model Context Protocol standardizes how applications expose capabilities to LLMs. Instead of operating in isolation, your AI gains direct access to external platforms, live data, and real-world actions through secure, standardized connections.
This server provides 10 capabilities that interface natively with Claude, ChatGPT, Cursor, and any MCP client. No middleware. No custom integration required.
Checking deliverability shouldn't require jumping between five different dashboards.
Today, if you suspect an email campaign failed because of a bad record or invalid domain setup, you have to context-switch constantly. You check the DNS records in one place, the bounce reports in another, and then try to correlate those failures with raw logs from a third tab. It’s slow, error-prone, and takes too much time.
With this MCP server, you tell your agent the problem—'Why did last week's campaign fail?' The agent coordinates calls across `get_domain`, `list_bounces`, and `list_logs`. You get a single, cohesive answer that points directly to the failure point. It cuts the investigative time from minutes to seconds.
Mailgun (Transactional Email & Domains) MCP Server: Manage every email state.
You no longer have to manually copy DNS records into a spreadsheet or run separate API calls for stats vs. logs. The agent handles the orchestration. You just ask, and it pulls everything together.
It's not just about sending emails; it's about having full, conversational control over every single data point—the validation, the bounce, the open rate, and the delivery log entry. That’s the difference.
What you can do with this MCP connector
Your agent uses send_email, which lets you send high-priority transactional or marketing emails using your configured domains and custom HTML templates. You'll never have to manually call the API again; just tell your AI client what you gotta send, and it handles the secure routing.
Domain Setup and Verification
Before sending anything, you gotta make sure your setup is tight. Use list_domains to pull a complete rundown of every domain sitting on your Mailgun account. Need details on one specific domain? Run get_domain; that pulls the full DNS records—SPF, DKIM, and MX—so you can verify everything's configured right for top deliverability.
Checking Addresses Before You Send a Dime
Don't waste credits sending to dead ends. The validate_email tool checks if an address is actually valid and technically deliverable through the dedicated Mailgun validation endpoint, letting you block hard bounces before they even happen.
Crafting and Sending Messages
When it comes time to write, you'll first need templates. Use get_templates to list all stored HTML Handlebars templates attached to your domain so you know what content options are available for the send. Once you’ve got your template ready, you use send_email, which handles sending transactional or marketing messages using verified domains.
Tracking What Happens After You Hit Send
Once the emails are out there, you need to watch 'em like a hawk. The list_logs tool gives you raw event logs for any domain over time; this tracks everything—deliveries, opens, drops, and bounces—giving you a chronological record of every single email's journey.
For performance metrics, run get_stats. This pulls key analytics data, specifically open rates and click-through rates, tied to your specified Mailgun domain. You can also use list_bounces and list_unsubscribes together to audit the suppression list for both bounced addresses and explicit unsubscribes across a given domain.
If you find an address that bounced but you gotta try sending it again, use delete_bounce. This tool permanently removes a specific bounced email address from your domain's suppression list. Finally, if you want to see exactly who quit receiving mail, run list_unsubscribes; this lists every single email that explicitly opted out of receiving messages for your domain.
019d75cc-afa7-722a-a763-036c294f08be 
How Mailgun MCP Works
- 1 First, subscribe to the server and provide your Mailgun Private API Key. This gives your AI client the necessary access credentials.
- 2 Next, tell your agent what you need—for example, 'Check the DNS health for my main domain' or 'Send a welcome email.'
- 3 The agent executes the required tool call against your live Mailgun account and presents the raw data (DNS records, logs, etc.) to you.
The bottom line is: You manage critical email infrastructure by talking to it, without ever having to write a single API request yourself.
Who Is Mailgun MCP For?
This server is for the DevOps engineer who can't trust manual dashboard clicks. It’s for developers building mission-critical communication paths and growth teams needing instant visibility into delivery failures. If your job involves sending anything important via email, you need this.
Monitors domain deliverability in real time. They use the server to check DNS records and query raw event logs immediately after an incident.
Tests transactional email flows before deployment. They validate domains using validate_email and test sending through send_email in a conversation, not a playground.
Audits campaign performance. They use the server to pull stats (get_stats) and manage suppression lists after a large mailing campaign.
What Changes When You Connect
- Pinpoint Delivery Failures: Instead of guessing why an email failed, use
list_logsto extract raw chronological data. You'll see the exact event—was it a bounce? A drop? This level of detail is impossible through standard dashboards. - Pre-flight Checks are Mandatory: Never send an email without checking first. Use
validate_emailbefore callingsend_email. It prevents hard bounces and saves you time cleaning up failed campaigns. - Confirm Domain Setup Instantly: Before your next big campaign, run
get_domain. You immediately verify if critical records like SPF and DKIM are active, eliminating the risk of being blocked by receiving servers. - Control Your Suppression List: Bounce lists get messy. With
list_bounces, you can see exactly which addresses bounced and, if necessary, usedelete_bounceto manually re-add them for a retry send. - Know Your Full Footprint: Use
list_domainsfirst. It gives you an inventory of every active domain on your account, ensuring no critical sending source gets forgotten or mismanaged.
Real-World Use Cases
The 'Did the Campaign Actually Send?' Check
A growth engineer needs to know why a batch email failed. Instead of jumping between three different dashboards, they prompt their agent: 'List all logs for domain X last night.' The agent runs list_logs, identifies 50 bounces, and tells them the specific error code (e.g., invalid recipient). They then use this data to update their CRM.
Validating a New Client Domain
A developer is setting up a new client domain for testing. They don't want to risk sending test emails until the DNS is perfect. They prompt: 'Check the DNS records for mg.newclient.com.' The agent runs get_domain and immediately reports if SPF/DKIM are missing, blocking them from proceeding until the issue is fixed.
Responding to a Blocked Sender
The ops team gets an alert that their sending reputation dropped. They prompt: 'List all bounces and unsubscribes for our main domain.' The agent runs list_bounces and finds 50 old, inactive addresses. The manager uses this list to manually remove the worst offenders using delete_bounce, improving overall sender hygiene.
Quickly Sending a Confirmation Email
A user signs up for service and needs an immediate welcome email. They prompt: 'Send a welcome email to john@example.com.' Before the agent calls send_email, it first runs validate_email on the address. If the validation fails, the agent tells them immediately instead of sending an error report.
The Tradeoffs
Assuming basic domain setup is fine
Just running 'Send a confirmation email' and assuming it works. You could hit a hard bounce rate because your SPF record expired or was never set up.
→
Always run get_domain first to verify DNS records like SPF and DKIM are current. Then, use validate_email on the target address before calling send_email. This multi-step process prevents 90% of delivery failure issues.
Ignoring old bounce addresses
Running a large campaign and seeing high bounce numbers, then just ignoring them. The list gets polluted with stale or bad data, costing you reputation.
→
After reviewing the failures with list_bounces, identify genuinely inactive addresses. Use delete_bounce to clean up the suppression list, keeping only active users for your next send.
Manually fetching logs from a UI
Going into the Mailgun dashboard, clicking through multiple tabs (Deliveries, Opens, Bounces) and manually copying data to a spreadsheet. This is slow and misses context.
→
Ask your agent: 'List raw event logs for domain X in the last 6 hours.' The agent runs list_logs and gives you all the raw, chronological data points instantly, saving time and ensuring completeness.
When It Fits, When It Doesn't
Use this server if your primary concern is email deliverability control. This tool set shines when you need to combine multiple checks: first validate the domain (get_domain), then validate the user (validate_email), and only then execute the send (send_email).
Don't use this server if your main problem is general marketing automation or CRM management. If all you need is to update a contact record in Salesforce, this isn't the tool. For those cases, look into dedicated CRM or database connector MCP servers.
However, if you are an SRE who needs to confirm that every step of a complex communication process worked—from DNS setup to final delivery log entry—this is your single source of truth. The power here isn't just in sending; it's in the deep audit capabilities provided by list_logs and get_domain.
Common Questions About Mailgun MCP
How do I check if my domain is set up correctly using get_domain? +
Run get_domain and check the output for SPF, DKIM, and MX records. If these records are missing or marked as 'Unverified', your emails might fail to deliver properly.
What's the difference between list_logs and list_bounces? +
list_logs gives you a raw history of every event (open, drop, bounce) that happened over time. list_bounces, however, is specifically for auditing addresses that failed delivery and managing them in the suppression list.
Can I send an email without first using validate_email? +
Yes, you can call send_email directly. But it's a bad idea. Always run validate_email first to confirm the address is active and deliverable. This stops hard bounces before they happen.
How do I list all my domains configured on Mailgun? +
You just need to call list_domains. It gives you a complete inventory of every domain attached to your account, which is useful for auditing and ensuring coverage.
When should I use the irreversible action of `delete_bounce`? +
You can only delete a bounced email if you confirm it was an incorrect entry or spam bounce. Remember, this action is permanent and removes the record entirely; don't run it unless you are certain about the data integrity issue.
Using `get_templates`, what information can I find to ensure consistent messaging? +
The tool lists all HTML Handlebars templates stored for your domain. This helps you audit your existing professional message formats, ensuring that every email sent via the agent uses approved and brand-consistent code.
How does `list_unsubscribes` help me maintain compliance? +
list_unsubscribes gives you a clean list of addresses that opted out. You must respect these records; never attempt to send any messages to an email listed here, regardless of how long ago they unsubscribed.
Beyond basic DNS checks, what metrics does `get_stats` provide? +
get_stats pulls domain-level analytics beyond connectivity. It tracks actual performance data like open rates and click-through rates, letting you measure the real success of your campaigns.
Can I check if my domain's DNS records are correctly configured? +
Yes. Use the get_domain tool by providing your verified domain name. Your agent will retrieve the status of SPF, DKIM, and MX records, helping you identify if any DNS dependencies are missing or misconfigured.
How do I see which emails have recently bounced from my domain? +
The list_bounces tool allows your agent to extract the suppression logs for a specific domain. You'll see the email addresses that failed to deliver, providing insights into audience health or sending boundaries.
Can my agent validate an email address before I send a message? +
Absolutely. Use the validate_email tool to check if an address is valid, deliverable, and doesn't belong to a disposable service. This is perfect for ensuring high-quality data before triggering outbound sends.
Use it with your favorite AI tools
Connect this server to Cursor, Claude, VS Code, and more.