Filtered, read-only IMAP and Gmail archived to disk as .eml + markdown, served over MCP.
If you already use Mail, the mail mcp server is the piece that lets your assistant work with it directly. Filtered, read-only IMAP and Gmail archived to disk as .eml + markdown, served over MCP.
The toolset is worth reading before you wire it up, because it tells you what the integration is really for:
Gmail — enforced by Google.** The only scope requested is gmail.readonlyIMAP — enforced by mail-muncher.** IMAP has no read-only credential to askname — agent-inboxRead — only by construction.** Nothing in mail-muncher writes to a mailboxCredential — an app password from your provider's own settings pageExpiry — nonelist_rules — What am I collecting, and which senders am I subscribed to right now? Each from_domains_file is re-read on every calllist_messages — What has arrived? Filter by rule, account, thread or date; optionally grouped into conversationssearch_messages — Where is the message that mentions X? Substring search over subject, sender, recipients, labels, attachment names and bodyread_message — One message in full — metadata, body, attachment names and sizes — and optionally its whole thread in ordersync — Fetch new mail once, returning the same manifest run --json writesgmail-archive — It was almost exactly this — Gmail query to Maildir, incremental — and would be the obvious answer if it were still maintained. It has not been sinceBecause this one is hosted, setup is mostly authentication — you point your client at the endpoint and approve access. Nothing runs on your machine, so there is no runtime to keep patched.
This sits in the team communication group, where several servers overlap in what they claim to do but differ sharply once you actually set them up. Mail's toolset — Gmail, IMAP, name and 11 more — is a fair guide to whether it matches your workflow. It is maintained by craigjmidwinter; worth a glance at recent repository activity before you build anything load-bearing on it.
This entry was verified against Mail's own documentation before publication; SyncDev keeps the directory reviewed rather than auto-generated.
| Tool | What it does |
|---|---|
| Gmail | enforced by Google.** The only scope requested is gmail.readonly. |
| IMAP | enforced by mail-muncher.** IMAP has no read-only credential to ask |
| name | agent-inbox |
| Read | only by construction.** Nothing in mail-muncher writes to a mailbox. |
| Credential | an app password from your provider's own settings page |
| Expiry | none |
| list_rules | What am I collecting, and which senders am I subscribed to *right now*? Each from_domains_file is re-read on every call. |
| list_messages | What has arrived? Filter by rule, account, thread or date; optionally grouped into conversations. |
| search_messages | Where is the message that mentions X? Substring search over subject, sender, recipients, labels, attachment names and body. |
| read_message | One message in full — metadata, body, attachment names and sizes — and optionally its whole thread in order. |
| sync | Fetch new mail once, returning the same manifest run --json writes. |
| gmail-archive | It was almost exactly this — Gmail query to Maildir, incremental — and would be the obvious answer if it were still maintained. It has not been since 2018. |
| gmail-exporter | You want a one-off, label-based, spreadsheet-shaped export rather than incremental sync. |
| Homebrew | That taps [craigjmidwinter/homebrew-tap](https://github.com/craigjmidwinter/homebrew-tap) and installs a prebuilt binary. brew upgrade mail-muncher tracks new releases. |
{
"mcpServers": {
"mail-muncher": {
"command": "/usr/local/bin/mail-muncher",
"args": ["mcp", "--config", "/Users/you/.config/mail-muncher/config.yml"]
}
}
}Configuration as documented by the project. Restart the client after saving.
Your assistant inside the workspace — read channels, search history, post messages and tame the noise.
Inbox intelligence — search, read, draft and send Gmail through your assistant with OAuth auto-setup.
Read and write Jira, Confluence, Bitbucket, JSM and Compass from your AI client — with your own permissions.
Read and send Telegram messages through your assistant — chats, channels and history via the client API.
Enables Discord bot integration with Model Context Protocol (MCP) compatible applications like Claude Desktop.
Exposes REST APIs defined by OpenAPI specifications as Model Context Protocol (MCP) tools, facilitating seamless integration into MCP-based workflows.