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

> An agent sends one email as a tool call (report, alert, artifact): 2 companies fully do it, 13 with a limit, 47 carry the tag. Every listing in Email delivery APIs with the reason and a source.

- Canonical: https://www.anchorterminal.com/niches/email.agent-tool-send/
- Markdown: https://www.anchorterminal.com/niches/email.agent-tool-send/index.md (~1,750 tokens)
- Slim: https://www.anchorterminal.com/niches/email.agent-tool-send/index.min.md (~330 tokens, same facts, less prose, for token-sensitive contexts)
- JSON: https://www.anchorterminal.com/niches/email.agent-tool-send/index.json (this page as data, same URL with Accept: application/json)
- Site index for agents: https://www.anchorterminal.com/llms.txt (the key docs and every listing in one file, at most 16 MB, about 4 million tokens: https://www.anchorterminal.com/llms-full.txt)
- API: https://www.anchorterminal.com/api/v1/index.json
- MCP: https://www.anchorterminal.com/mcp (the whole catalogue as tools, no key)
- DNS: dig +short TXT <slug>.grade.anchorterminal.com (the grade as a DNS TXT record, for a sandbox with no HTTP where names still resolve; also top., best.<category>. and <a>.vs.<b>. under the zone, and the same under grade.letme.dev)
- Licence: CC BY 4.0, credit Anchor Terminal and link this page (https://www.anchorterminal.com/terms/#data)
- Updated: 2026-11-15

Two or three companies' docs show a full fit.

| Companies, full fit | With a limit | Carry the tag | Share of the category's work | First-hand accounts |
| --- | --- | --- | --- | --- |
| 2 | 13 | 47 | 23 | 10 |

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

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

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

- **MailPace (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.
- **Resend API + MCP (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.

## Does the job, with a limit

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.

- **AhaSend API + MCP (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.
- **Amazon SES (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.
- **Brevo API + MCP (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.
- **Cloudflare Email Service (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.
- **Groundmail API + MCP (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.
- **Loops API + MCP (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.
- **MailerSend (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.
- **Mailgun API + MCP (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.
- **Mailtrap Email API + MCP (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.
- **Mailchimp Transactional (Mandrill) (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.
- **Postmark API + MCP (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.
- **SendLayer (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.
- **SMTP2GO API + MCP (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.

- not this job: Mailjet API + MCP (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.
- not this job: Twilio SendGrid (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.
- not this job: Zoho CPaaS (formerly ZeptoMail) (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.

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

As data: https://www.anchorterminal.com/api/v1/use-cases/email.agent-tool-send.json, or the MCP tool get_use_case with id email.agent-tool-send. Draft, read 2026-11-15 from public docs and first-hand accounts, not yet reviewed by a person.

---

Query this catalogue directly over MCP: https://www.anchorterminal.com/mcp (Streamable HTTP, no key). How: https://www.anchorterminal.com/agents/#mcp
