通用的邮箱MCP服务器
166 servers · 166 listings
MCP server for Google Workspace (Gmail + Calendar) with send-as alias support, email templates, scheduled send, attachments, batch
MailAgent MCP server (stdio) for Cursor and AI agents — email verification inboxes
Gmail MCP server — scope-gated tools + attachment/download path jails + supply-chain hardening. Fork of GongRzhe/Gmail-MCP-Server via
MCP server for IMAP/SMTP email access with environment-based configuration
A powerful MCP server for sending emails via 126.com SMTP service. Perfect for AI assistants and automation workflows!
MCP server for Beehiiv newsletter platform. Provides tools to interact with Beehiiv API including subscriber management.
Email validation and SMTP verification for AI assistants. Validate emails directly inside Claude Desktop, Cursor, and Claude Code.
DMARC Examiner MCP plugin for Claude Desktop, Claude Code, and Cursor
MCP server for the Mamba Labs Domain Deliverability Checker actor on Apify. Audit a domain's email deliverability: SPF, DKIM, DMARC, MX
Drive-backed multi-account email MCP with reliable IMAP-to-mailboxes sync.
MCP server for email validator ai. Features validate email, check mx, detect disposable. From MEOK AI Labs.
MCP server for envoi.work — give any AI agent a real email address
MCP server for Fastmail using effect-jmap library
Give any AI agent a disposable email inbox in one tool call. MCP server for email verification, auth flows, and testing.
MCP Server for 1TempMail - Generate temporary emails, check inboxes, and read messages via AI assistants
stdio compatibility bridge for the hosted AgentMail MCP server
AIBus Google MCP — Gmail + Calendar + Drive (100 tools). One command to install, one command to auth.
Mock gmail MCP with a bundled sample dataset and real search/get tools (write actions are safe mocks).
Better MCP server for Email (IMAP/SMTP) with composite tools optimized for AI agents
MCP (Model Context Protocol) server for Brevo email marketing platform with comprehensive analytics
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.
A server that runs on its publisher’s infrastructure is reached through the mcprush gateway, so 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. Installing one is a line of the mcprush CLI — npx mcprush@latest add, followed by the server’s id — and a --client flag writes another client’s config instead of the default one. A server that runs on your own machine carries its publisher’s own instructions instead, and the listing says which of the two it is before you install anything.