Maily

All your mailboxes, every assistant, one connection.

Maily is a free desktop app with public source code that bridges your mailboxes and your AI assistants. Your mail stays with your provider (Gmail, Google Workspace, or an IMAP host such as Orange). Maily connects to all of those accounts once, with your own Google OAuth client, and ships a local MCP server: every assistant on that computer (Claude Desktop, Claude Code, any MCP client) gets one access to all your accounts, instead of one connector per app, tied to one account. It is also a clean mail app for reading them yourself. No Maily server, no Maily account.

Website · Download for macOS, Windows and Linux · Changelog · Security · Contributing

Quick start. Download the app for macOS (.dmg), Windows (.zip) or Linux (.tar.gz) from the download page, install it with one line (curl -fsSL https://github.com/ThanaelFontaine/Maily/releases/latest/download/install.sh | sh on macOS and Linux, irm https://github.com/ThanaelFontaine/Maily/releases/latest/download/install.ps1 | iex in Windows PowerShell; see Install), or run it from source:

git clone https://github.com/ThanaelFontaine/Maily
cd Maily
uv sync
uv run maily

Then connect your accounts and, if you like, add Maily to Claude.

---

Table of contents

1. Why Maily
2. Features
3. Screenshots
4. How it works
5. Install
6. Connect your accounts
7. Use Maily with Claude (MCP)
8. A tour of the window
9. Where your data lives
10. Security and privacy
11. Beyond MCP: SQL views and the local API
12. Configuration reference
13. Troubleshooting
14. FAQ
15. Contributing
16. License

---

Why Maily

More and more people ask an AI assistant to sort, summarize and answer their mail. Hosted connectors make it possible, one app at a time, and come with trade-offs:

• Tied to the account you connected. A hosted connector ties an assistant to the account you connected: Claude's Gmail connector, for example, reaches "the Google account you've connected" (source). With several Gmail addresses, an IMAP provider and more than one assistant, you set up a connector in each app, and none of them sees the whole picture.
• Another cloud reaches your mailbox. With a hosted connector, the provider's servers fetch your mail for the assistant. Anthropic states that data retrieved through its connectors is stored on its servers (source). Check which Google permissions a hosted Gmail connection asks for on its consent screen: a scope such as gmail.modify lets it read, compose and send email (Google's description).
• Limited actions. Connectors only do what their provider has built. Anthropic notes, for instance, that with its Gmail connector attachment content is not directly accessible (metadata only) (source).

Maily's answer is one bridge on your computer. Maily connects to every mailbox you add, with your own Google OAuth client and your IMAP passwords, and keeps a synced copy (a local database and search index) so that it is fast and searchable; your providers still hold your mail. Its MCP server runs on the same computer, started by your assistant as a local process over the stdio transport (the client launches the server as a subprocess and talks to it over standard input and output, see the MCP specification). No network port is opened, and no Maily server sits between you and your providers. Every assistant you add Maily to sees every account at once, can read attachments, and can search all your mail instantly, even offline.

One thing stays true with any assistant: what it reads through Maily becomes part of your conversation with it, so it is processed by whoever runs the model behind that assistant. Only connect assistants you trust (see Security and privacy).

以上为 README 的开头部分。其余内容请阅读原文。 查看完整 README ↗