Head to head · Sending email · October 2026 research run

Postmark API + MCP vs Resend API + MCP

Resend API + MCP scores 81.2 (A) on agent readiness against Postmark API + MCP's 67.4 (B), and leads in 6 of 7 scored categories. Postmark API + MCP leads on agent ergonomics. Both do sending email.

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

Which one, for what

Postmark API + MCP B

Best for Transactional mail where deliverability and a small, well-annotated MCP matter more than a free tier.

Ahead on

  • Agent ergonomics, 79 against 67

Watch for

No OpenAPI spec and no published request-rate limit

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 60
  • Schema & documentation, 95 against 81
  • Security & auth, 69 against 63
  • Payments & pricing, 75 against 60
  • Maintenance & community, 93 against 80
  • Transparency & trust, 83 against 78

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

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 +30

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.

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

Postmark API + MCP 60

No x402, MPP or L402 (0). Prices and per-1,000 overage ($1.80, $1.30, $1.20) published without login, re-read on 1 November (20). Developer plan of 100 emails a month with no card (20). Browser signup and a manual account review before sending outside your own domains (0). 0 + 20 + 20 + 0 = 40. 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.

Schema & documentation Resend API + MCP +14

Postmark API + MCP 81

No OpenAPI spec for the REST API. Every one of the 24 MCP tools has a typed Zod schema, so half (15). llms.txt of about 1,100 lines with code samples, per the 1 October check (10). MCP descriptions state the purpose and point to the right alternative, such as 'Use sendBatch to send multiple distinct messages' (16). Typed inputs with email validation, a 50-recipient cap and the 22 bounce types as an enum (13). More than 40 JSON error codes grouped by area, with examples, re-read on 1 November (14). Dated product updates and a semver CHANGELOG for the MCP server, but no API versioning (13). 15 + 10 + 16 + 13 + 14 + 13 = 81.

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).

Maintenance & community Resend API + MCP +13

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.

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).

Agent ergonomics Postmark API + MCP +12

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.

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).

Security & auth Resend API + MCP +6

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.

Resend API + MCP 69

Bearer keys with full_access or sending_access, and a sending key can be limited to one domain. The hosted MCP signs in by OAuth with no documented scope choice (25). Sending-only keys exist, but the MCP has no read-only mode, and with a full key an agent can create keys and remove domains (10). get-received-email and the new inbox thread tools hand inbound mail to the model. Since resend-mcp 2.25.0 (6 October) local file reads by send-email attachments and create-contact-import are off over HTTP unless --allowed-file-dirs is set, and the README tells stdio users to set it to stop a prompt-injected agent attaching files outside chosen folders. That's a documented mitigation for one injection path, with no guidance on treating received mail as untrusted (4). Before 2.25.0 any local file path could be attached, including over HTTP, where a remote caller could read the server's disk; the maintainers fixed it and disclosed it in the README, read as Mapbox's 5 October fix was, as part of a public programme rather than a deduction. API request logs with full request and response bodies (14). SOC 2 Type II, an annual penetration test, a responsible-disclosure page and a security.txt with Contact and Policy but no Expires field, re-read on 1 November (16). 25 + 10 + 4 + 14 + 16 = 69.

Score by category

CategoryWeightPostmark API + MCPResend API + MCPEdge
Reliability16%6090Resend API + MCP +30
Performance10%pendingpendingpendingnot scored in this run
Schema & documentation13%8195Resend API + MCP +14
Agent ergonomics13%7967Postmark API + MCP +12
Security & auth14%6369Resend API + MCP +6
Payments & pricing10%6075Resend API + MCP +15
Task success10%pendingpendingpendingnot scored in this run
Maintenance & community7%8093Resend API + MCP +13
Transparency & trust7%7883Resend API + MCP +5
Negative events≤15-30
TotalB 67.4/100A 81.2/100

Facts side by side

FactPostmark API + MCPResend API + MCP
KindHTTP APIHTTP API
VendorPostmark (ActiveCampaign)Resend
Hosted endpointhttps://api.postmarkapp.comhttps://api.resend.com
TransportsHTTP, stdioHTTP, Streamable HTTP, stdio
AuthAPI keyOAuth or key
PricingFreemiumFreemium
x402nono
LicenceMITMIT
Tools exposed24136
Read-only variant documentednono
llms.txtyesyes
Last release2026-10-292026-10-30
Terms last updated2024-12-10no date given
Privacy policy last updated2026-10-01no date given
Customer content may train modelsyesnot found in the text
Terms restrict automated accessyesnot 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
Popularity57 stars, 1.3M npm/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

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.

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

Postmark API + MCP

  1. Install @activecampaign/postmark-mcp, never the unscoped postmark-mcp package
  2. Use the token POSTMARK_API_TEST to check a payload without sending
  3. Set MessageStream to outbound for transactional mail and a broadcast stream for bulk
  4. Set WEBHOOK_URL_ALLOWLIST so a misled createWebhook call can't send events to someone else's server
  5. Have a webhook endpoint answer 200 for every selected event before creating it. Postmark tests it and won't save on failure unless verify=false is passed

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, Postmark API + MCP or Resend API + MCP?

Resend API + MCP scores 81.2 (A) on agent readiness against Postmark API + MCP's 67.4 (B), and leads in 6 of 7 scored categories. Postmark API + MCP leads on agent ergonomics.

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

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

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

Yes. Postmark API + MCP has a hosted endpoint at https://api.postmarkapp.com and Resend API + MCP at https://api.resend.com.

Other comparisons with Postmark 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.