# Email for AI agents: AgentMail, Nylas or Command Mail?

> Should your agent get its own inbox, an email API or access to your existing mailbox? AgentMail, Nylas, Resend, Fluxmail and Command Mail compared, with prices.

Updated: 2026-10-19 · Fact-checked: 2026-10-19 · Canonical: https://commandmail.app/en/compare/email-for-ai-agents · Deutsch: https://commandmail.app/de/vergleich/e-mail-fuer-ki-agenten.md

The right email setup for an AI agent depends on one question: whose address does it write from? If the agent should have an address of its own, for a support bot or for signing up to services, agent inbox providers such as AgentMail, Nylas Agent Accounts or Cyberpigeon are built for that[^1][^4][^8]. If it should work with addresses you already use, it needs access to your mailbox, either directly through services like Fluxmail, MCP Emails or EmailEngine, or through a forwarding-based inbox such as Command Mail[^18][^20][^22][^24].

Command Mail is our product. Everything we say about other vendors comes from their pricing and documentation pages, read on 2026-10-19. We did not run these services side by side or create accounts with them. For Command Mail, we checked the rules in the production code that enforces them.

## Four ways to give an agent email

Agent email comes in a few distinct shapes, and the main difference is who owns the address the agent uses.

| Approach | Whose address | Examples | Built for | What you still build |
|---|---|---|---|---|
| Agent inbox | A new address used only by the agent | AgentMail, Nylas Agent Accounts, Cyberpigeon, Email for Agents, Shipmail, Open Agent Email | Developers and product teams | Agent logic, domain DNS, handling replies |
| Access to existing mailboxes | Your Gmail, Microsoft or IMAP addresses, or your users' | Nylas, EmailEngine, Fluxmail, MCP Emails | Software vendors; with Fluxmail and MCP Emails also individuals | Sign-in, permissions, and with an API the interface |
| Personal forwarding inbox | Your own addresses, gathered by forwarding | Command Mail | People who work with an agent in their own inbox | Forwarding at your current provider |
| Sending service with inbound | Your application's addresses | Resend, Postmark, Mailgun | Developers shipping an app | Mailbox logic, threads, agent access |

We placed vendors from their own descriptions. Nylas appears twice because one API covers both your users' connected accounts and accounts created for agents[^4][^5].

## Should the agent write as itself or as you?

A separate agent address keeps the agent's identity apart from yours. Replies, mistakes and sender reputation attach to something like support@ or agent@, and recipients can tell who they are dealing with. Nylas describes its Agent Accounts as a different model from pointing an agent at a person's inbox, with the account's own address, folders and calendar[^4]. When you connect a coding agent, Cyberpigeon can create a fresh inbox just for that app[^8].

If the agent replies to your clients, your accountant or your landlord, though, those people expect mail from you. Then the agent needs a way into your mailbox, and the real questions become how tightly you can scope what it may do and who signs off before anything is sent.

Plenty of workflows need both: an agent address for sign-ups and test messages, plus limited access to your own addresses for everything else.

## Are you building a product or using it yourself?

Developer platforms assume you will build an application around them. The Nylas MCP server needs an API key and a connected account, and Nylas recommends a dedicated IAM key with the narrowest permissions an agent needs[^6]. For connecting Google accounts, the Nylas Pro annual plan includes access to an add-on package with a shared Google app[^5].

EmailEngine runs on your own servers for 1,450 $ or 1,200 € a year regardless of mailbox count, with a 14-day trial[^18]. Its MCP endpoint is a labelled beta, off by default, and the tool list may still change between releases[^19].

If you are the one working with the agent, you mostly want to sign in, connect a mailbox and paste a server URL into Claude or another client. That is what Fluxmail Cloud, MCP Emails and Command Mail are designed for[^20][^22][^23].

## AgentMail vs Nylas vs Command Mail at a glance

The three names in the title stand for the three main routes: a dedicated agent inbox, a developer platform and a personal inbox.

