The most complete multi-backend email MCP server. 24 tools across and — send via SMTP, AWS SES, or SendGrid while reading from any IMAP server. File attachments, OAuth with auto-refresh, single Rust binary with enterprise governance.
Email MCP Server — Gmail and Microsoft Graph for sending, reading, and managing email
Étoiles
1
Outils
—
Disponibilité
—
5 send backends
3 read backends
Architecture
Key Principles
Multi-backend — 5 send + 3 read backends, mix and match freely
IMAP-first reading — works with any email provider, no OAuth required
SMTP-first sending — universal, works with any relay
This server is built with rmcp 3.1.2 and requires Rust 1.94.1 or newer. The rmcp 3 rollout retains legacy MCP initialization compatibility and targets MCP protocol revisions 2025-11-25 and 2026-07-28.
MCP 2026-07-28 rollout (P0 security)
This server uses rmcp 3.1.2 and adk-mcp-sdk 0.2 with a minimum supported
Rust version of 1.94.1. It accepts stateless MCP 2026 requests with
per-request protocol, client identity, and capability metadata while retaining
the legacy MCP 2025-11-25 initialize flow for ordinary tools.
Discovery and routing: rmcp serves on-demand discovery and validates the
per-request protocol envelope; HTTP deployments can route with Mcp-Method
and Mcp-Name. The packaged binary currently uses stdio.
Caching:tools/list returns a public ttlMs of 60,000 for MCP 2026;
rmcp omits the cache fields for legacy clients.
Deprecated extensions: this server does not add new Roots, Sampling, or
dynamic client-registration dependencies.
Protected tools require MCP_REQUEST_STATE_KEY with at least 32 high-entropy
bytes. All replicas must share that key so sealed approval state can resume on
another instance. Approval state is bound to the client identity, tool, and
arguments and expires after two minutes. Missing identity, invalid state,
rejection, or legacy protocol use fails closed. Task records are process-local
for the current stdio runtime; use a durable task store before deploying the
server behind scale-to-zero HTTP infrastructure.
Security hardening
Send, mutation, and destructive mailbox tools require sealed MRTR approval.
OAuth configuration files that may contain client secrets are created with
owner-only 0600 permissions on Unix, flushed before use, and covered by a
permission regression test.
M
MCP Email
zavora-ai·1 étoiles·
Email MCP Server — Gmail and Microsoft Graph for sending, reading, and managing email
Pas encore de liste d'outils. Les serveurs distants en obtiennent une après le premier contrôle d'état.
FAQ
Questions
Comment installer MCP Email ?
Copiez sur cette page la configuration stdio pour Cursor, Claude Desktop, Claude Code ou VS Code. Elle utilise l'installation de l'éditeur, pas un proxy PlugMCP.
MCP Email nécessite-t-il une clé API ?
Aucune variable d'environnement requise n'est indiquée sur cette fiche.
Quel transport MCP Email utilise-t-il ?
MCP Email s'exécute en local via stdio.
Quand MCP Email a-t-il été vérifié pour la dernière fois ?
Dernière vérification : 2026-10-28. Email MCP Server — Gmail and Microsoft Graph for sending, reading, and managing email