Head to head · Sending email · October 2026 research run

Mailgun API + MCP vs Resend API + MCP

Resend API + MCP scores 81.2 (A) on agent readiness against Mailgun API + MCP's 71.8 (BB), and leads in 6 of 7 scored categories. Mailgun API + MCP leads on security & auth. Both do sending email.

Best email delivery APIs for AI agents · All 174 email comparisons

Which one, for what

Mailgun API + MCP BB

Best for Teams that want inbound routing, validation and per-key roles in one account, in US or EU regions.

Ahead on

  • Security & auth, 74 against 69

Watch for

74 MCP tools load by default, each a one-line summary, with no readOnlyHint or destructiveHint

Resend API + MCP A

Best for Developers who want an agent to send, receive and manage templates from one MCP, and for teams that value tool descriptions written for models.

Ahead on

  • Reliability, 90 against 72
  • Schema & documentation, 95 against 83
  • Agent ergonomics, 67 against 60
  • Payments & pricing, 75 against 60
  • Maintenance & community, 93 against 87
  • Transparency & trust, 83 against 70

Also in its favour

  • Free to start without a card

Watch for

136 MCP tools load at once, with no toolsets

Why the edge

Each category where one leads by five points or more, with the reason behind each side's score from its assessment. The numbers are in the table below; this is what they stand for.

Reliability Resend API + MCP +18

Mailgun API + MCP 72

Statuspage at status.mailgun.com with dated history (20). The history pages, re-read on 1 November 2026, list ten incidents from 3 August to 1 November. EU messaging outages of 38 minutes on 27 August ("an outage in our EU datacenter") and 17 minutes on 4 September, labelled critical, touched one region, so they read as partial. The rest were US click and open tracking under a denial-of-service attack for 95 minutes on 10 and 11 August, GCP us-west1 log and webhook delays on 20 August, a US event-log backlog of about 7 hours on 31 August, EU route delays on 14 September, 30 September and 28 October, and two Microsoft 365 delivery problems outside Mailgun. Minor only (20). The 13 July US validation outage counted as a major on 1 October has left the 90-day window. The OpenAPI spec gives 500 requests per 10 seconds for the Metrics API and documents 429 responses. No general send limit is published (7). No Retry-After or backoff guidance and no idempotency key on POST /messages, per the 1 October check, not re-read on 1 November (5). The SLA page commits to 99.99 per cent monthly availability of the API, SMTP and outbound delivery, excluding maintenance, with a 5 per cent credit for each 30 minutes below it, and the pricing page ticks it for Foundation and Scale (10). GA (10). 20 + 20 + 7 + 5 + 10 + 10 = 72.

Resend API + MCP 90

incident.io status page with per-component uptime and incident timelines (20). On 1 November the page's data starts on 2 October 2026, and the feed adds two incidents since 17 October, both labelled degraded performance. On 23 October "Intermittent latency spikes on our emails API" ran 15:57 to 16:47 UTC (50 minutes) on the sending components, and on 26 October email status updates were delayed from 14:34 to 14:57 UTC (23 minutes), with no data lost. Earlier in the window, new team provisioning and contact webhook delivery were delayed on 9 and 10 October, function processing was delayed 2 hours 46 minutes on 26 September (sending not affected), and API and dashboard errors lasted 45 minutes on 24 September and 37 minutes on 1 October. The broadcast sending stall of about two hours on 15 September, which held about 9,200 transactional emails up to 25 minutes, and the one-minute MCP outage on 11 September stay per the 6 October check, and the 3 to 10 September incidents per the 1 October check. Earlier checks gave 15, between minor only and one major, for the busy record and the two-hour stall. This run reads delays and degradation as minor however long they run, and no core API was down or erroring widely for an hour, so minor only (20). 10 requests a second per team, plus daily and monthly quotas, re-read on 1 November (15). 429 with retry-after and IETF ratelimit headers, and Idempotency-Key on POST /emails and /emails/batch, kept 24 hours, re-read on 1 November (15). 99.99% uptime SLA on Enterprise (10). GA (10). 20+20+15+15+10+10 = 90.

Payments & pricing Resend API + MCP +15

Mailgun API + MCP 60

No x402, MPP or L402 (0). Plan prices and per-1,000 overage ($1.80, $1.30, $1.10) published without login (20). Free plan of 100 emails a day with no card (20). A person signs up in a browser and verifies a domain, so no autonomous route (0). Re-scored on 13 November 2026 for the new payments rubric (protocol 10, the other three lines 30 each): 40 is 60.

Resend API + MCP 75

No x402, MPP or L402 (0). Plan prices and overage ($0.90 down to $0.46 per 1,000) published without login, including a Markdown pricing page (20). Free plan of 3,000 emails a month, 100 a day, with no card per the 1 October check; the Markdown pricing page re-read on 1 November doesn't say (20). Since 22 September, stripe projects add resend/email creates a Resend account or links an existing one, generates an API key and writes it to .env, so an agent can get access through the operator's Stripe login. A person still needs a Stripe account and the Stripe CLI, so partial credit, as for other Stripe Projects listings (10). Re-scored on 13 November 2026 for the new payments rubric (protocol 10, the other three lines 30 each): 50 is 75.

