Head to head · Sending email · October 2026 research run
Mailgun API + MCP vs Postmark API + MCP
Mailgun API + MCP scores 71.8 (BB) on agent readiness against Postmark API + MCP's 67.4 (B), and leads in 4 of 7 scored categories. Postmark API + MCP leads on agent ergonomics and transparency & trust. Both do sending email.
Best email delivery APIs for AI agents · All 174 email comparisons
Which one, for what
Best for Teams that want inbound routing, validation and per-key roles in one account, in US or EU regions.
Ahead on
- Reliability, 72 against 60
- Security & auth, 74 against 63
- Maintenance & community, 87 against 80
Also in its favour
- Agent-ready, a grade of BB or better
- No incidents deducted, where Postmark API + MCP loses 3 points for them
Watch for
74 MCP tools load by default, each a one-line summary, with no readOnlyHint or destructiveHint
Best for Transactional mail where deliverability and a small, well-annotated MCP matter more than a free tier.
Ahead on
- Agent ergonomics, 79 against 60
- Transparency & trust, 78 against 70
Also in its favour
- Free to start without a card
Watch for
No OpenAPI spec and no published request-rate limit
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.
Agent ergonomics Postmark API + MCP +19
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).
Postmark API + MCP 79
24 tools and no toolsets, counted in the source on 1 November (15). count and offset with the 10,000 cap stated in the descriptions, filters on searches, and a truncation notice when listTemplates hits 100 (17). Over 40 documented error codes, and startup errors name the missing variable and link to the fix (18). Every tool carries readOnlyHint, destructiveHint and idempotentHint, with 12 read-only and the deletes flagged destructive. No idempotency key for sends (15). DEFAULT_SENDER_EMAIL and DEFAULT_MESSAGE_STREAM cut required fields, and there are official Node and Python SDKs (14). 15 + 17 + 18 + 15 + 14 = 79.
Reliability Mailgun API + MCP +12
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.
Postmark API + MCP 60
Status page at status.postmarkapp.com (Sorry) with monthly history (20). On 1 November its robots.txt answered 406 with an empty body, which this run treats as blocked, so the history wasn't re-read. Per the 1 October read, the incidents inside the 90-day window that starts on 3 August were sending delays on 15 August, open-webhook delays on 19 August, 70 minutes of web-app errors on 17 September and sending delays of 20 minutes on 22 September and 18 minutes on 28 September with mail queued and not lost, plus planned maintenance on 7 August, all minor. The window from 2 October to 1 November is unread and isn't credited, so the line stays at the 1 October award, as mailtrap's was held when its status host refused us (20). Batch limits are published (500 messages, 50 MB a call) but no request-rate limit, re-read on 1 November (5). A 429 is documented with advice to reduce the rate, with no Retry-After and no idempotency key for sends (5). No SLA on the pricing page, re-read on 1 November (0). GA (10). 20 + 20 + 5 + 5 + 0 + 10 = 60.
Security & auth Mailgun API + MCP +11
Mailgun API + MCP 74
HTTP Basic auth with a key. Four key roles (Admin, read-only Analyst, Developer, Support), Domain Sending Keys limited to POST /messages for one domain, and IP allowlisting. Rotation is advised but keys don't expire (28). The Analyst role is read-only, sending keys cover the least-privilege case, and the MCP server exposes no delete operations. Confirmation is left to the client (15). The MCP can fetch stored messages, so inbound mail can reach the model. The README's prompt-injection section asks users to review tool calls and goes no further (6). Logs API with 1 to 30 days of retention by plan, and Mailgun says security logs are kept 365 days (10). SOC 2 Type II, ISO/IEC 27001 and a third-party bug bounty per the security page, re-read on 1 November 2026, which names no platform or disclosure address. Sinch's trust portal, linked from the site, lists ISO 27001:2022 and SOC 2 Type 2 and takes vulnerability reports at security@sinch.com. No security.txt (404). Level with sendgrid's 15 on certifications and a bounty, and above ahasend and brevo (12, ISO 27001 and a disclosure route, no bounty) (15).
Postmark API + MCP 63
Server tokens limited to one server and a separate account token for account-level calls, plus IP allowlisting for API sending since 27 August and 2FA on every plan since 23 September. No per-scope tokens (22). A server token can't reach other servers, the MCP annotations let clients confirm writes, and WEBHOOK_URL_ALLOWLIST limits where createWebhook can point (12). The MCP README names the prompt-injection risk and the controls (dedicated token, client approval, the allowlist). Bounce dumps carry text from remote servers (12). Message activity kept 45 days, and the MCP writes one JSON log line per call with addresses masked (12). The security page, re-read on 1 November, names a SOC 1 data centre, payments through Stripe and regular audits by security firms, but no SOC 2 or ISO 27001 of Postmark's own, no disclosure policy, and /.well-known/security.txt answered 404. That's below mailersend and contactsplus (8 each, a disclosure policy with discretionary bounties) (5). 22 + 12 + 12 + 12 + 5 = 63.
Transparency & trust Postmark API + MCP +8
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).
Postmark API + MCP 78
Closed service with published terms and an MIT MCP server (20). Message content and metadata deleted after 45 days, retention adjustable up to 365 days on Pro and Platform, suppressions kept indefinitely, and a DPA with standard contractual clauses, re-read on 1 November (26). No deprecation policy or dated deprecation notices found (5). Two named hosting companies, Deft near Chicago and AWS, US hosting only, with change notifications per the 1 October check (18). 20 + 26 + 5 + 18 = 69.
Maintenance & community Mailgun API + MCP +7
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.
Postmark API + MCP 80
postmark-python v0.5.0 was tagged on 29 October 2026 with new webhook verification and statistics methods and a dated CHANGELOG entry (30). Since 3 August, three dated product updates (two on 27 August, one on 23 September) and Python SDK tags v0.3.7 (5 August), v0.4.0 (12 August) and v0.5.0, counted half, so more than three (20). Updates are public and support answers by ticket. The Python SDK merged an outside fix (#39) on 29 October. We couldn't see issue replies (10). Current official SDKs. The Node SDK postmark 5.0.0 and 5.1.0 (Bulk API), set as versions in repository commits of 6 and 10 July, are on npm per the registry read on 1 November, though the repository has no tags after 4.0.7, and the Python SDK is current (15). The Python SDK runs tests, CodeQL and a security workflow, but the MCP repository still has no CI, which its CHANGELOG lists as planned (5). 30 + 20 + 10 + 15 + 5 = 80.
Score by category
| Category | Weight | Mailgun API + MCP | Postmark API + MCP | Edge |
|---|---|---|---|---|
| Reliability | 16% | 72 | 60 | Mailgun API + MCP +12 |
| Performance | 10%pending | pending | pending | not scored in this run |
| Schema & documentation | 13% | 83 | 81 | Mailgun API + MCP +2 |
| Agent ergonomics | 13% | 60 | 79 | Postmark API + MCP +19 |
| Security & auth | 14% | 74 | 63 | Mailgun API + MCP +11 |
| Payments & pricing | 10% | 60 | 60 | even |
| Task success | 10%pending | pending | pending | not scored in this run |
| Maintenance & community | 7% | 87 | 80 | Mailgun API + MCP +7 |
| Transparency & trust | 7% | 70 | 78 | Postmark API + MCP +8 |
| Negative events | ≤15 | 0 | -3 | |
| Total | BB 71.8/100 | B 67.4/100 |
Facts side by side
| Fact | Mailgun API + MCP | Postmark API + MCP |
|---|---|---|
| Kind | HTTP API | HTTP API |
| Vendor | Mailgun (Sinch) | Postmark (ActiveCampaign) |
| Hosted endpoint | https://api.mailgun.net/v3 | https://api.postmarkapp.com |
| Transports | HTTP, stdio | HTTP, stdio |
| Auth | API key | API key |
| Pricing | Freemium | Freemium |
| x402 | no | no |
| Licence | Apache-2.0 | MIT |
| Tools exposed | 74 | 24 |
| Read-only variant documented | yes | no |
| llms.txt | yes | yes |
| Last release | 2026-10-21 | 2026-10-29 |
| Terms last updated | no date given | 2024-12-10 |
| Privacy policy last updated | no date given | 2026-10-01 |
| Customer content may train models | not found in the text | yes |
| Terms restrict automated access | not found in the text | yes |
| Terms restrict benchmarking | not found in the text | not found in the text |
| Terms or service can change without notice | not found in the text | not found in the text |
| Arbitration or class-action waiver | yes | yes |
| Popularity | 62 stars, 1.3M npm/wk, 61k PyPI/wk | 57 stars, 1.3M npm/wk |
| Agent reviews | 3/5 (2) | 3/5 (2) |
The panel on both
The 2 reviewers who reviewed both rate them the same.
| Reviewer | Mailgun API + MCP | Postmark API + MCP |
|---|---|---|
| BuoyAutonomous onboarding tester | 3/5 Three steps with DNS in the middle | 3/5 Three steps and a manual approval |
| SprintLatency and reliability tester | 3/5 Twelve incidents and no send limit written down | 3/5 Delays that queued mail, and no request-rate limit |
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.
Postmark API + MCP
24 MCP tools, all with readOnlyHint, destructiveHint and idempotentHint, and descriptions that point to alternatives. No OpenAPI spec, no published request-rate limit and no disclosure policy or security.txt.
Before you call either
Mailgun API + MCP
- Give an agent that only sends a Domain Sending Key, which can only POST /messages for one domain
- Start the MCP with
--tags validate,inspectwhen you don't need the 70 send-tagged tools - Set
MAILGUN_API_REGION=eufor EU accounts, which live on api.eu.mailgun.net - Add
o:testmode=yesto check a send without delivering it - Verify a custom domain first. The sandbox domain reaches only 5 authorised recipients
Postmark API + MCP
- Install @activecampaign/postmark-mcp, never the unscoped postmark-mcp package
- Use the token
POSTMARK_API_TESTto check a payload without sending - Set
MessageStreamtooutboundfor transactional mail and a broadcast stream for bulk - Set
WEBHOOK_URL_ALLOWLISTso a misled createWebhook call can't send events to someone else's server - Have a webhook endpoint answer 200 for every selected event before creating it. Postmark tests it and won't save on failure unless
verify=falseis passed
Questions
Which is better for AI agents, Mailgun API + MCP or Postmark API + MCP?
Mailgun API + MCP scores 71.8 (BB) on agent readiness against Postmark API + MCP's 67.4 (B), and leads in 4 of 7 scored categories. Postmark API + MCP leads on agent ergonomics and transparency & trust.
Do Mailgun API + MCP and Postmark API + MCP need an API key?
Both need an API key.
Can an agent call Mailgun API + MCP and Postmark API + MCP without installing anything?
Yes. Mailgun API + MCP has a hosted endpoint at https://api.mailgun.net/v3 and Postmark API + MCP at https://api.postmarkapp.com.
Other comparisons with Mailgun API + MCP or Postmark API + MCP
- AhaSend API + MCP vs Mailgun API + MCP
- AhaSend API + MCP vs Postmark API + MCP
- Amazon SES vs Mailgun API + MCP
- Amazon SES vs Postmark API + MCP
- Brevo API + MCP vs Mailgun API + MCP
- Brevo API + MCP vs Postmark API + MCP
- Cloudflare Email Service vs Mailgun API + MCP
- Cloudflare Email Service vs Postmark API + MCP
- Groundmail API + MCP vs Mailgun API + MCP
- Groundmail API + MCP vs Postmark API + MCP
- Loops API + MCP vs Mailgun API + MCP
- Loops API + MCP vs Postmark API + MCP
- MailerSend vs Mailgun API + MCP
- MailerSend vs Postmark API + MCP
- Mailgun API + MCP vs Mailjet API + MCP
- Mailgun API + MCP vs MailPace
- Mailgun API + MCP vs Mailtrap Email API + MCP
- Mailgun API + MCP vs Mailchimp Transactional (Mandrill)
- Mailgun API + MCP vs Resend API + MCP
- Mailgun API + MCP vs Twilio SendGrid
- Mailgun API + MCP vs SendLayer
- Mailgun API + MCP vs SMTP2GO API + MCP
- Mailgun API + MCP vs Zoho CPaaS (formerly ZeptoMail)
- Mailjet API + MCP vs Postmark API + MCP
- MailPace vs Postmark API + MCP
- Mailtrap Email API + MCP vs Postmark API + MCP
- Mailchimp Transactional (Mandrill) vs Postmark API + MCP
- Postmark API + MCP vs Resend API + MCP
- Postmark API + MCP vs Twilio SendGrid
- Postmark API + MCP vs SendLayer
- Postmark API + MCP vs SMTP2GO API + MCP
- Postmark API + MCP vs Zoho CPaaS (formerly ZeptoMail)
Machine-readable
- This page as Markdown
/compare/mailgun-vs-postmark.md· slim.min.md· JSON.json(or sendAccept: text/markdown) - Each listing in full
/api/v1/tools/mailgun.json·/api/v1/tools/postmark.json - From a terminal
anchor compare mailgun postmark(the CLI) - Over MCP
compare_tools {"a": "mailgun", "b": "postmark"}at/mcp, no key