Purpose: email-mcp is a unified MCP server that lets AI assistants access multiple email accounts through the MCP protocol, supporting Gmail (REST API), Outlook (Microsoft Graph), iCloud (IMAP), and generic IMAP/SMTP.
Main capabilities: provides 36 tools covering account management, reading and search, sending and drafts, organization, bulk operations, spam management, and forwarding rules. Supports OAuth2 browser login and automatic token refresh; by default returns compact search results (about 20KB instead of about 1.4MB), with optional retrieval of full message bodies; bulk deletes, moves, or marks hundreds of emails; attachments support paths or base64, with a total limit of 25MB (3MB per message for Outlook).
Usage: install globally via npm or run with npx, first run the interactive setup wizard to add accounts, then add the server to the MCP configuration (such as .mcp.json). Gmail and Outlook use built-in OAuth credentials, and you can also configure your own OAuth app; iCloud requires generating an app-specific password; generic IMAP requires providing server information.
Limitations and security: credentials are stored encrypted with AES-256-GCM in ~/.email-mcp/credentials.enc, and the key can be customized with EMAIL_MCP_KEY. Attachments can only be read from the directory specified by EMAIL_MCP_ATTACHMENTS_DIR; forwarding rules only accept addresses in EMAIL_MCP_FORWARD_ALLOWLIST. The forwarding rules and spam rules tools only support Gmail and Outlook; iCloud/IMAP have no server-side rule mechanism. The shared Gmail OAuth app was still under Google review as of October 1, 2026, so only test users can log in; other users need to create their own OAuth app. The tool is free, with no paid tier; the Google annual security assessment (CASA) fee is $675 per year, raised through donations.
