MCPs for sending and reading email
Email MCP servers expose send and read operations for transactional providers (Resend, SendGrid) and inbox providers (Gmail, Outlook). Agents can draft, send, and read email — enabling inbox triage, newsletter automation, and customer notifications in natural language.
Email MCPs let agents send transactional emails (Resend, SendGrid, Mailgun), read inboxes (Gmail, IMAP), and manage newsletters. They're central to customer comms, onboarding, and inbox-driven agent workflows.
Yes, via OAuth (Gmail, Outlook) or a transactional provider key (Resend). For personal email, OAuth is standard; for marketing, use Resend/SendGrid.
Yes — all transactional MCPs accept HTML bodies, attachments, inline images, and templated variables.
Use a reputable provider (Resend, Postmark) and configure SPF/DKIM/DMARC. The MCP doesn't affect deliverability — your sending domain does.
Yes — there are IMAP-based MCPs for any standard inbox. Gmail also has a dedicated OAuth-based MCP with richer features.
Browse the full marketplace or explore all tags to find the right MCPs for your stack.