Niches · Email delivery APIs

An agent sends one email as a tool call (report, alert, artifact)

Two or three companies' docs show a full fit.

2companies, full fit
13companies, fit with a limit
47companies carry the tag
23share of the category's work
10first-hand accounts

What counts as done

Precisely one message delivered per intended send, including after a timeout and retry, from an MCP whose tool schemas load in the model API without error.

Measured, for our own tests: the send takes at most 2 tool calls. No docs we read state these figures, so they don't count against a listing here.

How agents ask for it: email me when the job finishes, send me the morning summary, email this design doc to me, warn me by email if the server is down

Does the job 2

The docs show it meets the test above, and nothing we read says otherwise.

ListingWhy
MailPace C
OhMySMTP Ltd
@mailpace/mcp 2.0.1 is on npm under the vendor scope, its send tool takes idempotency_key mapped to the Idempotency-Key header, and the server token can only send from its one domain. source
Resend API + MCP A
Plus Five Five, Inc.
The official MCP's email tools take idempotencyKey, a sending_access key can be limited to one domain, and e14, e15 and e32 run agents that email through Resend. The ChatGPT plugin that dropped the key (e21) was fixed on 15 September 2026. source

Does the job, with a limit 13

It does the job, but something in the docs or a user's account will get in an agent's way. The limit is named in each row.

ListingWhy
AhaSend API + MCP BB
AhaSend B.V.
The HTTP send takes Idempotency-Key, but the hosted MCP's send_email and send_conversation_email schemas carry no idempotency field, so a retried tool call can send twice. Snake_case keys and short tool names load cleanly; 91 tools with every scope. source
Amazon SES BB
Amazon Web Services, Inc.
Agents reach SES through the general AWS MCP Server and the amazon-ses skill, under AWS's own namespace, but SendEmail has no idempotency token, so a retried call can send twice, and SigV4 or OAuth sign-in comes first. source
Brevo API + MCP E
Sendinblue SAS
None of the MCP server's 27 modules sends transactional email, and the MCP token has full account access. An agent must call the REST send, whose idempotencyKey header is documented for batch sends with a 30-minute TTL. source
Cloudflare Email Service B
Cloudflare, Inc.
An agent can call REST or a Worker binding, but the send takes no idempotency key and the Email Service docs name no email MCP tool; a token with send permission reaches every onboarded domain. source
Groundmail API + MCP B
Power Only Transit Inc. dba Groundmail
The MCP send_email tool's schema has no idempotency_key (only the mailbox send and reply tools do), so a retried call can send twice. Send-only OAuth grants and allowed_domains keys limit what the agent can do. source
Loops API + MCP B
Astrodon Corporation
The OAuth MCP at mcp.loops.so sends a published transactional email, and the HTTP send takes Idempotency-Key with a 409 on reuse within 24 hours. Whether the MCP tool exposes the key wasn't documented, ad hoc bodies aren't possible, and keys aren't scoped. source
MailerSend BB
MailerSend, Inc.
The hosted OAuth MCP has send_email and a create_token tool for scoped tokens, but neither the send endpoint nor the tool documents an idempotency key, so a retry can deliver twice; 127 tools load with no toolsets. source
Mailgun API + MCP BB
Mailgun Technologies, Inc.
The colon property names and over-64-character tool name that broke Claude (e19, e20) were fixed in issues closed on 9 February 2026, but sends take no idempotency key, and open issue 31 says generated tools carry no annotations. source
Mailtrap Email API + MCP B
Railsware Products Studio LLC
The local MCP (npm mcp-mailtrap, named in the vendor README) has send-email and batch-send tools, but no idempotency key exists on sends, so a retry can deliver twice; about 130 tools load at once. source
Mailchimp Transactional (Mandrill) B
The Rocket Science Group LLC d/b/a Mailchimp
The hosted MCP at mandrillapp.com/mcp has nine tools, sending through a generic call_api, and messages/send takes no idempotency key, so a retried call can send twice. source
Postmark API + MCP B
AC PM, LLC
@activecampaign/postmark-mcp is the vendor-scoped package (e17 is the unscoped backdoor), but the API and MCP have no idempotency key, and open issue 54 (e18) shows Claude resending an email on its own. source
SendLayer D
SendLayer, LLC
The hosted MCP's send-email tool covers CC, BCC, attachments and headers, but sends take no idempotency key and API keys can't be scoped, so a retry can deliver twice from a full-access key. source
SMTP2GO API + MCP B
Sand Dune Mail Ltd
The hosted MCP at developers.smtp2go.com/mcp is a docs server whose untyped execute-request tool calls any endpoint the key allows; sends take no idempotency key. A key limited to /email/send and an allowed-recipients list bound what it can do. source

Doesn't do this job 3

Listings in the category that do something else, with the reason.

ListingWhy
Mailjet API + MCP C
Mailjet SAS
The Mailjet MCP server registers GET-only tools and cannot send, and the docs index shows no idempotency key on Send API v3.1, so an agent sending by API can double-send on retry. source
Twilio SendGrid BB
Twilio Inc.
Twilio publishes no SendGrid MCP that sends (only docs search), and mail/send has no idempotency key, so the success's single delivery after retry can't be met through an MCP. source
Zoho CPaaS (formerly ZeptoMail) C
Zoho Corporation
No MCP server is documented (the llms.txt index has none), and the send takes no idempotency key; client_reference is a tracking label only. source

What stops agents finishing

  • MCP schema rejected by the model API (property names, tool name length)
  • no idempotency key on the MCP send tool, so a retry double-sends
  • malicious look-alike MCP package

Around it

Before: agent-harnesses.scheduled-job, personal-assistants.morning-brief. After: notifications.push.

Where this comes from

Weight 23 of 100 in Email delivery APIs: 10 of 32 accounts: scheduled or agent-driven sends to the owner (e14, e15, e32) and MCP send failures (e17 to e21, e30, e31)

The same as data: /api/v1/use-cases/email.agent-tool-send.json, or the MCP tool get_use_case with id email.agent-tool-send. Other jobs in this category: /api/v1/niches?category=email.

Draft, read 2026-11-15 from public docs and first-hand accounts, not yet reviewed by a person. A mark says what the docs show, not what a run measured.

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.