What you need
A recent Cursor version with MCP support and the following standard remote-server configuration:
Cursor's available settings and config locations can change. Refer to the current Cursor MCP documentation for the supported file location and schema in your version.
Add the server
- Open Cursor's current Settings area and find its MCP or tools section. The exact navigation path varies by release.
- Choose the option to add a server, then select the remote HTTP or URL-based server type when offered.
- Enter the canonical URL
https://zambo.dev/mcpand name the serverzambo. - Leave authentication, command, arguments, and environment variables empty. This is a remote endpoint.
- Enable the server and open Cursor's agent/chat panel.
Config-file option
If your version supports a global or project MCP file, add the same JSON to the location documented by Cursor. Do not assume a file path from an older release.
Verify it works
Ask the agent to list its available tools or request a small Zambo task, such as generating a QR code for https://zambo.dev. A completed tool call means the server is live. If it does not connect, check that the URL is exact and reload Cursor.
Machine detail: MCP clients may begin with a default list; a client requesting the full catalog can receive the live catalog. Cursor controls how the list is presented.
Usage and pricing
Zambo's free tier provides 20 free calls per metered tool each day with no account. The verified Day Pass is $0.99 for 24 hours, paid in USDC on Base through day_pass_activate. The Zambo Pass is $29/month or $290/year; verified $ZAMBO holders pay $19/month.
Quick FAQ
No. Cursor connects to Zambo's remote HTTP endpoint; no local server or npm install is needed.
Brennan Zambo built Zambo solo. It is MIT licensed.