Direct answer

Add Zambo MCP to Goose

Add https://zambo.dev/mcp to Goose as a remote extension. Run goose configure, choose Add Extension, then Remote Extension (Streamable HTTP), name it zambo, and paste the endpoint URI. Goose 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

For a saved setup, Goose stores extensions under the extensions block in ~/.config/goose/config.yaml. Add this entry, keeping any extensions you already have. The interactive route writes the same entry for you: run goose configure, choose Add Extension, then Remote Extension (Streamable HTTP), enter the name zambo, the endpoint URI below, and the timeout 300 when prompted.

extensions:
  zambo:
    name: Zambo
    type: streamable_http
    uri: https://zambo.dev/mcp
    enabled: true
    timeout: 300

The field names matter: Goose uses type: streamable_http with an underscore and the endpoint under uri, not url. Zambo is a hosted remote server, so there is no command to run locally. In Goose Desktop the same setup is sidebar, Extensions, Add custom extension, with the type set to Streamable HTTP and the same URI. For a one-off session only, skip the config and run goose session --with-streamable-http-extension "https://zambo.dev/mcp".

Verify the connection

Start a new Goose session, or restart Goose if it was already open, so the new extension loads. Zambo should be enabled and its tools should be available in the session. If the extension fails to activate, open ~/.config/goose/config.yaml and check the entry first: the type, the uri value, and the YAML indentation under extensions.

Your first tool call

Ask Goose for something small and checkable:

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

Here is a live sample from a real Zambo call: https://zambo.dev/run/578cbf05-1011-48bc-b3b5-7b3289f6035b. 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

Goose supports remote extensions over Streamable HTTP, which is what this setup uses. Very old Goose builds that predate remote extensions cannot connect this way and need an update first. 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 Goose?

Run goose configure, choose Add Extension, then Remote Extension (Streamable HTTP), name it zambo, and enter https://zambo.dev/mcp as the endpoint URI. Or add a zambo entry under extensions in ~/.config/goose/config.yaml with type streamable_http, uri set to https://zambo.dev/mcp, enabled true, and timeout 300. Zambo then appears with 153 tools in total and 35 on the default surface.

Does Goose need a command to run Zambo?

No. Zambo is a hosted remote server, so the Goose entry has a type and a uri and no cmd or args block. A command is only for a locally run stdio extension, which Zambo is not.

How do I verify Zambo is connected in Goose?

Start a new session and ask Goose to run one small Zambo 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 Goose to a checkable record is working.

What do I get once Zambo is connected to Goose?

Goose 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 Goose can be recalled later in another AI connected to the same Zambo account.

How much does Zambo cost in Goose?

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 Goose. 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.

Is there a free MCP server with no account required?

Yes. Zambo's MCP endpoint at https://zambo.dev/mcp can be added to Goose with no account, no API key, and no credit card, and the free tier gives you 20 free calls per day. Every free call still returns a verifiable receipt at a public link. When the day's free calls are used up, a Day Pass covers 24 hours for $0.99, and the Zambo Pass is $29 for 30 days for ongoing work.

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