# MCPmailer vs Forward Email

Forward Email is open-source forwarding with mailbox hosting and an API. MCPmailer is an agent mailbox with MCP tools and oversight.

Also searched as: Forward Email alternative, open source agent email, forwardemail.net for agents.

## What Forward Email is

Forward Email is an open-source forwarding service that has grown into mailbox hosting, with plans from about three dollars a month that include sending, storage, and API access. Being able to read the code and self-host it is a genuine differentiator.

## Where Forward Email is the better choice

If open source matters to you, or you want the option of self-hosting the whole thing later, Forward Email is the strongest choice on this page and we have no self-hosted distribution to offer against it.

## Where MCPmailer differs

It gives you mail. We give an agent a way to work: threading on ingest, a blocking wait, reply-first quotas, contact memory, and a dashboard for the person accountable. The gap is not storage, it is everything shaped around the agent using it.

### A mailbox with an API is not an agent interface

IMAP, SMTP, and a REST API are the right primitives for a mail client. A model does better with get_thread, search_inbox, wait_for_reply, and refusals that explain themselves, because it cannot assemble MIME or decide a quota policy on its own.

### Reply-first quotas

A mail host applies one sending limit. Our pre-send pipeline classifies each message and refuses cold outreach with a structured reason and a reset time, which is what stops a confused agent from becoming a spam incident.

### Supervision as a product surface

Nothing in a mail host shows a non-technical colleague what an agent has been saying. That dashboard, and the ability to take a thread over mid-conversation, is a large part of what we are.

## Which to choose

This one splits on values as much as features.

1. **Open source matters most** Use Forward Email. You can read it, and you can leave with your data and your code.
2. **Agent behaviour matters most** Come here for threading, quotas, memory, and oversight built around an agent.
3. **Both** Personal aliases there, agent addresses here, on a subdomain of the same domain.

## Side by side (checked July 2026)

| | MCPmailer | Forward Email |
| --- | --- | --- |
| Built for | Agents holding conversations. The mailbox is the product, not an endpoint bolted onto a sender. | Forwarding and mailbox hosting, openly. |
| Inbox per agent | One mailbox per agent, created from the dashboard or the API, each with its own scoped key. | Mailboxes and aliases, priced per plan. |
| Receiving and threading | The mailbox is the destination, not a hop. Mail is stored, threaded, and searchable where it lands. | Yes, with storage on paid plans. |
| MCP server | Native. Streamable HTTP with a bearer key, or OAuth 2.1 for clients that cannot hold one. | No. |
| Waiting for a reply | wait_for_reply long-polls the mailbox until the other side answers, up to five minutes per call. | IMAP idle or polling. |
| Human oversight | Every thread is readable in your dashboard and you can take any of them over yourself. | Account and log surfaces. |
| Sending limits | Reply-first. Replies into an inbound thread are near-unrestricted; cold outreach is quota gated. | Host sending limits. |
| Your domain | Instant you.mcpmailer.email subdomain, then verify agents.yourcompany.com with a guided DNS wizard. | Your own domain. |
| Search | Full-text search over mail the workspace actually holds, rather than over whatever the destination kept. | Mailbox search. |
| Beyond the inbox | A shared contact book with per-contact memory, notes, an encrypted vault, and a public hostname per agent. | Nothing agent shaped. |
| Free tier | 3,000 emails a month, 100 a day, 3 inboxes, no card. | Free forwarding, paid plans for sending and storage. |
| Content privacy | We never read message content and never train on it. Enforcement is behavioral and metadata only. | Strong, open source, and self-hostable. |

## Questions

### Can I self-host MCPmailer?

No, and if that is a requirement Forward Email is the better answer. Dedicated infrastructure is an enterprise conversation, but there is no self-hosted distribution.

### Is Forward Email enough for an AI agent?

It gives the agent a real mailbox with an API, which is more than a pure forwarder. You still build threading policy, cold-send controls, memory, and supervision.

### Which is cheaper?

Forward Email, on plan price. What we add is agent-shaped: threading, quotas, contact memory, and a dashboard.

### Can I run both on one domain?

Yes. Keep personal aliases there and give agents their own subdomain, so the two MX setups never collide.

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