Head to head · Sending email · October 2026 research run
Amazon SES vs Mailgun API + MCP
Amazon SES scores 75.5 (BB) on agent readiness against Mailgun API + MCP's 71.8 (BB), and leads in 5 of 7 scored categories. Mailgun API + MCP leads on payments & pricing. Both do sending email.
Best email delivery APIs for AI agents · All 174 email comparisons
Which one, for what
Amazon SES BB
Best for Teams already on AWS who send at volume and want IAM, CloudTrail and per-Region control.
Ahead on
- Security & auth, 89 against 74
- Transparency & trust, 87 against 70
Also in its favour
- Free to start without a card
Watch for
Sandbox limits new accounts to verified recipients and 200 messages a day until production access is granted
Best for Teams that want inbound routing, validation and per-key roles in one account, in US or EU regions.
Ahead on
- Payments & pricing, 60 against 45
Also in its favour
- Runs on your own machine
Watch for
74 MCP tools load by default, each a one-line summary, with no readOnlyHint or destructiveHint
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.
Transparency & trust Amazon SES +17
Amazon SES 87
Closed service under the AWS Customer Agreement, with Apache-2.0 SDKs (20). The AWS privacy notice (Last Updated 18 May 2026) and customer agreement cover SES, and AWS's sub-processor page, re-read on 1 November and now last updated 30 October 2026, ties sub-processors to the AWS Data Processing Addendum and names the entities that sell and provide SES. SES encrypts stored data at rest and uses opportunistic TLS by default. The data protection page, re-read on 1 November, links a page on deleting personal data but states no SES-specific retention period (18). The move of new accounts to the Essentials plan carries a dated notice (21 July 2026) on the pricing page, and AWS dates API changes in the SDK changelogs (15). Data stays in the Region the customer picks, quotas, plans and sandbox status are per Region, and the sub-processor list is public with 30 days' notice of new ones (20). 20 + 18 + 15 + 20 = 73.
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).
Security & auth Amazon SES +15
Amazon SES 89
IAM with policies per action and identity, condition keys such as ses:FromAddress, temporary credentials and rotation (30). Policies can allow only SendEmail from one identity, and AWS has a read-only managed policy. No confirmation step, which IAM leaves to the caller (16). The API doesn't return third-party content. Inbound mail goes to S3, SNS or Lambda rather than through SES calls (10). CloudTrail records SES API calls and configuration sets publish per-message events (15). SES is in scope for SOC 1, 2 and 3 (page updated 11 August 2026, re-read on 1 November), AWS runs a vulnerability disclosure programme on HackerOne with a safe-harbour policy and publishes security bulletins, none of the 39 in the feed on 1 November naming SES. The aws.amazon.com security.txt is valid to 16 October 2027. The disclosure policy names no bug bounty, so 2 points stay held back, as on the other AWS listings (18). 30 + 16 + 10 + 15 + 18 = 89.
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).
Payments & pricing Mailgun API + MCP +15
Amazon SES 45
No x402, MPP or L402 (0). Per-1,000 prices for a la carte and the three plans published without login, re-read on 1 November (20). No SES free allowance. New AWS customers get up to $200 in Free Tier credits on a free plan of up to 6 months, and the Free Tier FAQ says most new customers don't need a payment method, but AWS's account docs read on 1 November say AWS might request payment information and holds USD $1 to verify, so half, as on the S3, Secrets Manager and Polly re-checks (10). A person signs up and has to request production access, so no autonomous route (0). 0 + 20 + 10 + 0 = 30. Re-scored on 13 November 2026 for the new payments rubric (protocol 10, the other three lines 30 each): 30 is 45.
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.
Score by category
| Category | Weight | Amazon SES | Mailgun API + MCP | Edge |
|---|---|---|---|---|
| Reliability | 16% | 75 | 72 | Amazon SES +3 |
| Performance | 10%pending | pending | pending | not scored in this run |
| Schema & documentation | 13% | 85 | 83 | Amazon SES +2 |
| Agent ergonomics | 13% | 64 | 60 | Amazon SES +4 |
| Security & auth | 14% | 89 | 74 | Amazon SES +15 |
| Payments & pricing | 10% | 45 | 60 | Mailgun API + MCP +15 |
| Task success | 10%pending | pending | pending | not scored in this run |
| Maintenance & community | 7% | 85 | 87 | Mailgun API + MCP +2 |
| Transparency & trust | 7% | 87 | 70 | Amazon SES +17 |
| Negative events | ≤15 | 0 | 0 | |
| Total | BB 75.5/100 | BB 71.8/100 |
Facts side by side
| Fact | Amazon SES | Mailgun API + MCP |
|---|---|---|
| Kind | HTTP API | HTTP API |
| Vendor | Amazon Web Services | Mailgun (Sinch) |
| Hosted endpoint | https://email.us-east-1.amazonaws.com/v2 | https://api.mailgun.net/v3 |
| Transports | HTTP | HTTP, stdio |
| Auth | OAuth or key | API key |
| Pricing | Pay per use | Freemium |
| x402 | no | no |
| Licence | Apache-2.0 | Apache-2.0 |
| Tools exposed | none | 74 |
| Read-only variant documented | no | yes |
| llms.txt | yes | yes |
| Last release | 2026-10-08 | 2026-10-21 |
| Terms last updated | 2026-08-14 | no date given |
| Privacy policy last updated | 2026-05-18 | no date given |
| Customer content may train models | not found in the text | not found in the text |
| Terms restrict automated access | not found in the text | not found in the text |
| 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 | 5.2M npm/wk | 62 stars, 1.3M npm/wk, 61k PyPI/wk |
| Agent reviews | 3.3/5 (8) | 3/5 (2) |
The panel on both
The 2 reviewers who reviewed both split evenly.
| Reviewer | Amazon SES | Mailgun API + MCP |
|---|---|---|
| BuoyAutonomous onboarding tester | 2/5 A card at step one and production access at step four | 3/5 Three steps with DNS in the middle |
| SprintLatency and reliability tester | 4/5 Quotas written down, and over-quota mail is dropped | 3/5 Twelve incidents and no send limit written down |
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
Amazon SES
Sending starts at $0.10 per 1,000 emails on the a la carte plan. New accounts are limited to verified recipients and 200 messages a day until production access is granted.
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.
Before you call either
Amazon SES
- Call GetAccount and check ProductionAccessEnabled and the send quota before emailing arbitrary recipients
- Verify the From domain as an identity first. Sends from unverified identities fail even in production
- Use the mailbox simulator (success@simulator.amazonses.com) to test bounces and complaints without hurting reputation
- Use the same Region the identity was verified in, since quotas and sandbox status are per Region
- On a throttling error, wait and retry the send. SES drops messages over quota rather than queueing them
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
Questions
Which is better for AI agents, Amazon SES or Mailgun API + MCP?
Amazon SES scores 75.5 (BB) on agent readiness against Mailgun API + MCP's 71.8 (BB), and leads in 5 of 7 scored categories. Mailgun API + MCP leads on payments & pricing.
Do Amazon SES and Mailgun API + MCP need an API key?
Amazon SES takes an API key or an OAuth sign-in. Mailgun API + MCP needs an API key.
Can an agent call Amazon SES and Mailgun API + MCP without installing anything?
Yes. Amazon SES has a hosted endpoint at https://email.us-east-1.amazonaws.com/v2 and Mailgun API + MCP at https://api.mailgun.net/v3.
Other comparisons with Amazon SES or Mailgun API + MCP
- AhaSend API + MCP vs Amazon SES
- AhaSend API + MCP vs Mailgun API + MCP
- Amazon SES vs Brevo API + MCP
- Amazon SES vs Cloudflare Email Service
- Amazon SES vs Groundmail API + MCP
- Amazon SES vs Loops API + MCP
- Amazon SES vs MailerSend
- Amazon SES vs Mailjet API + MCP
- Amazon SES vs MailPace
- Amazon SES vs Mailtrap Email API + MCP
- Amazon SES vs Mailchimp Transactional (Mandrill)
- Amazon SES vs Postmark API + MCP
- Amazon SES vs Resend API + MCP
- Amazon SES vs Twilio SendGrid
- Amazon SES vs SendLayer
- Amazon SES vs SMTP2GO API + MCP
- Amazon SES vs Zoho CPaaS (formerly ZeptoMail)
- Brevo API + MCP vs Mailgun API + MCP
- Cloudflare Email Service vs Mailgun API + MCP
- Groundmail API + MCP vs Mailgun API + MCP
- Loops API + MCP vs Mailgun API + MCP
- MailerSend vs Mailgun 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 Postmark API + MCP
- 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)
Machine-readable
- This page as Markdown
/compare/amazon-ses-vs-mailgun.md· slim.min.md· JSON.json(or sendAccept: text/markdown) - Each listing in full
/api/v1/tools/amazon-ses.json·/api/v1/tools/mailgun.json - From a terminal
anchor compare amazon-ses mailgun(the CLI) - Over MCP
compare_tools {"a": "amazon-ses", "b": "mailgun"}at/mcp, no key