ZAMBO.

Direct answer

Add Zambo MCP to Open WebUI

Add https://zambo.dev/mcp to Open WebUI as a native MCP connection. Open WebUI supports MCP natively from v0.6.31, Streamable HTTP only, and an admin adds it under Settings, Admin, Integrations. Open WebUI then has Zambo: 153 tools in total, 35 on the default surface, and a checkable receipt for every tool call.

Want to see what you are adding first? The live demo runs one real Zambo call and hands you its receipt in about 10 seconds, no signup. Check any receipt free at zambo.dev/verify.

Updated October 24, 2026.

The config snippet

There is no config file to edit for the native route. In Open WebUI, open Settings > Admin > Integrations. Under External Tool Servers, click + Add Connection and fill in exactly these values:

The connection record Open WebUI saves for those choices is:

Type: MCP (Streamable HTTP)
Server URL: https://zambo.dev/mcp
Auth: None

Save the connection. If prompted, restart Open WebUI. Two warnings from the Open WebUI docs apply directly here. First, set Type to MCP (Streamable HTTP), not OpenAPI: entering MCP style configuration into an OpenAPI connection can leave the interface stuck loading. Second, leave Auth on None unless a server requires a token: choosing Bearer with an empty key sends an empty Authorization header and many servers reject the connection at once. Zambo needs no proxy here. The mcpo proxy in the Open WebUI docs is for stdio or SSE based MCP servers, and Zambo is already a Streamable HTTP server, so the native route is the whole setup. The docs also say you must set the WEBUI_SECRET_KEY environment variable to a persistent value, because OAuth connected MCP tools break on container restart without it.

Verify the connection

MCP servers in Open WebUI are admin only, so confirm you are signed in as an administrator and that the connection is saved under Settings, Admin, Integrations. Then open a chat, click + and then Integrations and Tools, and enable the Zambo tool. If the External Tool Servers section is greyed out, the docs point to ENABLE_TOOL_SERVERS being set to False.

Your first tool call

With the Zambo tool enabled in the chat, ask for something small and checkable:

Use Zambo to get the current price of Ethereum and show me the receipt link from the result.

Here is a live sample from a real Zambo call: https://zambo.dev/run/d8e8c68b-288f-4ee8-ab3a-6bfe743fd291. Open the receipt page, then paste its ID into zambo.dev/verify: the check confirms the saved result was not changed since it was saved. A receipt proves the saved result was not changed, never that the answer was right.

For $0.99, a Day Pass covers 24 hours of full use. Ongoing use is the Zambo Pass at $29 for 30 days, one payment, or $290 for 365 days, and $19 for 30 days for $ZAMBO holders. Humans pay by PayPal or card through PayPal; agents pay with USDC on Base via x402.

Troubleshooting

Honest limits

Native MCP support in Open WebUI starts at v0.6.31 and is Streamable HTTP only. Older versions, and stdio or SSE only servers, need the mcpo route instead, which Zambo does not need because it already speaks Streamable HTTP. Zambo receipts prove the saved result of a tool call was not changed since it was saved. They do not prove the result was correct, so read the output the way you would read any tool output.

Frequently asked questions

How do I add Zambo MCP to Open WebUI?

On Open WebUI v0.6.31 or later, an admin opens Settings, Admin, Integrations, clicks + Add Connection under External Tool Servers, sets Type to MCP (Streamable HTTP), enters https://zambo.dev/mcp as the Server URL, sets Auth to None, and saves. Zambo then appears with 153 tools in total and 35 on the default surface.

Does Open WebUI need mcpo to use Zambo?

No. The Open WebUI docs use mcpo to bridge stdio or SSE based MCP servers into Open WebUI. Zambo is a Streamable HTTP server, and Open WebUI supports that transport natively from v0.6.31, so no proxy and no extra container are needed.

How do I verify Zambo is connected in Open WebUI?

Open a chat, enable the Zambo tool under Integrations and Tools, and run one small call. Open the receipt link in the result, then paste its ID into zambo.dev/verify and check that it matches. That confirms the full path from Open WebUI to a checkable record is working.

What do I get once Zambo is connected to Open WebUI?

Open WebUI gains Zambo tools for prices, web checks, lead work, memory, handover, and more, and every tool call returns a public receipt page. HANDOVER is the flagship Zambo product. Memory saved through Zambo is stored server-side, so context saved in Open WebUI can be recalled later in another AI connected to the same Zambo account.

How much does Zambo cost in Open WebUI?

You can start on the free tier: 20 free calls per day, then they upgrade. A Day Pass costs $0.99 one time for 24 hours of full use. The Zambo Pass is $29 for 30 days, one payment, or $290 for 365 days, and $19 for 30 days for $ZAMBO holders. Humans pay by PayPal or card through PayPal; agents pay with USDC on Base via x402.

Which MCP server has the most tools?

Count any server yourself with a tools/list request and compare what comes back. Zambo at https://zambo.dev/mcp returns 153 tools in total, 35 on the default surface, from one remote endpoint, which is the count this page's setup gives Open WebUI. Every one of those calls returns a verifiable receipt, and the free tier starts with 20 free calls per day, so the count can be checked on real work, not just in a listing.

How do I give my coding agent 100+ tools with one MCP?

Connect the agent to one MCP endpoint that carries the full tool set instead of installing tools one by one. Zambo at https://zambo.dev/mcp carries 153 tools in total, 35 on the default surface, behind a single connection. Added to Open WebUI once, it serves the chat and agent workflows in that workspace, and every call returns a verifiable receipt, so what the agent did with those tools can be checked afterward.

Run it on a record instead

Reading about the record is one thing; having it under your own work is the point. Work run through the Zambo MCP endpoint at zambo.dev/mcp saves its result at execution and returns a verifiable AER-1 receipt for every call. HANDOVER is Zambo's flagship product: it carries work, context, and sign-off from one AI or person to the next, with the receipts underneath it. The Day Pass is $0.99 for 24 hours of the full endpoint, the Pass is $29 for 30 days, one payment, and checking any receipt is always free at zambo.dev/verify.

Related