| Criterion | AgentMail | Nylas | Command Mail |
|---|---|---|---|
| Whose address | New addresses for agents[^1] | New agent accounts or your users' connected accounts[^4] | Your existing addresses, gathered by forwarding[^24] |
| Built for | Developers building agents[^1] | Software vendors[^5] | People working with an agent in their own inbox[^23] |
| Create inboxes by API | Yes[^1] | Yes, as Agent Accounts[^4] | No; you or your agent connect addresses with the mailboxes permission[^24] |
| Sending on the free plan | Yes, up to 100 emails a day[^2] | Yes, within the Agent Account allowance[^5] | No, sending starts with Pro[^23] |
| Limiting access | Keys per organization, pod or inbox, permissions as an allow list[^3] | IAM keys bound to the narrowest permissions[^6] | Separate permissions for reading, drafting, approved and independent sending, autonomy per mailbox[^23] |
| Before sending | Leave out the send permission, confirm in the client[^1][^3] | A confirmation call that returns a hash; user consent is yours to build[^6] | Approval of one exact draft revision; independent sending only from mailboxes on auto[^23] |
| MCP sign-in | OAuth or API key[^1] | API key as a bearer token[^6] | OAuth 2.1 with PKCE[^23] |
| Data region | EU cloud on Enterprise[^2] | US by default, EU data region available[^6] | US operator, attachments in Cloudflare's EU jurisdiction[^25] |

## All providers compared

| Provider | Approach | Free start | First paid plan | Agent access |
|---|---|---|---|---|
| AgentMail | Agent inbox | 3 inboxes, 3,000 emails a month, 100 a day[^2] | Developer 20 $ a month, 10 inboxes[^2] | Hosted MCP with OAuth or API key, ChatGPT plugin[^1] |
| Nylas | Agent inbox and access to user accounts | 5 connected accounts, 3 Agent Accounts, 3,000 emails a month[^5] | Essentials 15 $ a month[^5] | Hosted MCP with API key, US and EU endpoints[^6] |
| Cyberpigeon | Agent inbox | Beta: 3 mailboxes, 1,000 outbound recipients a month[^7] | Launch 49 $ a month, 100 mailboxes[^7] | Hosted MCP with OAuth or API key[^8] |
| Email for Agents | Agent inbox | 1 live inbox, 100 email units a month, 3 test inboxes[^9] | Paid plans not on sale yet[^9] | MCP server and REST API[^9] |
| Open Agent Email | Self-hosted agent inbox | Apache 2.0; you pay for the server and a sending relay[^11] | No plans | 96 MCP tools, REST, SMTP[^11] |
| Shipmail | Business email with agent mailboxes | Not checked | Solo 4 $ a month, 2 mailboxes[^12] | Hosted MCP with OAuth or API key[^13] |
| Postmark | Sending service with inbound | 100 emails a month for testing[^16] | Basic 15 $ a month; inbound processing only from Pro at 16.50 $[^16] | Not checked |
| Mailgun | Sending service with inbound | 100 emails a day, 1 inbound route[^17] | Basic 15 $ a month, 5 inbound routes[^17] | Not checked |
| Resend | Sending service with inbound | 3,000 emails a month, 100 a day, 3 inboxes[^14] | Pro 20 $ a month[^14] | Official remote MCP[^15] |
| EmailEngine | Self-hosted access to existing mailboxes | 14-day trial[^18] | 1,450 $ or 1,200 € a year[^18] | MCP endpoint in beta[^19] |
| Fluxmail | Access to existing mailboxes | 7-day trial[^20] | Cloud Pro 120 $ a year, 10 mailboxes[^20] | Hosted MCP with OAuth; self-hosted over stdio or HTTP[^20] |
| MCP Emails | Access to existing mailboxes | 1 inbox, 150 email actions a month[^22] | Personal 9 $ a month, 3 inboxes[^22] | Hosted MCP[^22] |
| Command Mail | Personal forwarding inbox | 1 mailbox, last 90 days, no sending[^23] | Pro €19 a month for the first 100 paying accounts, then €29[^23] | Hosted MCP with OAuth 2.1, CLI[^23] |

Prices are what each vendor published on 2026-10-19. We did not buy any of these plans or measure usage.

## Agent inbox providers in detail

### AgentMail

AgentMail focuses on inboxes for agents. Its documentation lists 39 MCP tools for inboxes, threads, messages, drafts, attachments, and allow and block lists, plus two organization-selection tools for OAuth sessions[^1]. It also has AgentID tools that let the agent create accounts at supported services. Claude and ChatGPT sign in with OAuth; Cursor and Windsurf use an API key.

You can scope an API key to an organization, a pod of inboxes or a single inbox[^3]. A key without a permissions object has full access inside that scope; once you add one, only the permissions set to true apply, so you can issue a key that reads but lacks message_send. The free plan allows 100 emails a day and Developer 1,000; AgentMail lists an EU cloud only on Enterprise[^2].

