Mailgun

Mailgun

Official

Manage Mailgun messaging, domains, webhooks, and analytics from an AI agent.

Score 75(?)MailgunApache-2.058Verified Top MCPs for Email

Quick answer

What it does

Surfaces Mailgun operations as MCP tools: send/retrieve/resend messages, manage domains and DNS, configure webhooks, define routes, manage mailing lists and templates, query analytics and suppressions.

Best for

  • Operational Mailgun ops (routes, suppressions, IPs)
  • DNS and domain verification
  • Delivery analytics queries
  • Mailing list and template CRUD

Not for

  • Greenfield projects (modern API ergonomics — try Resend)
  • Volumes high enough to hit per-second rate limits via agent

Source: top-mcps.com/mcp/mailgun — verified Aug 2026

Setup recipe

Pick your client, then follow the three steps.

  1. 1

    Install

    claude_desktop_config.json
    {
      "mcpServers": {
        "mailgun": {
          "command": "npx",
          "args": [
            "-y",
            "@mailgun/mcp-server"
          ],
          "env": {
            "MAILGUN_API_KEY": "${MAILGUN_API_KEY}",
            "MAILGUN_API_REGION": "${MAILGUN_API_REGION}"
          }
        }
      }
    }

    Paste under mcpServers. Fully quit and reopen Claude after editing.

    CLI or .mcp.json
    # export MAILGUN_API_KEY=your_mailgun_key
    # export MAILGUN_API_REGION=us
    claude mcp add mailgun -- npx -y @mailgun/mcp-server

    Run from your repo. Commit .mcp.json to share with your team.

    .cursor/mcp.json
    {
      "mcpServers": {
        "mailgun": {
          "command": "npx",
          "args": [
            "-y",
            "@mailgun/mcp-server"
          ],
          "env": {
            "MAILGUN_API_KEY": "${MAILGUN_API_KEY}",
            "MAILGUN_API_REGION": "${MAILGUN_API_REGION}"
          }
        }
      }
    }

    Global path: ~/.cursor/mcp.json. Reload window after editing.

    .vscode/mcp.json
    {
      "servers": {
        "mailgun": {
          "command": "npx",
          "args": [
            "-y",
            "@mailgun/mcp-server"
          ],
          "env": {
            "MAILGUN_API_KEY": "${MAILGUN_API_KEY}",
            "MAILGUN_API_REGION": "${MAILGUN_API_REGION}"
          }
        }
      }
    }

    VS Code uses the "servers" key (not "mcpServers").

    ~/.codeium/windsurf/mcp_config.json
    {
      "mcpServers": {
        "mailgun": {
          "command": "npx",
          "args": [
            "-y",
            "@mailgun/mcp-server"
          ],
          "env": {
            "MAILGUN_API_KEY": "${MAILGUN_API_KEY}",
            "MAILGUN_API_REGION": "${MAILGUN_API_REGION}"
          }
        }
      }
    }

    Open via Cascade → hammer icon → Configure.

    cline_mcp_settings.json
    {
      "mcpServers": {
        "mailgun": {
          "command": "npx",
          "args": [
            "-y",
            "@mailgun/mcp-server"
          ],
          "env": {
            "MAILGUN_API_KEY": "${MAILGUN_API_KEY}",
            "MAILGUN_API_REGION": "${MAILGUN_API_REGION}"
          }
        }
      }
    }

    Open via the Cline sidebar → MCP Servers → Edit.

    ~/.continue/config.json
    {
      "experimental": {
        "modelContextProtocolServers": [
          {
            "transport": {
              "type": "stdio",
              "command": "npx",
              "args": [
                "-y",
                "@mailgun/mcp-server"
              ],
              "env": {
                "MAILGUN_API_KEY": "${MAILGUN_API_KEY}",
                "MAILGUN_API_REGION": "${MAILGUN_API_REGION}"
              }
            }
          }
        ]
      }
    }

    Continue uses modelContextProtocolServers with a transport block.

    ~/.codex/config.toml
    # ~/.codex/config.toml
    [mcp_servers.mailgun]
    command = "npx"
    args = [
      "-y",
      "@mailgun/mcp-server",
    ]
    env = { MAILGUN_API_KEY = "${MAILGUN_API_KEY}", MAILGUN_API_REGION = "${MAILGUN_API_REGION}" }

    Codex uses TOML. Each server is a [mcp_servers.<name>] subtable.

    ~/.config/zed/settings.json
    {
      "context_servers": {
        "mailgun": {
          "command": {
            "path": "npx",
            "args": [
              "-y",
              "@mailgun/mcp-server"
            ]
          },
          "env": {
            "MAILGUN_API_KEY": "${MAILGUN_API_KEY}",
            "MAILGUN_API_REGION": "${MAILGUN_API_REGION}"
          }
        }
      }
    }

    Zed calls them "context_servers". Settings live-reload on save.

    ChatGPT → Apps directory

    Mailgun doesn't ship a hosted HTTPS endpoint today. ChatGPT supports remote MCP servers only — to use this server in ChatGPT you'll need to deploy it to a public HTTPS URL first (e.g. via Cloudflare Workers or Vercel) or wait for an official remote build.

  2. 2

    Set required secrets

    Set MAILGUN_API_KEY, MAILGUN_API_REGION in your shell environment before launching your MCP client.

  3. 3

    Try a minimum working prompt

    Minimum working prompt pending verification. Try any prompt from the MCP’s README once installed.

