MCPs for sending and reading email
TL;DR
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.
About Email
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.
Common use cases
- Auto-draft replies to customer support emails for human review
- Send invoice PDFs automatically on Stripe payment
- Triage inbox: summarize, categorize, and flag action items
- Generate and send personalized onboarding emails
- Read a newsletter inbox and extract action items
Related recipes
Related tags
Frequently asked questions
Can an agent send email on my behalf?
Yes, via OAuth (Gmail, Outlook) or a transactional provider key (Resend). For personal email, OAuth is standard; for marketing, use Resend/SendGrid.
Do email MCPs support HTML?
Yes — all transactional MCPs accept HTML bodies, attachments, inline images, and templated variables.
What about deliverability?
Use a reputable provider (Resend, Postmark) and configure SPF/DKIM/DMARC. The MCP doesn't affect deliverability — your sending domain does.
Can I read IMAP inboxes?
Yes — there are IMAP-based MCPs for any standard inbox. Gmail also has a dedicated OAuth-based MCP with richer features.
Install Email MCPs
Browse the full directory or explore all tags to find the right MCPs for your stack.