LaunchEngine.dev vs Zambo
A side-by-side look at the LaunchEngine.dev and Zambo MCP servers: transport, auth, tools, quality signals, and the config to install either one in Claude, Cursor, Windsurf or VS Code.
L
LaunchEngine.devDeveloper Tools · Local subprocess (stdio)Find posts where someone is asking for a product like yours, scored 1-100, with reply drafts.53GoodAuth: api key requiredVerdict: choose LaunchEngine.dev for developer tools work as a local process; choose Zambo for developer tools over a hosted endpoint. You can also run both side by side in one mcpServers block.
Which MCP server should you choose?
LChoose LaunchEngine.dev when
- You need dedicated capabilities in the Developer Tools domain.
- You prefer a local stdio subprocess transport.
- Its auth model fits you: API key required.
- You have the keys it needs:
LAUNCHENGINE_DEV_API_KEY. - You want tools like
list_projects, get_credit_balance, find_intent_signals.
Choose Zambo when
- You need dedicated capabilities in the Developer Tools domain.
- You prefer a remote HTTP/SSE transport.
- Its auth model fits you: No auth required.
- You want tools like
workflow_close, workflow_seal, zambo_universal.
Feature & specification comparison
Rows where the two servers differ are marked.
| Spec | L LaunchEngine.dev | |
|---|---|---|
| Category | Developer Tools | Developer Tools |
| Quality signal | 53/100 · Good | 78/100 · Great |
| Install command | Confirmed | Confirmed |
| Transport | Local subprocess (stdio) | Remote HTTP/SSE |
| Auth | API key required | No auth required |
| Pricing | Not declared | Free |
| Required env vars | LAUNCHENGINE_DEV_API_KEY | None listed |
| Verified owner |
Tools & capabilities
LaunchEngine.dev tools 6
list_projectsYour projects: name, URL, description, target ICP, competitors. Start hereget_credit_balanceCredit balance and planfind_intent_signalsScored posts for a project, highest intent first. `scan: true` searches live sources firstget_intent_detailsOne signal in full: post, author, score, reasons, saved draftdraft_replyA reply for you to review and post, in a `consultative`, `direct` or `technical` tonesubscribe_to_keywordAdd a keyword for a project's scans to search
Zambo tools 23
workflow_closeCreate or return an immutable snapshot of this job's eligible receipts. Repeating the call with unchanged receipt data returns the same snapshot workflow_id; later calls after new receipts create a separate snapshot while session_workflow_id continues identifying the live ledger. Both identifiers are unbound metadata excluded from canonical receipt bytes. The first close returns a one-time private workflow_manage_token; retries do not rotate or reissue it. The workflow_close summary receipt is excluded from the step count. Records Zambo's claims, not issuer authentication.workflow_sealSeals a closed workflow for durable export. Requires the matching job session and an active pass. Never spends, captures, or starts a payment. The export remains a Zambo claim, not issuer authentication.zambo_universalUniversal Zambo entry point for routing natural-language requests across supported Zambo tools through one MCP connection. Covers strategy, code audits, lead generation, wallet intelligence, provenance certificates, swarm coordination, and live market data. Returns a route, execution state, downstream tool results when available, and receipt information.
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.
LaunchEngine.dev
{
"mcpServers": {
"launchengine-dev": {
"command": "npx",
"args": [
"-y",
"@launchengine-dev/mcp"
],
"env": {
"LAUNCHENGINE_DEV_API_KEY": "YOUR_LAUNCHENGINE_DEV_API_KEY_HERE"
}
}
}
}
Zambo
{
"mcpServers": {
"zambo": {
"command": "npx",
"args": [
"-y",
"zambo"
]
}
}
}
Frequently asked questions
LaunchEngine.dev is categorized under Developer Tools and uses a local stdio subprocess. Zambo belongs to Developer Tools and uses a remote HTTP/SSE transport. Pick LaunchEngine.dev for developer tools work and Zambo for developer tools.
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.
LaunchEngine.dev has no declared pricing — check the project's own site. Auth: api key required. Zambo 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 launchengine-dev and zambo as separate keys in the same mcpServers object, and your assistant will call tools from either one.
On AllMCPs, LaunchEngine.dev has a quality signal of 53/100 (Good) with 0 views, 0 installs and 0 GitHub stars. Zambo has 78/100 (Great) with 9 views, 0 installs and 0 GitHub stars.