Tools & permissions

Tools list pending verification. The server exposes tools over MCP; we haven’t yet parsed its capability manifest into this page. Check the GitHub repo for the authoritative list.

Security & scope

Access scope
Read + write
Sandbox
OpenAPI-driven with a curated endpoint allowlist: tools cover read and update operations only — no delete endpoints are registered, which the vendor states keeps the blast radius of an unintended action small. MAILGUN_MCP_TAGS / --tags narrows the surface further to send, validate, optimize, or inspect product groups.
Gotchas
  • The API key sits in an environment variable and sending is billable — a retry loop on a send tool spends real money and sender reputation.
  • Update operations on routes, webhooks, and tracking settings change live mail flow even though nothing can be deleted.

Agent prompt pack

— copy into Claude, Cursor, or ChatGPT.
Paste into Claude, Cursor, or ChatGPT. Edit the [brackets] before sending.
Recommend the best MCP servers for [task: e.g. email work] in [client: Claude].

Constraints:
- Prefer tools that are [official | open-source | read-only] — pick what matters for my use case.
- Exclude MCPs that require [e.g. a paid plan, OAuth-only flows, remote-only transport].
- Return at most 3 picks, ranked.

For each pick include:
1. One-sentence rationale.
2. The ready-to-paste install snippet for my client.
3. Any required secrets I need to create before installing.

Cross-check the top-mcps.com listing: https://top-mcps.com/top-mcps-for-email
Compare Mailgun against a real alternative. Swap the second MCP in [brackets] if you want a different match.
Compare Mailgun MCP vs [Resend MCP] for the following job: [describe the job, e.g. "let an agent create GitHub issues on bug triage"].

Judge them on:
- Setup time and complexity (what a new user hits first).
- Auth model (none / API key / OAuth 2.1) and credential risk.
- Transport (stdio / Streamable HTTP / SSE) and where the server runs.
- Required secrets and the blast radius if they leak.
- Operational risk in an unattended agent loop.
- Which one is "good enough" for a weekend prototype vs. production.

End with one sentence: which should I pick for my scenario, which is: [my scenario].

References:
- https://top-mcps.com/mcp/mailgun
- top-mcps.com listing for Resend
Asks the agent to install and verify. Works inside Claude Code, Cursor Agent, Codex CLI.
Install the Mailgun MCP server for my [client: Claude] at the default config path for that client.

Use the exact install snippet published at https://top-mcps.com/mcp/mailgun (fetch https://top-mcps.com/mcp/mailgun.json for the canonical server.json if you can read URLs).

Before finishing:
1. Create the required secrets (MAILGUN_API_KEY, MAILGUN_API_REGION) and put them in the appropriate env block — do not hard-code them.
2. Restart or reload the client so it picks up the new server.
3. Verify the server is connected (green / running state) and at least one tool is listed.
4. If anything fails, read the client's MCP logs and report the exact error — do not silently retry.

Confirm when done and list the tools the server now exposes.

Frequently asked questions

What changed

2 updates tracked.
  1. v2.1.0 released

  2. v2.0.0 released

More Email MCPs

Other tools in the same category worth evaluating.

Microsoft Work IQ
Official

Ask natural-language questions across Microsoft 365 Copilot data.

microsoft, copilot, search, email
10 minMedium
Microsoft 365

Outlook mail and calendar, Teams, OneDrive and Excel through one Graph API server.

microsoft, outlook, calendar, email
10 minMedium
Gmail

Send, read, search, and label Gmail from an AI agent — community MCP with auto-OAuth.

gmail, email, community, google
15 minMedium

Compared with Mailgun

Side-by-side breakdowns for the choices people most often weigh against this MCP.

Exploring Top MCPs for Email? See all Email MCPs →