Mailzzy vs Jmpy MCP Server
A side-by-side look at the Mailzzy and Jmpy MCP Server MCP servers: transport, auth, tools, quality signals, and the config to install either one in Claude, Cursor, Windsurf or VS Code.
M
MailzzyMarketing · Remote HTTP/SSEAllows AI assistants to interact with Mailzzy for email marketing tasks, including campaign management, contact handling, template operations, sending, and automation.48FairAuth: not declaredVerdict: choose Mailzzy for marketing work over a hosted endpoint; choose Jmpy MCP Server for marketing as a local process. You can also run both side by side in one mcpServers block.
Which MCP server should you choose?
MChoose Mailzzy when
- You need dedicated capabilities in the Marketing domain.
- You prefer a remote HTTP/SSE transport.
Choose Jmpy MCP Server when
- You need dedicated capabilities in the Marketing domain.
- You prefer a local stdio subprocess transport.
- You have the keys it needs:
JMPY_API_KEY.
Feature & specification comparison
Rows where the two servers differ are marked.
| Spec | M Mailzzy | |
|---|---|---|
| Category | Marketing | Marketing |
| Quality signal | 48/100 · Fair | 39/100 · Fair |
| Install command | Confirmed | Confirmed |
| Transport | Remote HTTP/SSE | Local subprocess (stdio) |
| Auth | Not declared | Not declared |
| Pricing | Not declared | Not declared |
| Required env vars | None listed | JMPY_API_KEY |
| Verified owner | Community listing |
Tools & capabilities
Mailzzy tools
No tool names declared yet. Check the project README from the listing page.
Jmpy MCP Server 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.
Mailzzy
{
"mcpServers": {
"mailzzy": {
"url": "https://api.mailzzy.com/crm/mcp/"
}
}
}
Jmpy MCP Server
{
"mcpServers": {
"jmpy-mcp-server": {
"command": "npx",
"args": [
"-y",
"jmpy-mcp-server"
],
"env": {
"JMPY_API_KEY": "YOUR_JMPY_API_KEY_HERE"
}
}
}
}
Frequently asked questions
Mailzzy is categorized under Marketing and uses a remote HTTP/SSE transport. Jmpy MCP Server belongs to Marketing and uses a local stdio subprocess. Pick Mailzzy for marketing work and Jmpy MCP Server for marketing.
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.
Mailzzy has no declared pricing — check the project's own site. Jmpy MCP Server 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 mailzzy and jmpy-mcp-server as separate keys in the same mcpServers object, and your assistant will call tools from either one.
On AllMCPs, Mailzzy has a quality signal of 48/100 (Fair) with 1 views, 0 installs and 0 GitHub stars. Jmpy MCP Server has 39/100 (Fair) with 2 views, 0 installs and 0 GitHub stars.