Agent Armor scans inbound mail for attempts to manipulate agents; AgentMail calls the result advisory, not a guarantee[^26]. Some messages get no verdict (unavailable), such as bounces, very large messages or scans that fail, and AgentMail advises treating them like a review verdict. It lives in AgentMail Labs and runs in US production only, not yet in the EU. In Hold mode, AgentMail sends message.received for mail with a review verdict only after someone releases it, while mail marked unavailable is delivered to the agent as usual. Through listing, search or IMAP the agent can still reach held mail. The documentation explains how to find every held message.

### Nylas Agent Accounts

At Nylas, an Agent Account is a real mailbox on a domain you have registered, or on a nylas.email trial domain[^4]. It comes with six system folders, a calendar and its own grant_id, which works with the same endpoints as a connected user account, so messages, drafts, attachments and webhooks follow paths you may already know. Inbound block rules can reject mail at SMTP time, and outbound mail is checked against the sender domain, outbound rules and send quotas.

The Nylas MCP server offers 38 tools across email, calendar, contacts and Notetaker[^6]. Before send_message or send_draft, the agent has to call a confirmation tool that generates a hash. Nylas itself says you are responsible for requiring explicit user confirmation and for further safeguards against prompt injection.

### Cyberpigeon

Cyberpigeon describes itself as being in developer beta, free during the beta and capped at 50 outbound recipients a day[^7]. Paid plans bill in euros or dollars, and paying does not skip the automatic abuse review on sending. send_email and reply_to_email are annotated as irreversible so MCP clients can ask first, and received mail is labelled as untrusted in tool results[^8]. The beta sending policy bans cold outreach, prospecting, bulk marketing and inbox warmup, through MCP as through the API. Cyberpigeon also notes it is not a listed partner or directory app in Claude, Codex or ChatGPT.

### Email for Agents

Email for Agents ties an approval to one exact draft, using a hash of the content and the recipients[^10]. If the content changes after approval, the send fails, and unanswered requests expire after seven days. Recipient rules, a daily cap and a project-wide pause sit alongside. The vendor also says direct sending stays the default for a send-capable credential until a policy asks for review. Its Builder and Team plans cannot be bought yet, and custom domains require one of them[^9].

### Open Agent Email and Shipmail

Open Agent Email is self-hosted under Apache 2.0, with SQLite or PostgreSQL and a sending relay you choose, such as Amazon SES[^11]. The README describes an optional approval gate with approve and reject links, an expiry and a history, and per-inbox keys that are read-only, read and send, or review-only. According to the README, the server screens incoming mail for tricks aimed at AI readers and hidden text. Receiving mail from the internet needs a public server, an MX record and port 25 open. The project says it is single-user today, with customer accounts planned.

Shipmail sells business email on your own domains from 4 $ a month for two mailboxes[^12]. It documents mailboxes for agents on your domain and a hosted MCP server that accepts OAuth or a scoped API key[^13]. In Claude, a mailbox password can approve the connection for that one mailbox only.

## Sending services with inbound: Resend, Postmark and Mailgun

Sending services give your application addresses and accept incoming mail, but most of an agent's day-to-day mailbox work is left for you to build. At Resend, received and sent emails draw from the same quota; every plan includes three inboxes, and on paid plans with pay-as-you-go each extra one is 1 $ a month[^14]. Resend's official remote MCP takes OAuth or an API key, and its README covers sending, receiving, contacts and domains[^15].

Postmark lists inbound email processing from its Pro plan upward, while Mailgun includes one inbound route even on its free plan[^16][^17]. For an agent that follows threads, drafts replies and waits for approvals, these services are the plumbing underneath.

## Direct access to existing mailboxes: EmailEngine, Fluxmail and MCP Emails

These services let an agent work straight in the original Gmail, Outlook or IMAP account. EmailEngine provides a REST API with webhooks and only lists the MCP tools a given token may actually call[^18][^19].

Fluxmail runs as a cloud service or self-hosted. Each connection gets a permission profile from read-only through read-write to full; keys created without options are read-only, and an optional mailbox allowlist limits which accounts an agent can reach[^21]. According to its pricing page, Fluxmail Cloud keeps no copy of your mail, and scheduled sends are not available there yet[^20].

MCP Emails connects Gmail, Outlook and Microsoft 365, iCloud, Fastmail and IMAP, and fetches mail live on each call without storing it; only scheduled messages are held until they go out[^22]. Optional per-inbox approval holds sends, replies, forwards and scheduled mail for review in the dashboard. You can also self-host the server under AGPL-3.0 for IMAP and SMTP mailboxes; according to the vendor, Gmail and Outlook OAuth sign-in and the dashboard stay with the hosted plan.

