email-mcp and mcp-headless-gmail
One server provides full IMAP+SMTP support, while the other specifically offers Gmail integration without local credential setup, suggesting they are **competitors** targeting different email backend preferences within the Model Context Protocol.
About email-mcp
codefuturist/email-mcp
Email MCP server with full IMAP + SMTP support — read, search, send, manage, and organize email from any AI assistant via the Model Context Protocol
Exposes 47 tools across 7 prompts and 6 resources, including real-time IMAP IDLE watchers with AI-powered triage, email scheduling, calendar extraction, and provider-aware label management. Built with layered service architecture decoupled from MCP wiring for testability, uses stdio transport with XDG-compliant TOML config, and auto-detects settings for 8+ providers (Gmail, Outlook, Yahoo, iCloud, Fastmail, ProtonMail, Zoho, GMX). Supports multi-account workflows with OAuth2 (experimental), token-bucket rate limiting, TLS/STARTTLS encryption, and 5 MB attachment caps; installable via npm/Docker or integrated directly into Claude Desktop, VS Code, Cursor, Windsurf, and Zed.
About mcp-headless-gmail
baryhuang/mcp-headless-gmail
A MCP (Model Context Protocol) server that provides get, send Gmails without local credential or token setup.
Implements a Python-based MCP server using the google-api-python-client library with credential decoupling—OAuth tokens are passed per-request rather than stored locally, enabling truly headless operation in remote/containerized environments. Supports chunked email retrieval (1k character increments with offset-based pagination), automatic token refresh, and both plaintext and HTML email composition, with deployment options via Docker (multi-platform) or npm.
Related comparisons
Scores updated daily from GitHub, PyPI, and npm data. How scores work