Every MCP setup guide I followed this year had the same shape: install a server for files, a server for search, a server for prices, a server for memory, and keep a config file full of local processes that break one at a time. I wanted the opposite. One remote endpoint, the whole catalog behind it, and a record of what ran.
This is the setup I use now, with the numbers checked against the live catalog today.
The one command
For Claude Code:
claude mcp add --transport http zambo https://zambo.dev/mcp
For Cursor, VS Code, Windsurf, or Codex, the same URL goes in the MCP config as a remote HTTP server named zambo. One endpoint, every client. No local process, no API key, no account.
What is actually behind it
The default surface is 36 tools. The full catalog is 153 tools, and the way you reach the rest is the part most single-purpose servers do not have: a capability search that takes a plain-language need and returns the matching tools from the full catalog.
I ran one today from a coding session, searching for tools for coding agents. The call came back with the ranked matches, and the platform wrote receipt 6072dad7-dc9a-45c5-88c8-93c895aeb545 as it executed. You can open it here:
https://zambo.dev/run/6072dad7-dc9a-45c5-88c8-93c895aeb545
That receipt is the second half of why I run my work through one endpoint. Every call, the search calls included, leaves a verifiable receipt: the tool, the time, the caller it is bound to, and the saved result, which anyone can recompute at the receipt's verify endpoint. When the agent says a step is done, the record is something I can check instead of something I have to trust.
The free tier, stated exactly
20 calls plus 1 wrap-up free every day, per caller, no account. The wrap-up is the handover tool: it seals a job into a record another AI can pick up, which matters the first time you switch from Claude Code to Cursor mid-task and want the work, not a summary of the work, to make the trip. Picking up a handover in another AI is always free.
When a job runs past the free calls, a Day Pass is $0.99 for unlimited use for 24 hours. Agents can pay it themselves in USDC on Base when an endpoint speaks x402. Humans pay by card or PayPal.
When one endpoint is the wrong answer
If you need exactly one narrow tool and nothing else, a dedicated local server is simpler. The one-endpoint setup earns its place when the work sprawls: research, then files, then a price check, then memory, then a handover to a different AI to finish. That sprawl is most of my real workload, and it is where per-job server installs fall apart.
One URL. 153 tools behind it. A receipt for every call. That is the whole stack.
Top comments (0)