Mail vs Email Automation MCP
A side-by-side look at the Mail and Email Automation MCP MCP servers: transport, auth, tools, quality signals, and the config to install either one in Claude, Cursor, Windsurf or VS Code.
M
MailCommunication · Remote HTTP/SSEEmail + calendar for any IMAP/CalDAV mailbox — OVH, Gandi, iCloud, Zoho, Fastmail and more.39FairAuth: oauth 2.0Verdict: choose Mail for communication work over a hosted endpoint; choose Email Automation MCP for communication as a local process. You can also run both side by side in one mcpServers block.
Which MCP server should you choose?
MChoose Mail when
- You need dedicated capabilities in the Communication domain.
- You prefer a remote HTTP/SSE transport.
- Its auth model fits you: OAuth 2.0.
Choose Email Automation MCP when
- You need dedicated capabilities in the Communication domain.
- You prefer a local stdio subprocess transport.
- Its auth model fits you: other.
Feature & specification comparison
Rows where the two servers differ are marked.
| Spec | M Mail | |
|---|---|---|
| Category | Communication | Communication |
| Quality signal | 39/100 · Fair | 44/100 · Fair |
| Install command | Confirmed | Confirmed |
| Transport | Remote HTTP/SSE | Local subprocess (stdio) |
| Auth | OAuth 2.0 | other |
| Pricing | Not declared | Free |
| Required env vars | None listed | None listed |
| Verified owner | Community listing | Community listing |
| GitHub stars | — | 0 |
| Directory activity | 0 views 0 installs 0 upvotes | 5 views 0 installs 0 upvotes |
| Tools | Not listed | Not listed |
| Full listing | View Mail | View Email Automation MCP |
Tools & capabilities
Mail tools
No tool names declared yet. Check the project README from the listing page.
Email Automation MCP tools
No tool names declared yet. Check the project README from the listing page.
Ready-to-paste client configs
Paste either block (or both) into your client config, e.g. claude_desktop_config.json or ~/.cursor/mcp.json. We only show a config when the install command is confirmed.
{
"mcpServers": {
"mail": {
"command": "npx",
"args": [
"-y",
"mail"
]
}
}
}
Email Automation MCP
{
"mcpServers": {
"email-automation-mcp": {
"command": "npx",
"args": [
"-y",
"meok-setup"
]
}
}
}
Frequently asked questions
Mail is categorized under Communication and uses a remote HTTP/SSE transport. Email Automation MCP belongs to Communication and uses a local stdio subprocess. Pick Mail for communication work and Email Automation MCP for communication.
Copy the mcpServers block from the config section on this page into your client's config (for example claude_desktop_config.json or ~/.cursor/mcp.json), then fully restart the client.
Mail has no declared pricing — check the project's own site. Auth: oauth 2.0. Email Automation MCP is listed as free. Auth: other. If a server needs environment variables such as API keys, define them under the env key in your client's MCP config.
Yes. MCP clients support multiple servers: add mail and email-automation-mcp as separate keys in the same mcpServers object, and your assistant will call tools from either one.
On AllMCPs, Mail has a quality signal of 39/100 (Fair) with 0 views, 0 installs and 0 GitHub stars. Email Automation MCP has 44/100 (Fair) with 5 views, 0 installs and 0 GitHub stars.