Discover the Best AI Tools

MCP server connecting AI clients to Lettio mailboxes over JMAP to read, search, send, reply and organize messages across one or more accounts. The local option requires Node.js 18+ and mailbox app passwords; hosted OAuth access is also documented. Email handling remains subject to the connected AI client’s data practices.

MCP adapter for the PostStack email API, with tools for transactional sending, inbound threads, contacts, templates and deliverability checks. Runs locally over stdio or through the hosted HTTP endpoint. Requires a PostStack API key and hosted service access; previews and checks do not guarantee delivery.

Local single-user Outlook MCP reading message bodies and attachments through Microsoft Graph, and attaching local files to drafts or sends. Requires Microsoft app authorization; sending is opt-in per call and attachments must each be under 3 MB. Refresh tokens persist on disk, so local operation still involves cloud access and stored credentials.

Agent-operated outreach infrastructure for domains, mailboxes, sequences, replies and delivery monitoring through MCP, HTTP and CLI. A free fault-injecting sandbox simulates vendors; real operation requires paid provisioning and send activation. The customer agent writes content, and inbox placement or deliverability is not guaranteed.

Self-hosted read-only mail MCP backed by an IMAP-synced local notmuch index and authenticated HTTP. Searches and reads indexed mail without sending, moving or deleting it. Requires mailbox access and deployment; a shared server secret is not per-user mailbox isolation, and returned content may reach the client model.

MCP server and CLI for VaEmail transactional mail, newsletters, contacts, sending-domain setup and delivery diagnostics. Requires API access for account operations. Queuing a message is distinct from delivery; feature support and provider event gaps must be checked rather than treating a send response as proof of receipt.

Rust MCP for multi-account email over IMAP, SMTP, EWS and Microsoft Graph, with OAuth2, searches and bulk operations. Requires provider credentials and configuration. Version 0.4.13 validates all configured sender addresses at startup and rejects dotless domains, so internal-relay addresses may block startup; no universal delivery guarantee is implied.

MCP for listing, searching, reading and sending Zoho Mail messages through its API. Requires Node.js 18+, a Zoho account, OAuth client credentials, a refresh token and account configuration. Mail reads need message and folder IDs; sending uses the configured sender and authorized scopes.

Unofficial local MCP for reading, searching, sending and organizing Hey.com mail through reverse-engineered web endpoints. Uses Bun/TypeScript plus a Python login helper. Session cookies are stored on disk, including for Docker operation; upstream website changes may break access.

Self-hosted email and task handoff infrastructure with threads, approval records and webhooks over MCP/REST. Existing agent harnesses execute the work; approval records do not execute actions and automatic wakeup needs integration. Requires deployed mail infrastructure and agent identities; self-hosting does not by itself keep model inputs local.

SMTP sending, replies and forwarding from one configured address. Sending is disabled by default and requires credentials, explicit enablement and a recipient allowlist. Supports message-bound confirmation through MCP elicitation or a two-call token fallback; the token fallback is not equivalent to human approval. Mail reading is a separate server.

Local stdio MCP for EngageLab agent mailboxes, sending, receiving, replies and conversation threads, with a sandbox option. Requires an EngageLab secret key and Node.js 20+. This package provides no hosted HTTP or OAuth MCP endpoint; live mode sends real email.

Microsoft Graph MCP for Outlook mailbox cleanup: bulk moves, folder restructuring, inbox rules and drafts. Requires Microsoft account authorization and an app ID. No send tool or permanent deletion; read-only mode is optional, while supported bulk operations preview by default.

Unofficial MCP for Open-Xchange and standards-based mail, calendars and contacts, including filters and free/busy. Requires configured accounts and credentials; reads default on and writes off. OX HTTP search is limited to subjects and addresses of recent mail; full-body search requires IMAP. Free/busy does not expose event details.

Email triage MCP with an in-memory heuristic sandbox for urgency, commitments and reviewable drafts, plus API-key connected reading and search. Connected mode does not send or mutate real mail. Sandbox heuristics are not the production accuracy engine; documented risk stops should not be read as guaranteed fraud or prompt-injection detection.

MCP access to QMailing mailboxes, email sending and reading, custom domains and webhooks through OAuth or scoped API tokens. The public API requires PLUS or higher; local package use needs Node.js 18.17+. Granted scopes define real account access, and sending remains an external action.

MCP adapter for Inxmail Commerce transactional email events, sending, bounces, blocklists and delivery tracking. Requires an existing instance and API key ID/secret. It includes live event triggers and raw-mail sending, so it is not merely a read-only reporting tool.

Unofficial Proton Mail MCP for sending via SMTP and reading, searching and organizing mail via local Proton Mail Bridge. Requires Node.js 24+, appropriate Proton credentials and Bridge for IMAP. Read-only mode and bulk dry-runs are available; default operation is not universally read-only, and service eligibility still applies.

Official Shipmail MCP for custom-domain mailboxes, messages, threads, webhooks and rules. Requires a service API key and a compatible client; local use needs Node.js 20+. The documented MCP protocol requirement excludes older initialization clients. Safe retry deduplication needs the caller to reuse an idempotency key; defaults generate a fresh key per call.

Community MCP for Resend email, domains, contacts, broadcasts, templates and delivery diagnostics. Requires an API key and appropriate service access and quotas. Read-only mode is opt-in; local attachment reads are disabled unless an allowed directory is configured. Not an official Resend server.

Read-first MCP over an existing local notmuch mail database for search, threads, attachments and optional drafts. Drafts, tags and exports require explicit opt-in; there is no sending capability in any mode. Needs the notmuch CLI and separate attachment converters as appropriate; drafts must be reviewed and sent through another mail client.

MCP access to hosted email verification, including catch-all and security-gateway-protected addresses, with result details and credit balance. Requires service authentication via OAuth or an API key and verification credits. Results are provider assessments, not independently validated accuracy guarantees or proof that a future message will reach the inbox.

Gmail MCP for search, labeling, mailbox triage and snoozing via dated labels and a sweep. Requires Gmail OAuth and running the sweep for resurfacing. Deliberately has no compose, reply or forwarding tools; it can still modify mailbox state. Local operation does not prevent retrieved messages reaching the connected model.

Microsoft Graph MCP for Outlook mail and OneDrive operations, starting in read-only mode with browser sign-in. Writes require higher modes; sending and deletion also need explicit flags. Human prompts depend on client elicitation support and otherwise fall back to those flags. Attachment tools return metadata, not attachment bytes.