Email (IMAP/SMTP)
Let your agent read, search, send, and organize mail across multiple IMAP/SMTP accounts from one MCP server.
Overview
Email (IMAP/SMTP) is a MCP server for the Build phase that offers 22 tools for multi-account email read, send, search, and organization over IMAP/SMTP.
What is this MCP server?
- 22 MCP tools for reading, sending, searching, and organizing email
- Multi-account IMAP and SMTP in one server
- OCI image ghcr.io/boutquin/mcp-server-email:latest with stdio transport
- Configure via EMAIL_CONFIG_FILE path or inline EMAIL_ACCOUNTS JSON (secret)
- Title in registry: Email (IMAP/SMTP) for discoverability
- 22 MCP tools (per registry description)
- Registry version 1.0.1
Community signal: 2 GitHub stars.
What problem does it solve?
Your agent cannot safely touch real inboxes because each provider needs different IMAP/SMTP setup and you do not have time to script twenty mail operations yourself.
Who is it for?
Solo founders who run support and outbound mail from multiple accounts and want agent-driven triage inside MCP workflows.
Skip if: Teams that only need read-only newsletters, or builders who refuse to put mailbox credentials in agent-adjacent config.
What do I get? / Deliverables
After registration, your agent can work across configured accounts using a single MCP surface for mail actions you define in JSON config.
- Agent-callable access to 22 email operations across configured accounts
- Read, send, search, and organize workflows over standard IMAP/SMTP
Recommended MCP Servers
Journey fit
Email automation is wired during build when you connect product workflows, support inboxes, and outbound sequences to your agent stack. Integrations is the shelf for multi-account IMAP/SMTP bridging—not a standalone marketing skill or infra monitor.
How it compares
Multi-account mail MCP integration, not a CRM skill or transactional email API wrapper alone.
Common Questions / FAQ
Who is io.github.boutquin/email for?
It is for indie builders and small teams who want agents to manage IMAP/SMTP mail across several accounts through MCP tools.
When should I use io.github.boutquin/email?
Use it when you are integrating agent workflows with real email—support, follow-ups, or inbox search—during build or early grow operations.
How do I add io.github.boutquin/email to my agent?
Run the OCI image ghcr.io/boutquin/mcp-server-email:latest over stdio and supply EMAIL_CONFIG_FILE or the secret EMAIL_ACCOUNTS JSON array.