Your own mailbox, with full access for your AI agent, and the brake in the menu bar.
Install via Homebrew tap and authenticate your email account:
$ brew install --cask nspxmiguel/tap/mymailforai
$ mymailforai login voce@gmail.com
| Feature | MailForAI | MyMailForAI |
|---|---|---|
| Mailbox | Agent's mailbox (claude@nspx.dev) | Your own (Gmail, iCloud, etc.) |
| Scope | Send to allowlist only | Read all, write, move, archive |
| Interface | Windowed app with tabs & assistant | Menu bar item only |
| Brake | Allowlist + daily limit | Mode (automatic / ask / read-only) |
| Accounts | One | As many as you want, with logout |
An iCloud account is not an address — it is a mailbox that receives on several: the Apple ID, the @icloud.com ones, your own domain, the Hide My Email aliases. They all land in the same inbox, so connecting each as a separate account would show you the same mail three times. What actually differs is which address the message goes out as.
The address appears in the From: of something in your Sent folder. The server has already accepted sending as it — that is history, not a guess.
The address appears in the To: of mail that arrived. It proves the mailbox receives on it, which is not the same as being allowed to send from it.
$ mymailforai identities
$ mymailforai identities --send-as you@yourdomain.com
Replies pick the identity on their own: a message that arrived for you@yourdomain.com is answered from you@yourdomain.com, not from whichever address you happened to log in with.
A mailbox that receives on several addresses is also, unavoidably, one IMAP connection. Opening "the agent's mailbox" and opening your personal mail are the same connection, so without a limit the very first listing hands the agent fifteen hundred messages that were never meant for it. Every account is created scoped to the address you connected with.
$ mymailforai scope
$ mymailforai scope --all
The limit holds on both sides: the server-side search is filtered before results exist, and reading by UID checks again — a UID can come from anywhere, including a guess.
Read access is fully enabled, and all email sending or writing actions execute immediately.
Read access is fully enabled; write actions enter the queue and await approval in the menu bar.
Read access is fully enabled, but any write or modification attempt is rejected with a clear explanation.
Your app password goes directly into the macOS Keychain. Nothing ever leaves your machine, and there is no server of ours.
When launched with mymailforai mcp, the following Model Context Protocol tools are exposed over stdio: