Call4me vs Leadmagic
A side-by-side look at the Call4me and Leadmagic MCP servers: transport, auth, tools, quality signals, and the config to install either one in Claude, Cursor, Windsurf or VS Code.
L
LeadmagicCommunication · Local subprocess (stdio)LeadMagic MCP — wraps the LeadMagic B2B email-finder API (leadmagic.io)41FairAuth: api key requiredVerdict: choose Call4me for communication work over a hosted endpoint; choose Leadmagic for communication as a local process. You can also run both side by side in one mcpServers block.
Which MCP server should you choose?
Choose Call4me when
- You need dedicated capabilities in the Communication domain.
- You prefer a remote HTTP/SSE transport.
- Its auth model fits you: OAuth 2.0.
LChoose Leadmagic when
- You need dedicated capabilities in the Communication domain.
- You prefer a local stdio subprocess transport.
- Its auth model fits you: API key required.
Feature & specification comparison
Rows where the two servers differ are marked.
| Spec | L Leadmagic | |
|---|---|---|
| Category | Communication | Communication |
| Quality signal | 79/100 · Great | 41/100 · Fair |
| Install command | Confirmed | Confirmed |
| Transport | Remote HTTP/SSE | Local subprocess (stdio) |
| Auth | OAuth 2.0 | API key required |
| Pricing | Paid service | BYOK (pay the provider) |
| Required env vars | None listed | None listed |
| Verified owner | Verified |
Tools & capabilities
Call4me tools
No tool names declared yet. Check the project README from the listing page.
Leadmagic 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.
Call4me
{
"mcpServers": {
"call4me": {
"url": "https://call4.me/mcp"
}
}
}
Leadmagic
{
"mcpServers": {
"leadmagic": {
"command": "npx",
"args": [
"-y",
"@pipeworx/mcp-leadmagic"
]
}
}
}
Frequently asked questions
Call4me is categorized under Communication and uses a remote HTTP/SSE transport. Leadmagic belongs to Communication and uses a local stdio subprocess. Pick Call4me for communication work and Leadmagic 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.
Call4me is listed as a paid service. Auth: oauth 2.0. Leadmagic is bring-your-own-key: usage is billed by the API provider you supply a key for. Auth: api key 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 call4me and leadmagic as separate keys in the same mcpServers object, and your assistant will call tools from either one.
On AllMCPs, Call4me has a quality signal of 79/100 (Great) with 6 views, 1 installs and 12 GitHub stars. Leadmagic has 41/100 (Fair) with 0 views, 0 installs and 0 GitHub stars.
