MCP servers that send email
Let your AI compose and send email via Gmail, Resend, SMTP, and more.
3 servers · Last updated June 17, 2026
TL;DR: These servers let an agent send (and sometimes read/search) email. The split is transactional APIs (Resend, providers) for app-style sending vs mailbox integrations (Gmail, SMTP) for acting on your real inbox. Sending email is a high-trust action — review the auth model before wiring one up.
Bottom line: if you only try one, Gmail MCP Server (GongRzhe) is the most popular, verified option for this (1,100★). 2 more compared below.
Compare 3 servers
| Server | Transport | Auth | Verified | Stars | Tools for this |
|---|---|---|---|---|---|
| Gmail MCP Server (GongRzhe) | Local (stdio) | OAuth | 1,100 | send_email, draft_email, read_email +6 | |
| Resend Email MCP Server | Local (stdio) | API key | 530 | send_email, emails (list / get / update / cancel), received emails | |
| Email MCP Server (IMAP/SMTP) | Local (stdio) | API key | 254 | get_emails_content, send_email, save_to_mailbox |
The servers
Gmail MCP with auto OAuth: send, search, label and manage email
Official Resend MCP to compose and send transactional email from your assistant
Provider-agnostic email MCP over IMAP/SMTP — read, search and send from any mailbox
FAQ
Is it safe to let AI send email?
Treat it as a privileged action. Use a dedicated sending domain/address, scope OAuth narrowly, and consider a human-in-the-loop approval for anything outbound to real people.
Transactional API vs Gmail MCP — which do I want?
Use a transactional API (e.g. Resend) for app/system emails; use a Gmail/SMTP MCP when the agent needs to act on your actual mailbox.