## Approval before sending: what each vendor documents

Most of these services now offer some check before mail leaves, but it sits in different places:

- **In the service, tied to one version:** Email for Agents binds approval to the content and recipients[^10]. With the mail:send-approved permission, Command Mail sends exactly the draft revision a person approved, once, and any edit clears the approval[^23].
- **In the service, as a hold queue:** MCP Emails and Open Agent Email hold outgoing mail for a decision when you turn that on[^22][^11].
- **In the tool:** Nylas requires a confirmation call before sending and leaves the actual user consent to your application[^6].
- **Through permissions and the client:** AgentMail and Cyberpigeon let you withhold send permission and rely on your AI client to ask; AgentMail notes that ChatGPT confirms write actions[^1][^3][^8].

These are vendor statements. Command Mail is the only one whose enforcement we checked in code.

## When AgentMail, Nylas or another service is the better choice

Another service is the stronger pick in these cases:

- **The agent needs its own identity.** For a support bot or signing up to services, AgentMail, Nylas Agent Accounts and Cyberpigeon give the agent addresses that belong to it alone[^1][^4][^8]. Nylas lists sales outreach as a use case; Cyberpigeon bans cold outreach during its beta.
- **Many inboxes created in code.** AgentMail lists 150 inboxes on its Startup plan, Nylas describes one account per customer on that customer's domain, and Cyberpigeon offers 1,000 mailboxes on Scale[^2][^4][^7].
- **Email and calendar inside your product.** Nylas connects your users' mail and calendar accounts and agent accounts through one API[^5].
- **Working in the original mailbox.** Fluxmail, MCP Emails and EmailEngine can change folders, labels and drafts directly in the source account, as far as their permissions allow[^21][^22][^19].
- **Running it yourself.** Open Agent Email, EmailEngine and Fluxmail run on your own infrastructure, and so can MCP Emails, though without hosted Gmail and Outlook OAuth or the dashboard[^11][^18][^20][^22].
- **Free sending.** AgentMail, Resend and Cyberpigeon send without payment within the limits above[^2][^14][^7].

## When Command Mail fits

Command Mail fits when you have several addresses across Gmail, Outlook and your own domains, want to read them in one inbox, and want your agent to work there under fixed rules[^23]. Each address gets its own private inbound address for forwarding. You verify a domain with a TXT record and import older mail from MBOX or EML files with the CLI; with the mailboxes permission, your agent can do these steps for you[^24].

Permissions are separate: mail:read to read and sort, mail:draft for drafts only, mail:send-approved for approved drafts, and mail:send for sending on its own[^23]. The agent sends independently only from mailboxes on the auto autonomy level, with a unique send key per message, a daily limit of 50 emails by default and at most 20 recipients per message. Command Mail treats message content as untrusted data and flags suspected prompt injection, and the agent does not write on its own to automated senders, mailing lists or no-reply addresses. That detection relies on headers and patterns and can get an individual case wrong.

On the free plan the agent reads, searches, sorts and drafts, and you get the morning brief[^23]. That is enough to try an agent in your inbox before you let it send.

## Who Command Mail is not for

- **Anyone giving many agents their own addresses:** Command Mail is built around one person's addresses, and its documentation does not describe creating agent inboxes in bulk through an API[^24].
- **Anyone who needs changes in the original account:** Forwarding and import are not sync, so sorting in Command Mail leaves your Gmail or Outlook account as it was[^24].
- **Anyone who wants to send for free:** Free does not send; sending starts with Pro[^23].
- **Anyone who wants to self-host:** Command Mail is a hosted service run by FYN Labs LLC in the US. The app and database run on Cloudflare, and the privacy page says attachments are stored in Cloudflare's EU jurisdiction; that is no promise that all data stays in the EU[^25].

## Getting started and switching

For an agent inbox, you create an account with the provider, add an inbox on its domain or set up DNS records for your own, then connect its MCP server to your client. Each vendor documents the exact records; for your own domain you need access to its DNS settings[^4][^11][^13].

For Command Mail, you sign up, connect your address in the browser or with the CLI, and set up forwarding to its private inbound address at your current provider[^24]. Then connect your agent, for example in Claude Code and the Codex CLI[^23]:

```bash
claude mcp add --transport http commandmail https://commandmail.app/mcp
codex mcp add commandmail --url https://commandmail.app/mcp
codex mcp login commandmail
```