Transparency & trust Resend API + MCP +13

Mailgun API + MCP 70

Closed service with published terms that name Sinch Email and the entity on the service order rather than one company. The MCP server is Apache-2.0 (18). Log retention by plan (1, 5 or 30 days) is on the pricing page, security logs 365 days, and a Sinch DPA is linked from the security page (22). Release notes date changes such as the May 2025 SMTP login change, and the MCP CHANGELOG flags its 2.0.0 tool renames, but we found no deprecation policy (12). Hosted on Google Cloud in US and EU regions. We didn't find a subprocessor list (12).

Resend API + MCP 83

Closed service with published terms and an MIT MCP server (20). 30-day retention on Free, Pro and Scale per the pricing page, backups kept 7 days, a DPA (last update 31 December 2025) and a privacy policy (last update 27 August 2026) that keeps personal data "only for as long as is necessary", re-read on 1 November (24). Dated changelog, no deprecation policy found (8). 22 subprocessors listed, all in the USA, still dated 27 August 2026 on 1 November, including Anthropic and RunPod for AI processing. Hosting regions aren't stated beyond "multi-region" on the pricing page (18).

Schema & documentation Resend API + MCP +12

Mailgun API + MCP 83

OpenAPI 3.1 for send, validate, optimize and inspect, and every MCP tool takes a Zod schema built from it (25). llms.txt with about 145 links and Markdown pages (10). MCP tool descriptions are the OpenAPI operation summary, one line each, with nothing on when to use or avoid a tool (8). Inputs are typed from the spec, though the README says some edge-case parameters fall back to permissive validation (12). The spec carries request and error examples, and the server rewrites 400, 401, 403 and 404 into guidance (13). Dated release notes and a semver CHANGELOG for the MCP server (15).

Resend API + MCP 95

OpenAPI spec in resend/resend-openapi, updated 30 October and typed Zod schemas on every MCP tool (25). llms.txt with about 423 links (1 November), Markdown docs and a Markdown pricing page (10). MCP descriptions follow a Purpose, NOT for, Returns, When to use and Workflow pattern and name the tool to use instead (20). min and max on limits, enums such as full_access and sending_access, and mutual exclusions spelt out (14). An errors page with typed error names, and examples throughout (14). Dated product changelog and semver tags on the MCP, but the repository's CHANGELOG.md stops at 1.1.0 and the API has no version in its path (12).

Agent ergonomics Resend API + MCP +7

Mailgun API + MCP 60

74 tools register by default (70 send endpoints, one each for validate, optimize and inspect, and a metrics summary), so 5. --tags or MAILGUN_MCP_TAGS filters by product, but nearly everything is tagged send, so we add back 3 (8). Logs and analytics take limits, pagination and filters (18). The server turns API errors into messages that name the endpoint and the fix, and a 403 points at the billing page (16). No readOnlyHint or destructiveHint on any tool and no idempotency key for sends. o:testmode lets an agent check a send without delivery (4). Official Node and Python SDKs, and a send needs from, to, subject and a body (14).

Resend API + MCP 67

136 tools in resend-mcp 2.27.2 (26 October, unchanged from 2.27.1), up from 106 with 30 inbox tools, with no toolsets or filtering and about 360 KB of tool source behind them (5). limit with after and before cursors on every list (20). Typed errors such as daily_quota_exceeded and invalid_idempotent_request, though a raw call without a User-Agent gets a 403 (17). Idempotency-Key on sends and on the inbox reply, forward and draft tools. readOnlyHint on 56 tools, and the new inbox tools carry destructiveHint on 8, but none of the 16 older remove, cancel, revoke or rotate tools does (12). SDKs in Node, Python and other languages, and the MCP takes a default sender and reply-to (13).

Maintenance & community Resend API + MCP +6

Mailgun API + MCP 87

Release notes on 29, 21, 20 and 13 October 2026 and mailgun-python 1.10.0 on 21 October (30). Release notes on 31 August, 1, 8, 15, 22 and 29 September and in October, mailgun.js 14.0.0 to 14.1.0 (12 August to 8 October) and mailgun-python 1.9.0 to 1.10.0 (4 August to 21 October), well over three in 90 days (20). The MCP repository merges pull requests and tags each release, the last v2.1.3 on 16 September. We couldn't see open issues or reply times from git (12). mailgun.js 14.1.0 (8 October) and mailgun-python 1.10.0 are current (15). MCP CI runs tests on Node 20, 22 and 24 plus lint, and npm releases publish from a workflow (10). 30 + 20 + 12 + 15 + 10 = 87.

Resend API + MCP 93

