Leadharbor MCP vs Emailmd
A side-by-side look at the Leadharbor MCP and Emailmd MCP servers: transport, auth, tools, quality signals, and the config to install either one in Claude, Cursor, Windsurf or VS Code.
L
Leadharbor MCPCommunication · Local subprocess (stdio)Email verify (MX), website contacts, LinkedIn jobs, YouTube data via RapidAPI. Bring your own key.41FairAuth: api key requiredVerdict: choose Leadharbor MCP for communication work as a local process; choose Emailmd for communication as a local process. You can also run both side by side in one mcpServers block.
Which MCP server should you choose?
LChoose Leadharbor MCP when
- You need dedicated capabilities in the Communication domain.
- You prefer a local stdio subprocess transport.
- Its auth model fits you: API key required.
- You have the keys it needs:
RAPIDAPI_KEY.
Choose Emailmd when
- You need dedicated capabilities in the Communication domain.
- You prefer a local stdio subprocess transport.
- Its auth model fits you: No auth required.
Feature & specification comparison
Rows where the two servers differ are marked.
| Spec | L Leadharbor MCP | |
|---|---|---|
| Category | Communication | Communication |
| Quality signal | 41/100 · Fair | 64/100 · Good |
| Install command | Confirmed | Confirmed |
| Transport | Local subprocess (stdio) | Local subprocess (stdio) |
| Auth | API key required | No auth required |
| Pricing | BYOK (pay the provider) | Free |
| Required env vars | RAPIDAPI_KEY | None listed |
Tools & capabilities
Leadharbor MCP tools
No tool names declared yet. Check the project README from the listing page.
Emailmd 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.
Leadharbor MCP
{
"mcpServers": {
"leadharbor-mcp": {
"command": "npx",
"args": [
"-y",
"leadharbor-mcp"
],
"env": {
"RAPIDAPI_KEY": "YOUR_RAPIDAPI_KEY_HERE"
}
}
}
}
Emailmd
{
"mcpServers": {
"anypost-emailmd": {
"command": "npx",
"args": [
"-y",
"emailmd"
]
}
}
}
Frequently asked questions
Leadharbor MCP is categorized under Communication and uses a local stdio subprocess. Emailmd belongs to Communication and uses a local stdio subprocess. Pick Leadharbor MCP for communication work and Emailmd 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.
Leadharbor MCP is bring-your-own-key: usage is billed by the API provider you supply a key for. Auth: api key required. Emailmd is listed as free. Auth: no auth required. 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 leadharbor-mcp and anypost-emailmd as separate keys in the same mcpServers object, and your assistant will call tools from either one.
On AllMCPs, Leadharbor MCP has a quality signal of 41/100 (Fair) with 0 views, 0 installs and 0 GitHub stars. Emailmd has 64/100 (Good) with 2 views, 0 installs and 1,380 GitHub stars.