"compare": ["receiver.email", "agentmail"]
Receiver.email vs AgentMail
AgentMail is an email provider built for AI agents: each inbox is a full mailbox that sends and receives, keeps threads and drafts, and can live on your own domain, with a hosted MCP server, a CLI and Python and Node SDKs. Receiver.email is receive-only: an agent or a test makes up an address, hands it to a sign-up form, and one call returns the email with the code and links extracted. The address can't send.
If your agent sends email, replies or holds conversations, choose AgentMail. If it only has to get through “check your email for a code”, and you want unlimited addresses, the code returned on its own, and the same inboxes in your test suite, Receiver.email is the simpler fit.
Pick AgentMail if
Your agent sends, replies or drafts email, needs a lasting identity on your own domain, or you need MCP over OAuth, WebSockets or prompt-injection screening.
Pick Receiver.email if
Your agent only needs codes, magic links and confirmations, must not be able to send, should use a fresh address per task, or your tests need the same inboxes through SDKs.
Last checked November 2026.
Feature by feature.
| Feature | Receiver.email | AgentMail |
|---|---|---|
| How mail arrives | Public catch-all: any-prefix-<project>@receiver.email, from any sender | Inboxes created through the API, on agentmail.to or your own domain |
| Addresses | Unlimited per project, no setup per address | 3 inboxes (Free), 10 (Developer), extra inboxes $2/month each |
| Free option | Free plan: 100 emails/month, 1 project | Free plan: 3 inboxes, 3,000 emails/month (100/day), 3 GB, no card |
| Entry paid plan | Starter: $29/month, 10,000 emails/month | Developer: $20/month, 10 inboxes, 10,000 emails/month |
| Retention | 7 days (Free), 30 (Starter), 90 (Pro), up to 365 (Enterprise) | No fixed period stated; 3 GB (Free) or 10 GB (Developer) of storage |
| Wait for an email | One call: wait_for_email (MCP), waitFor() (SDKs), receiver wait (CLI) | No long-poll documented; new mail arrives by webhook or WebSocket |
| Verification code extraction | wait_for_email with extract: "otp", or waitForOtp() | Not listed; extracted_text strips quoted replies |
| Link extraction | Yes | n/c |
| Signed webhooks on arrival | Yes | Yes |
| Live stream of new mail | Server-sent events | WebSockets |
| Send or reply to external addresses | No. Receive-only (a test email to your own address) | Yes: send, reply and drafts |
| Threads, drafts and labels | No | Yes |
| SMTP and IMAP access | No | Yes |
| Custom domains | Roadmap | 1 on Free, 10 on Developer |
| Prompt-injection screening | No | Agent Armor |
| Client libraries | TypeScript, Python | Python, Node |
| MCP server for AI agents | Yes: hosted (mcp.receiver.email, API key) or local (npx) | Hosted remote server (OAuth or API key) |
| Command-line client | Yes | agentmail-cli |
| Self-hosting or your own cloud | No, cloud only | Bring-your-own cloud on Enterprise |
Last checked November 2026. Competitor details come from each vendor's own pricing and documentation pages, listed below. Plans change, so confirm on their site before you buy. n/c means we could not confirm it from those pages, not that it's missing. Spotted something out of date? Email [email protected].
When to choose AgentMail
- The agent sends email: outreach, support replies, scheduling or follow-ups.
- It needs a lasting identity, on your own domain.
- You want threads, drafts for human review, labels or calendars.
- Your MCP client can only connect with OAuth (Receiver.email's hosted server takes the API key in an Authorization header).
- You want real-time WebSockets, or prompt-injection screening of inbound mail (Agent Armor).
- You need an EU region or a bring-your-own-cloud deployment on an enterprise plan.
When to choose Receiver.email
- The agent only needs codes, magic links or confirmations: one tool call returns them.
- The agent must not be able to send email: a Receiver.email address only receives.
- You want a fresh address for every task or test run, with no inbox count to manage.
- You want the code returned on its own, not the whole email in the agent’s context.
- Your test suite uses the same inboxes, through TypeScript and Python SDKs whose waits throw on a timeout.
Moving from AgentMail
Only receive-only work moves over. If an agent signs up, verifies and reads confirmations, give it the Receiver.email MCP server and let it call create_inbox per task, then wait_for_email with extract: "otp": the wait and the code come back in one tool call, with no webhook to receive.
If the agent sends or replies, keep AgentMail for that; Receiver.email can't send.
| AgentMail | Receiver.email |
|---|---|
| API key | Project API key (RECEIVER_API_KEY) |
| An inbox created through the API, counted per plan | create_inbox or inboxes.create({ prefix }): any number |
| A webhook or WebSocket for new mail | wait_for_email or emails.waitFor(), or a signed email.received webhook |
| Reading the code out of extracted_text | wait_for_email with extract: "otp", or emails.waitForOtp(...).code |
| Hosted MCP server | Hosted at https://mcp.receiver.email/mcp (API key header), or local: npx -y @receiverdotemail/mcp |
| Sending and replying | Not available: keep AgentMail for agents that send |
claude mcp add receiver \
-e RECEIVER_API_KEY=recv_live_... \
-- npx -y @receiverdotemail/mcp{
"mcpServers": {
"receiver": {
"command": "npx",
"args": ["-y", "@receiverdotemail/mcp"],
"env": { "RECEIVER_API_KEY": "recv_live_..." }
}
}
}create_inbox({ "prefix": "acme" })
→ { "address": "[email protected]",
"since": "2026-11-05T10:00:00.000Z" }
wait_for_email({ "address": "[email protected]",
"since": "2026-11-05T10:00:00.000Z",
"extract": "otp" })
→ { "status": "received",
"email": { "from": "[email protected]", "subject": "Your Acme code", ... },
"otp": { "code": "847291", "candidates": [...] } }# Hosted agents and the Claude API: the same tools at a URL
# https://mcp.receiver.email/mcp
# Authorization: Bearer recv_live_...
# Claude Code, remote instead of local
claude mcp add --transport http receiver https://mcp.receiver.email/mcp \
--header "Authorization: Bearer recv_live_..."npm install -g @receiverdotemail/cli
export RECEIVER_API_KEY=recv_live_...
ADDRESS=$(receiver inbox new --prefix acme)
# ...the agent signs up with $ADDRESS...
receiver otp "$ADDRESS" --timeout 60 # prints 847291, exit code 2 on timeoutFull walkthrough in the Quick Start. Plans and limits are on the pricing page.
Try it on one test
Free tier: 100 emails a month, one project, unlimited addresses. No credit card required.