Lhremote vs Mailzzy
A side-by-side look at the Lhremote 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 Lhremote 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 Lhremote when
- You need dedicated capabilities in the Marketing domain.
- You prefer a local stdio subprocess transport.
- Its auth model fits you: No auth required.
- You want tools like
find-app, launch-app, quit-app.
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.
Tools & capabilities
Lhremote tools 75
find-appDetect running LinkedHelper application instances and their CDP connection details.launch-appLaunch the LinkedHelper application with remote debugging enabled.quit-appQuit the LinkedHelper application.list-accountsList available LinkedHelper accounts. Returns account ID, LinkedIn ID, name, and email for each account. Returns accounts in the currently selected workspace by default (LinkedHelper 2.113.x+); set `includeAllWorkspaces` to enumerate every workspace the current LH user belongs to.list-workspacesList LinkedHelper workspaces the current LH user belongs to. Each workspace includes the user's role and a `selected` flag indicating the currently active workspace. Returns an empty list on LinkedHelper versions that predate workspaces (pre-2.113.x).start-instanceStart a LinkedHelper instance for a LinkedIn account.stop-instanceStop a running LinkedHelper instance.check-statusCheck LinkedHelper connection status, running instances, and database health.campaign-listList existing campaigns with summary statistics.campaign-createCreate a new campaign from YAML or JSON configuration.campaign-getGet detailed campaign information including action chain.campaign-exportExport campaign configuration as YAML or JSON.- +63 more on 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.
Lhremote
{
"mcpServers": {
"alexey-pelykh-lhremote": {
"command": "npx",
"args": [
"-y",
"lhremote"
]
}
}
}
Mailzzy
{
"mcpServers": {
"mailzzy": {
"url": "https://api.mailzzy.com/crm/mcp/"
}
}
}
Frequently asked questions
Lhremote is categorized under Marketing and uses a local stdio subprocess. Mailzzy belongs to Marketing and uses a remote HTTP/SSE transport. Pick Lhremote 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.
Lhremote is listed as a paid service. Auth: no auth required. 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 alexey-pelykh-lhremote and mailzzy as separate keys in the same mcpServers object, and your assistant will call tools from either one.
On AllMCPs, Lhremote has a quality signal of 60/100 (Good) with 3 views, 0 installs and 19 GitHub stars. Mailzzy has 48/100 (Fair) with 1 views, 0 installs and 0 GitHub stars.