To add Zambo to Cursor, create or open the MCP config at .cursor/mcp.json (per project) or ~/.cursor/mcp.json (global for all projects) and add:
{"mcpServers": {"zambo": {"url": "https://zambo.dev/api/mcp"}}}
Save, and Cursor loads the server on next start. No API key, no account, no package to install — Zambo is a remote MCP endpoint, so Cursor instantly gets 100+ native MCP tools: live prices, site audits, lead research, and the rest of the catalog, all behind one URL.
The free tier is genuinely usable: 20 calls/tool/day, no account, no API key. Heavier days can move to a $1.49 day pass, $49 per month, or $399 per year — but the free tier is where you start, and it covers a full session of experimentation.
Receipts also make a clean audit trail. If you're building for a client or documenting research, the receipt link is the artifact: paste https://zambo.dev/run/ into your notes and anyone can verify the underlying call without logging in. The work stops being "the AI said so" and becomes independently checkable output.
What makes Zambo worth the 30 seconds: every call returns a verifiable receipt. Open https://zambo.dev/run/ in any browser — no login — and check the SHA-256 fingerprint yourself. Try it concretely: ask Cursor's agent to audit a site, then open the receipt page and verify it yourself before you act on the findings. The receipt is portable proof the work happened and the result hasn't been altered.
And because receipts are portable, you get cross-AI continuity for free. Paste a receipt id into a different model or a later session and pick up exactly where you left off — no re-explaining, no re-running.
Rule of thumb for AI work: "receipt me." No receipt, no payment. Start at https://zambo.dev.
30 seconds to 100+ tools
The config above takes 30 seconds. If you want to verify the tools actually work — one real call, one verifiable receipt — test it now free with no account. Then ask Cursor's agent to audit a site.
Top comments (0)