| What it is | Local app, CLI and MCP server that connects an agent to your existing mailbox. | Hosted API that creates new email inboxes for agents. |
|---|
| Your existing mailbox | Yes: Microsoft 365 and Outlook.com through Microsoft Graph, any IMAP server (Gmail, Aruba, Libero…). | Not offered: it creates new inboxes on @agentmail.to or on your custom domain. |
|---|
| Where mail lives | On your computer. GigaMail runs no servers and receives nothing. | In AgentMail’s cloud: United States; an EU region on the Enterprise plan. |
|---|
| Source code | Open source, AGPL-3.0, the whole product. | Closed service; SDKs, CLI and MCP bridge are open source (MIT). |
|---|
| Self-hosting | It runs on your machine by design. | Not offered; “BYO cloud deployment” is listed on Enterprise. |
|---|
| Price | Free. | Free: 3 inboxes, 3,000 emails a month. Developer $20/month, Startup $200/month, Enterprise on request. |
|---|
| MCP server | Local, over stdio, 30 tools, no network port. | Hosted over HTTP, 47 tools, OAuth or API key. |
|---|
| Before a send | Every send, reply, move or delete waits for a person’s approval out of band (Windows Hello / Touch ID). The agent cannot approve. | The agent sends through the API. For human review, the docs suggest drafts plus API keys without send permission, which you configure. |
|---|
| Prompt injection | Mail reaches the agent as visible text only; hidden text is left out and flagged. Logins and setup are CLI only. | Agent Armor (in Labs, US only) gives inbound mail a clear or review verdict, described as advisory. |
|---|
| Sensitive data | In the console, the masker hides tax codes, VAT numbers, IBANs and phone numbers before a mail goes to the agent for a draft, and puts them back in the draft. The same filter on the MCP side is planned. | No masking or redaction feature found in the docs. |
|---|
| Built for | People and teams who want an agent to help with their own mail. | Developers building agents and products that need email of their own. |