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