Community Gmail server with auto-auth: search, read and send email via MCP.
606 MCP servers
MCP (Model Context Protocol) server for Claude integration with MailDev
Gmail integration with OAuth authentication, message search, batch operations, and Sheets export
Render markdown into email-safe HTML, lint drafts for deliverability problems, and preview emails.
Organize several Gmail accounts: labels, filters, archiving, drafts. Never sends or deletes mail.
Proton Mail Bridge Client — full-featured CLI and Claude Desktop MCP for Proton Mail via Proton Bridge. Read, search, send, draft, archive
An MCP server that gives AI agents a practical interface to Mailgun workflows for sending, diagnosing deliverability, and taking account
Official Postmark MCP server for sending emails via Claude and AI assistants
IMAP/SMTP MCP server to search, read, organize, send, reply & forward email for AI assistants
IMAP/SMTP email MCP server — 52 tools, stdio + HTTP, IMAP IDLE push, multi-account, AI triage.
Outlook integration with OAuth, message search, batch operations, and calendar management
MCP server for Apple Mail - read, search, send, and manage emails via Claude and other AI assistants
Read-focused, prompt-injection-hardened email MCP server for any IMAP provider
MCP server for Open-Xchange and standards-based mail platforms: email (IMAP/SMTP), mail filters (Sieve), calendar (CalDAV), contacts
Outlook & OneDrive MCP: personal & enterprise tools for mail, calendar, contacts, tasks, files
Extended Gmail MCP server via gogcli — auth + full Gmail support (threads, labels, drafts, attachments, forward, autoreply, bulk operations)
Outlook mail and OneDrive files via Microsoft Graph — read, search, send and organize.
SendGrid transactional email: preflight send, templates, and delivery diagnostics.
Sequenzy MCP server for AI-powered email marketing automation
stdio compatibility bridge for the hosted AgentMail MCP server
A real inbox for AI agents: send, receive and thread email, behind a prompt-injection firewall.
Email MCP servers on mcprush, filed under one heading so the shelf can be read in one pass.
Every server here names the publisher behind it and whether that publisher has been verified, the runtime it uses, how it authenticates, the tool surface it exposes and the price model it is sold under — and where a security scan has been run against it, what the scan found. The filters on the left narrow it further and the sort at the top decides what comes first.
Nearly every server in this catalogue is connected straight to its publisher: the listing gives the publisher’s own address or start command, and mcprush is not in the path, so nothing is routed, metered or billed here. The exception is a server delivered through the mcprush gateway — there one key covers everything installed against your account, the calls are metered where you can see them and the ceiling on what they may cost is yours to set, and installing it is a line of the mcprush CLI: npx mcprush@latest add, followed by the server’s id. The listing says which of the two it is before you install anything.