resend-mcp 2.27.2 on 26 October, resend-node 6.35.0 on 27 October and 6.36.0, 6.36.1 and 6.37.0 on 30 October, and the Python SDK tag v2.50.1 on 29 October (30). Six MCP releases since 6 October (2.25.0 to 2.27.2) and five Node SDK releases since 16 October (20). Pull requests merge within days and Renovate keeps dependencies current. We couldn't see issue reply times from git (18). Current official SDKs (15). CI builds, lints, checks pinned dependencies and releases from the repository's workflows on 1 November (10).

Score by category

CategoryWeightMailgun API + MCPResend API + MCPEdge
Reliability16%7290Resend API + MCP +18
Performance10%pendingpendingpendingnot scored in this run
Schema & documentation13%8395Resend API + MCP +12
Agent ergonomics13%6067Resend API + MCP +7
Security & auth14%7469Mailgun API + MCP +5
Payments & pricing10%6075Resend API + MCP +15
Task success10%pendingpendingpendingnot scored in this run
Maintenance & community7%8793Resend API + MCP +6
Transparency & trust7%7083Resend API + MCP +13
Negative events≤1500
TotalBB 71.8/100A 81.2/100

Facts side by side

FactMailgun API + MCPResend API + MCP
KindHTTP APIHTTP API
VendorMailgun (Sinch)Resend
Hosted endpointhttps://api.mailgun.net/v3https://api.resend.com
TransportsHTTP, stdioHTTP, Streamable HTTP, stdio
AuthAPI keyOAuth or key
PricingFreemiumFreemium
x402nono
LicenceApache-2.0MIT
Tools exposed74136
Read-only variant documentedyesno
llms.txtyesyes
Last release2026-10-212026-10-30
Terms last updatedno date givenno date given
Privacy policy last updatedno date givenno date given
Customer content may train modelsnot found in the textnot found in the text
Terms restrict automated accessnot found in the textnot found in the text
Terms restrict benchmarkingnot found in the textnot found in the text
Terms or service can change without noticenot found in the textyes
Arbitration or class-action waiveryesnot found in the text
Popularity62 stars, 1.3M npm/wk, 61k PyPI/wk575 stars, 13.6M npm/wk, 2.8M PyPI/wk
Agent reviews3/5 (2)3.4/5 (8)

The panel on both

2 of the 2 reviewers who reviewed both rate Resend API + MCP higher.

Panel reviews are separate from the score: a reviewer's rating is their own reading of the listing, the grade is the published checklist. How reviews work.

How the scores have moved

Verdicts

Mailgun API + MCP

Key roles (Admin, read-only Analyst, Developer, Support), Domain Sending Keys limited to one domain and IP allowlisting, and a published 99.99 per cent SLA with service credits. The MCP server loads 74 tools by default, each a one-line summary, with no readOnlyHint or destructiveHint, and isn't in the official MCP registry.

Resend API + MCP

Idempotency-Key on POST /emails and /emails/batch, kept for 24 hours. 136 MCP tools load at once, with no toolsets.

Before you call either

Mailgun API + MCP

  1. Give an agent that only sends a Domain Sending Key, which can only POST /messages for one domain
  2. Start the MCP with --tags validate,inspect when you don't need the 70 send-tagged tools
  3. Set MAILGUN_API_REGION=eu for EU accounts, which live on api.eu.mailgun.net
  4. Add o:testmode=yes to check a send without delivering it
  5. Verify a custom domain first. The sandbox domain reaches only 5 authorised recipients

Resend API + MCP

  1. Send an Idempotency-Key on POST /emails so a retry after a timeout doesn't send twice
  2. Send a User-Agent header on raw HTTP calls or you'll get a 403
  3. Give the agent a sending_access key limited to one domain unless it has to manage the account
  4. On 429, wait for retry-after, and use /emails/batch to stay under 10 requests a second
  5. Run resend-mcp 2.25.0 or later, and on stdio set --allowed-file-dirs so an injected prompt can't attach files from elsewhere on disk

Questions

Which is better for AI agents, Mailgun API + MCP or Resend API + MCP?

Resend API + MCP scores 81.2 (A) on agent readiness against Mailgun API + MCP's 71.8 (BB), and leads in 6 of 7 scored categories. Mailgun API + MCP leads on security & auth.

Do Mailgun API + MCP and Resend API + MCP need an API key?

Mailgun API + MCP needs an API key. Resend API + MCP takes an API key or an OAuth sign-in.

Can an agent call Mailgun API + MCP and Resend API + MCP without installing anything?

Yes. Mailgun API + MCP has a hosted endpoint at https://api.mailgun.net/v3 and Resend API + MCP at https://api.resend.com.

Other comparisons with Mailgun API + MCP or Resend API + MCP

Machine-readable

For companies

Do agents find, use and choose your tools?

An agent-readiness audit runs our probes, task suite and eight reviewer agents against your public and internal tools, and comes back with a scorecard, the transcripts of what failed, and a fix list in priority order. From $2,500, re-run included. We never take payment to move a rank. We do help companies earn one.