# MCPmailer vs Cloudflare Email Routing

Email Routing forwards inbound mail into a Worker for free. MCPmailer is the mailbox, thread store, and MCP surface you would build behind it.

Also searched as: Email Workers agent inbox, Cloudflare Email Routing alternative.

## What Cloudflare Email Routing is

Cloudflare Email Routing gives any domain on Cloudflare free inbound addresses that forward to a real mailbox or into an Email Worker, where you get the raw message in code. Paired with Cloudflare Email Service for sending, it is a very cheap two-way path.

## Where Cloudflare Email Routing is the better choice

If you are already living in Workers and want a receive-only hook at essentially no cost, Email Routing plus an Email Worker is hard to argue with. For internal alerting and small tools, use it and move on.

## Where MCPmailer differs

This is the cheapest possible starting point, and it is still only transport. You get a message in a Worker. You do not get a mailbox, a thread, a searchable history, per-agent keys, quotas that separate replies from cold outreach, or a dashboard. We are those things, running on the same class of infrastructure.

### Nothing is stored

An Email Worker sees the message once. If you want to answer "what did we tell this customer in March", you are building storage, an index, and a retention policy. Ours keeps metadata in Postgres and raw MIME in R2, with full-text search across the workspace.

### Sending is a separate problem

Routing is inbound. The moment your agent replies you are back to a sending domain, DKIM alignment, bounce handling, complaint feedback loops, and suppression. That is the half where reputations are lost, and it is not what Email Routing is for.

### The agent still needs tools

A Worker with a message in it is not an interface a model can use. You would write the MCP server, the tool schemas, the auth, and the error strings. That layer, and keeping it current with the spec, is the thing we maintain.

## When Email Workers is enough

Be honest about which of these you are doing.

1. **Receive-only automation** Parse an alert, trigger a job, done. Email Routing is free and correct.
2. **Anything that replies to a person** You now need a sending identity, suppression, and bounce handling. That is where this stops being free.
3. **Anything a human must review** A dashboard over threads is not something you want to build in a Worker.

## Side by side (checked July 2026)

| | MCPmailer | Cloudflare Email Routing |
| --- | --- | --- |
| Built for | Agents holding conversations. The mailbox is the product, not an endpoint bolted onto a sender. | Routing inbound mail on a Cloudflare domain. |
| Inbox per agent | One mailbox per agent, created from the dashboard or the API, each with its own scoped key. | Addresses, not mailboxes. No storage. |
| Receiving and threading | Received, parsed, threaded, and stored, so a reply arrives as part of a conversation rather than as a webhook body. | Yes, forwarded or delivered into an Email Worker. |
| MCP server | Native. Streamable HTTP with a bearer key, or OAuth 2.1 for clients that cannot hold one. | No. You would write the MCP server yourself. |
| Waiting for a reply | wait_for_reply long-polls the mailbox until the other side answers, up to five minutes per call. | No. |
| Human oversight | Every thread is readable in your dashboard and you can take any of them over yourself. | Routing rules and logs. |
| Sending limits | Reply-first. Replies into an inbound thread are near-unrestricted; cold outreach is quota gated. | Sending policy belongs to whatever you send through. |
| Your domain | Instant you.mcpmailer.email subdomain, then verify agents.yourcompany.com with a guided DNS wizard. | Your domain, on Cloudflare DNS. |
| Search | Full-text search across the workspace, exposed to the agent as search_inbox. | None. Nothing is stored. |
| Beyond the inbox | A shared contact book with per-contact memory, notes, an encrypted vault, and a public hostname per agent. | The rest of the Workers platform, if you want to build on it. |
| Free tier | 3,000 emails a month, 100 a day, 3 inboxes, no card. | Free for routing. |
| Content privacy | We never read message content and never train on it. Enforcement is behavioral and metadata only. | Your own code sees the message. |

## Questions

### Is MCPmailer built on Cloudflare?

The application, MCP server, queues, and per-mailbox coordination run on Cloudflare; the mail path in both directions is SES. So the comparison is between using the raw pieces and using the product built from them.

### Can I use Email Workers to give an agent an inbox?

For receiving, yes, cheaply. You will add a sending path, storage, threading, search, and an MCP server, at which point you have rebuilt this.

### What does Email Routing cost?

Routing is free on Cloudflare, which is exactly why it is worth comparing honestly rather than pretending it is not an option.

### Can an Email Worker reply to a message?

Not on its own. Replying means a sending path, which is Cloudflare Email Service or another provider, plus DKIM alignment, bounce handling, and suppression. That second half is where the work is.

All comparisons: https://mcpmailer.com/vs
Docs: https://mcpmailer.com/docs.md
Pricing: https://mcpmailer.com/pricing.md