Email Automation MCP vs Mail
A side-by-side look at the Email Automation MCP and Mail 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 Email Automation MCP for communication work as a local process; choose Mail for communication over a hosted endpoint. You can also run both side by side in one mcpServers block.
Which MCP server should you choose?
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.
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.
Feature & specification comparison
Rows where the two servers differ are marked.
| Spec | M Mail | |
|---|---|---|
| Category | Communication | Communication |
| Quality signal | 44/100 · Fair | 39/100 · Fair |
| Install command | Confirmed | Confirmed |
| Transport | Local subprocess (stdio) | Remote HTTP/SSE |
| Auth | other | OAuth 2.0 |
| Pricing | Free | Not declared |
| Required env vars | None listed | None listed |
| Verified owner | Community listing | Community listing |
| GitHub stars | 0 | — |
| Directory activity | 5 views 0 installs 0 upvotes | 0 views 0 installs 0 upvotes |
| Tools | Not listed | Not listed |
| Full listing | View Email Automation MCP | View Mail |
Tools & capabilities
Email Automation MCP tools
No tool names declared yet. Check the project README from the listing page.
Mail 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.
Email Automation MCP
{
"mcpServers": {
"email-automation-mcp": {
"command": "npx",
"args": [
"-y",
"meok-setup"
]
}
}
}
{
"mcpServers": {
"mail": {
"command": "npx",
"args": [
"-y",
"mail"
]
}
}
}
Frequently asked questions
Email Automation MCP is categorized under Communication and uses a local stdio subprocess. Mail belongs to Communication and uses a remote HTTP/SSE transport. Pick Email Automation MCP for communication work and Mail 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.
Email Automation MCP is listed as free. Auth: other. Mail has no declared pricing — check the project's own site. Auth: oauth 2.0. 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 email-automation-mcp and mail as separate keys in the same mcpServers object, and your assistant will call tools from either one.
On AllMCPs, Email Automation MCP has a quality signal of 44/100 (Fair) with 5 views, 0 installs and 0 GitHub stars. Mail has 39/100 (Fair) with 0 views, 0 installs and 0 GitHub stars.