Secure Mail MCP
A provider-neutral blueprint for building safety-first mail MCP servers.
What it solves
It separates mail-provider adapters from MCP policy and confirmation boundaries.
Architecture
MCP server, provider interface, IMAP/SMTP adapters, and an explicit confirmation gate.
What is included
Threat model, environment example, test plan, and implementation guidance.
What is intentionally excluded
Private production code, credentials, deployment OAuth configuration, and provider account data.
Security model
Read operations are conservative; sending and mutations require explicit confirmation.
Suitable use cases
Building an account-scoped IMAP/SMTP MCP server.