Direct answer

Add Zambo MCP to Meta Muse

Add Zambo to Meta Muse by asking Muse to build the connection. Meta's Help Center says that if you want to connect to a service not yet in the Connector list, you can ask Muse to create a Custom Connector and Muse will guide you through the process. Send Muse one message naming https://zambo.dev/mcp, follow its steps, and Muse then has Zambo: 153 tools in total, 35 on the default surface, and a checkable receipt for every tool call.

The one-message install

Paste this into a Muse chat, exactly as written:

Build a custom connector to Zambo. Name: Zambo. MCP server URL: https://zambo.dev/mcp. Transport: remote streamable HTTP. Auth: none. Test it with a first call and show me the receipt link it returns, then save the connector for future chats.

No key, no signup: Zambo's endpoint is open. There is no API key to paste and no Zambo account to create; the free tier starts at 20 free calls per day.

The fields, if Muse asks: Name: Zambo. URL: https://zambo.dev/mcp. Transport: remote streamable HTTP. Auth: none. Your first call comes back with a receipt link (a zambo.dev/run/ page) that anyone can open and check. The custom connector route works today; Zambo's Muse directory listing is in review with Meta.

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.

Last checked October 24, 2026, against Meta's Muse Help Center pages on connectors.

The setup steps

There is no Zambo entry to tap in Muse's Connector list, and no settings field where you paste an MCP address for a custom connector. The route Meta documents for a service that is not listed is a chat request, as follows.

Open Muse and start a new chat. Open Muse in the Muse app, on the web, or in WhatsApp, signed in with your Meta account, and start a fresh conversation.
Ask Muse to create the custom connector. Send this exact message: Create a custom connector for https://zambo.dev/mcp
Follow the guided setup. Muse guides you through the process. Meta says that process can involve retrieving API information from the service, so if Muse asks what to connect to, give it the same address: https://zambo.dev/mcp. Meta says Muse stores that information in its Secure Credentials Store.
Approve the connection. Read what Muse shows you about the connection and approve it, following any additional login or authorization steps Muse presents.
Ask for a test call. Ask Muse to use the new Zambo connection for one small job, for example the first prompt below, and to include the receipt link in its answer.

Meta's warning, in its own Help Center: Meta does not review custom connectors or how they use your information, so grant access with caution and review the provider's privacy policies. Connect only services you trust, including Zambo.

Check it worked

Send Muse this check prompt: Use Zambo to check the current price of Bitcoin, and include the receipt link for the call in your reply. A current price plus a receipt link means it worked.

Look for the Zambo connection in the answer Muse gives to the test call: a current result plus a receipt link means the connector reached the server. Open the receipt page, then paste its ID into zambo.dev/verify and run the free check. A match confirms the full path from Muse to a saved, checkable record is working. Meta also notes you can disconnect a Connector at any time in Settings, under Connectors.

Your first tool call

Use this first prompt in Muse: Use Zambo to check the current price of Bitcoin, and include the receipt link for the call in your reply. The answer comes back with current data and a receipt link, instead of a price remembered from training.

Sample receipt from a real Zambo call run for this page: https://zambo.dev/run/173481e8-6352-493c-90d2-c0456ae64e9a. Open it, then paste its ID into zambo.dev/verify: the check confirms the saved result was not changed after the fact.

Why that link settles arguments: an agent receipt is a record of one ai agent tool call that anyone can check: it keeps the exact saved bytes and their sha-256 digest, and it proves the result was not changed since it was saved, not that it 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

Muse starts building something else. Repeat the one line request exactly, with the full address: Create a custom connector for https://zambo.dev/mcp. Naming the service address is the API information Muse needs to retrieve.
Muse asks for credentials. Enter information only through the secure prompt Muse presents, never as a plain chat message when a secure prompt is offered. Meta says connector information is stored in Muse's Secure Credentials Store.
The connection works once and then stops. Ask Muse in a new chat to use the Zambo custom connector again. If it cannot find it, repeat the setup message above; the service address has not changed.

Honest limits

Meta's Help Center article on Muse connectors describes custom connectors in terms of a service and the API information Muse retrieves from it; the article does not name MCP. The setup on this page follows that documented route exactly, giving Muse the Zambo MCP endpoint as the service address in the request. What Muse builds from that request runs in your Muse only, and Meta does not review it. By default, Muse will not take many important actions, like sending an email, without your approval, and many connectors can be set to retrieve data only; you can change when Muse asks in Settings. Zambo receipts prove the saved result of a tool call was not changed after the fact. 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 Meta Muse?

Ask Muse in a chat. Meta's Help Center says you can ask Muse to create a Custom Connector for a service not yet in the Connector list, and Muse will guide you through the process. Send: Create a custom connector for https://zambo.dev/mcp, then follow the guided steps and approve the connection. Zambo then offers 153 tools in total and 35 on the default surface.

Is there a settings screen where I paste the Zambo address in Muse?

Not for a custom connector. Meta documents two routes: tap a listed Connector under Settings, then Connectors, or ask Muse to create a Custom Connector for an unlisted service. Zambo uses the second route, so the address goes in the chat request, not in a settings field.

Does Meta review the Zambo custom connector?

No. Meta says it does not review custom connectors or how they use your information, so grant access with caution and review the provider's privacy policies. The connection is built for your Muse only.

What do I get once Zambo is connected to Meta Muse?

Muse 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 product: a finished job can be packaged as one handover link carrying the goal, the steps, the outputs, and any open items. Memory saved through Zambo is stored server side, so context saved in Muse can be recalled later in Claude, Cursor, ChatGPT, or Grok when they are connected to the same Zambo account.

How much does Zambo cost in Meta Muse?

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 Meta Muse. 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. Zambo at https://zambo.dev/mcp carries 153 tools in total, 35 on the default surface, behind a single remote connection: no per-tool installs and no local server to run. In Meta Muse that is one endpoint entry, and the same entry gives a coding agent the full set, with a verifiable receipt returned on every call.

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