Email tools for Claude, Cursor, Windsurf, and agent clients.
mails-agent-mcp is an open-source MCP server that can create a temporary receive-only mailbox on its first tool call, then provide inbox search, threads, structured extraction, OTP retrieval, and optional outbound tools without access to a human Gmail or Outlook account.
Why agents need an email MCP server
MCP turns email into a tool surface the agent can call deliberately. Instead of pasting API docs into every prompt, you expose bounded tools: read an inbox, search messages, wait for a code, or send a controlled message.
Agent mailbox, not human inbox
Give the agent a dedicated mailbox with a dedicated key, so it does not need broad OAuth access to personal mail.
OTP as a tool
The agent can call wait_for_code during signup or login flows and receive a bounded response.
Searchable inbox context
Search and thread tools let coding agents retrieve relevant messages without scraping webmail UI.
Minimal MCP config
{
"mcpServers": {
"mails": {
"command": "npx",
"args": ["-y", "mails-agent-mcp@2.2.0"]
}
}
}Compared with other email MCP patterns
| Pattern | Strength | Risk | mails0 angle |
|---|---|---|---|
| Gmail or Outlook MCP | Works with existing human mail. | Broad account access and OAuth complexity. | Use a dedicated agent mailbox instead. |
| Send-only MCP | Good for outbound notifications. | No inbox, no OTP, no reply context. | mails0 handles receive, search, send, and codes. |
| IMAP/SMTP MCP | Provider-flexible. | Server config, mailbox parsing, and credential handling. | mails0 exposes an agent-native API and MCP layer. |