On the first sign-in, grant reading and drafting only. Start every session with capabilities, which returns the owner, permissions, mailboxes with their autonomy level and limits[^23]. The ChatGPT route and its plan limits are covered in [Connect Gmail to ChatGPT](https://commandmail.app/en/guides/connect-gmail-to-chatgpt).

You can combine approaches. An agent inbox for sign-ups and testing works alongside a forwarding inbox for your own addresses, with permissions kept separate per service.

For MCP servers that reach Gmail, Outlook and IMAP, see [Best email MCP servers](https://commandmail.app/en/compare/best-email-mcp-servers). To bring several of your own accounts to one agent, see [Use multiple email accounts with an AI agent](https://commandmail.app/en/guides/multiple-email-accounts-ai-agent).

You can [start Command Mail for free](https://commandmail.app/login?signup=1) and connect your agent afterwards.

## Frequently asked questions

### What is the difference between AgentMail and Command Mail?

AgentMail creates new inboxes through an API that belong to the agent, for example a support bot or an agent that signs up for services. Command Mail collects the addresses you already have into one inbox by forwarding, and your agent works there with separate permissions. Some teams need both.

### Is Nylas an option if I don't write code?

Not really. Nylas is a developer platform: even its MCP server needs an API key and a connected account. Services such as Fluxmail Cloud, MCP Emails and Command Mail are built for people who want to connect a mailbox and start.

### Do I need my own domain for an agent inbox?

Not to get started. Cyberpigeon and Email for Agents hand out free addresses on their own domains, Nylas offers a trial domain, and AgentMail includes custom domains from its Developer plan. For mail to customers, a verified domain of your own is the usual choice; Email for Agents cannot sell one yet.

### Which services hold an email until I approve it?

According to their vendors, Email for Agents, MCP Emails and Open Agent Email, each as a setting you turn on. Command Mail gives sending an approved draft revision and sending on its own separate permissions. AgentMail, Cyberpigeon and Nylas rely on key permissions and the confirmation prompt in your AI client.

### Does Command Mail work inside my Gmail account?

No. Command Mail receives forwarded copies, so sorting or archiving there leaves your Gmail account unchanged. If the agent should work in the original mailbox, services with direct access such as Fluxmail, MCP Emails or EmailEngine fit better.

## Sources

1. [AgentMail Docs: MCP (setup, sign-in, tools)](https://docs.agentmail.to/integrations/mcp), accessed 2026-10-19
2. [AgentMail: Pricing](https://www.agentmail.to/pricing), accessed 2026-10-19
3. [AgentMail Docs: Permissions](https://docs.agentmail.to/permissions), accessed 2026-10-19
4. [Nylas Docs: Nylas Agent Accounts](https://developer.nylas.com/docs/v3/agent-accounts/), accessed 2026-10-19
5. [Nylas: Pricing](https://www.nylas.com/pricing/), accessed 2026-10-19
6. [Nylas Docs: Nylas MCP server](https://developer.nylas.com/docs/dev-guide/mcp/), accessed 2026-10-19
7. [Cyberpigeon: Pricing & Plans for Agent Email](https://cyberpigeon.ai/pricing), accessed 2026-10-19
8. [Cyberpigeon: MCP server guide](https://cyberpigeon.ai/guides/mcp-server), accessed 2026-10-19
9. [Email for Agents: Pricing](https://emailforagents.ai/pricing), accessed 2026-10-19
10. [Email for Agents: Approvals & Permissions](https://emailforagents.ai/product/controls), accessed 2026-10-19
11. [GitHub Anil-matcha/open-agent-email (README)](https://github.com/Anil-matcha/open-agent-email), accessed 2026-10-19
12. [Shipmail: Pricing](https://shipmail.to/pricing), accessed 2026-10-19
13. [Shipmail Docs: Connect an agent with MCP](https://shipmail.to/docs/mcp), accessed 2026-10-19
14. [Resend: Pricing](https://resend.com/pricing), accessed 2026-10-19
15. [Resend MCP README: remote server, OAuth, sending and receiving](https://raw.githubusercontent.com/resend/resend-mcp/main/README.md), accessed 2026-10-19
16. [Postmark: Pricing](https://postmarkapp.com/pricing), accessed 2026-10-19
17. [Mailgun: Pricing](https://www.mailgun.com/pricing/), accessed 2026-10-19
18. [EmailEngine: Self-Hosted Email API](https://emailengine.app/), accessed 2026-10-19
19. [EmailEngine Docs: MCP](https://learn.emailengine.app/docs/mcp), accessed 2026-10-19
20. [Fluxmail: Pricing](https://fluxmail.ai/pricing), accessed 2026-10-19
21. [Fluxmail Docs: Permissions](https://fluxmail.ai/docs/permissions), accessed 2026-10-19
22. [MCP Emails: Email MCP server for Gmail, Outlook and IMAP](https://mcpemails.com/), accessed 2026-10-19
23. [Command Mail: llms.txt with plans, MCP address and permissions](https://commandmail.app/llms.txt), accessed 2026-10-19
24. [Command Mail: Documentation](https://commandmail.app/en/docs), accessed 2026-10-19
25. [Command Mail: Privacy, operator and hosting](https://commandmail.app/privacy), accessed 2026-10-19
26. [AgentMail Docs: Agent Armor (Labs)](https://docs.agentmail.to/agent-armor), accessed 2026-10-19

[^1]: [AgentMail Docs: MCP (setup, sign-in, tools)](https://docs.agentmail.to/integrations/mcp), accessed 2026-10-19
[^2]: [AgentMail: Pricing](https://www.agentmail.to/pricing), accessed 2026-10-19
[^3]: [AgentMail Docs: Permissions](https://docs.agentmail.to/permissions), accessed 2026-10-19
[^4]: [Nylas Docs: Nylas Agent Accounts](https://developer.nylas.com/docs/v3/agent-accounts/), accessed 2026-10-19
[^5]: [Nylas: Pricing](https://www.nylas.com/pricing/), accessed 2026-10-19
[^6]: [Nylas Docs: Nylas MCP server](https://developer.nylas.com/docs/dev-guide/mcp/), accessed 2026-10-19
[^7]: [Cyberpigeon: Pricing & Plans for Agent Email](https://cyberpigeon.ai/pricing), accessed 2026-10-19
[^8]: [Cyberpigeon: MCP server guide](https://cyberpigeon.ai/guides/mcp-server), accessed 2026-10-19
[^9]: [Email for Agents: Pricing](https://emailforagents.ai/pricing), accessed 2026-10-19
[^10]: [Email for Agents: Approvals & Permissions](https://emailforagents.ai/product/controls), accessed 2026-10-19
[^11]: [GitHub Anil-matcha/open-agent-email (README)](https://github.com/Anil-matcha/open-agent-email), accessed 2026-10-19
[^12]: [Shipmail: Pricing](https://shipmail.to/pricing), accessed 2026-10-19
[^13]: [Shipmail Docs: Connect an agent with MCP](https://shipmail.to/docs/mcp), accessed 2026-10-19
[^14]: [Resend: Pricing](https://resend.com/pricing), accessed 2026-10-19
[^15]: [Resend MCP README: remote server, OAuth, sending and receiving](https://raw.githubusercontent.com/resend/resend-mcp/main/README.md), accessed 2026-10-19
[^16]: [Postmark: Pricing](https://postmarkapp.com/pricing), accessed 2026-10-19
[^17]: [Mailgun: Pricing](https://www.mailgun.com/pricing/), accessed 2026-10-19
[^18]: [EmailEngine: Self-Hosted Email API](https://emailengine.app/), accessed 2026-10-19
[^19]: [EmailEngine Docs: MCP](https://learn.emailengine.app/docs/mcp), accessed 2026-10-19
[^20]: [Fluxmail: Pricing](https://fluxmail.ai/pricing), accessed 2026-10-19
[^21]: [Fluxmail Docs: Permissions](https://fluxmail.ai/docs/permissions), accessed 2026-10-19
[^22]: [MCP Emails: Email MCP server for Gmail, Outlook and IMAP](https://mcpemails.com/), accessed 2026-10-19
[^23]: [Command Mail: llms.txt with plans, MCP address and permissions](https://commandmail.app/llms.txt), accessed 2026-10-19
[^24]: [Command Mail: Documentation](https://commandmail.app/en/docs), accessed 2026-10-19
[^25]: [Command Mail: Privacy, operator and hosting](https://commandmail.app/privacy), accessed 2026-10-19
[^26]: [AgentMail Docs: Agent Armor (Labs)](https://docs.agentmail.to/agent-armor), accessed 2026-10-19

---

Command Mail: one inbox for you and your AI agent. Start free: https://commandmail.app/login?signup=1 · Connect your agent: https://commandmail.app/en/agents · MCP: https://commandmail.app/mcp