Forward Email is open-source forwarding with mailbox hosting and an API. MCPmailer is an agent mailbox with MCP tools and oversight.
Forwarding and aliases · Forward Email claims checked July 2026
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.
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.
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.
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.
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.
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.
Every row is a claim we could defend with their documentation open beside it. Where they are ahead, the row says so.
This one splits on values as much as features.
Open source matters most
Use Forward Email. You can read it, and you can leave with your data and your code.
Agent behaviour matters most
Come here for threading, quotas, memory, and oversight built around an agent.
Both
Personal aliases there, agent addresses here, on a subdomain of the same domain.
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.
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.
Forward Email, on plan price. What we add is agent-shaped: threading, quotas, contact memory, and a dashboard.
Yes. Keep personal aliases there and give agents their own subdomain, so the two MX setups never collide.
Forwarding is the cheapest way to receive at an address you own, and it is a delivery mechanism rather than a mailbox. When the agent needs to hold the conversation rather than pass it along, that is this.
The free tier is 3,000 emails a month across three agent inboxes, no card, with receiving, threading, and search included. Enough to watch a real conversation happen before you decide.
More Forwarding and aliases