Email Automation MCP vs MailFathom
A side-by-side look at the Email Automation MCP and MailFathom MCP servers: transport, auth, tools, quality signals, and the config to install either one in Claude, Cursor, Windsurf or VS Code.
Verdict: choose Email Automation MCP for communication work as a local process; choose MailFathom for communication. 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.
Choose MailFathom when
- You need dedicated capabilities in the Communication domain.
Feature & specification comparison
Rows where the two servers differ are marked.
| Spec | ||
|---|---|---|
| Category | Communication | Communication |
| Quality signal | 43/100 · Fair | 32/100 · Emerging |
| Install command | Confirmed | Not confirmed yet |
| Transport | Local subprocess (stdio) | — |
| Auth | other | Not declared |
| Pricing | Free | Not declared |
| Required env vars | None listed | None listed |
| Verified owner | Community listing | Community listing |
| GitHub stars | 0 | 15 |
| Directory activity | 4 views 0 installs 0 upvotes | 0 views 0 installs 0 upvotes |
| Tools | Not listed | Not listed |
| Full listing | View Email Automation MCP | View MailFathom |
Tools & capabilities
Email Automation MCP tools
No tool names declared yet. Check the project README from the listing page.
MailFathom 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"
]
}
}
}
MailFathom
No confirmed install command for MailFathom yet — follow the setup steps linked from its listing page rather than a guessed package name.
Frequently asked questions
Email Automation MCP is categorized under Communication and uses a local stdio subprocess. MailFathom belongs to Communication and uses an install path we have not confirmed yet. Pick Email Automation MCP for communication work and MailFathom 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. MailFathom has no confirmed install command yet — follow its own setup instructions.
Email Automation MCP is listed as free. Auth: other. MailFathom has no declared pricing — check the project's own site. 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 mailfathom-2 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 43/100 (Fair) with 4 views, 0 installs and 0 GitHub stars. MailFathom has 32/100 (Emerging) with 0 views, 0 installs and 15 GitHub stars.
