Add Zambo to Muse in one message
Muse has no add-a-server form to hunt through, and there is nothing to install: the way in is to ask. Muse connects to remote MCP servers as custom connectors it builds itself, and Zambo is a remote MCP server that needs no API key and no account. The whole setup is one message, and the only thing you paste is the URL:
Create a custom connector for Zambo, a remote MCP server.
Name: Zambo
URL: https://zambo.dev/mcp
Transport: remote streamable HTTP
Auth: none, no API key
Connect to it, test the tools, and save it so you can use Zambo in future conversations.Send that in any Muse chat (web, iOS, Android, or WhatsApp). Muse builds the connector, connects to the server, and tests the tools itself. If it asks about transport or authentication, the answers are already in the message: streamable HTTP, and none. The honest count is 1 message, 1 paste, 0 forms, 0 keys. Once connected, you can review or disconnect the connector any time under Settings, then Connectors.
What Muse's work looks like with receipts on
A Muse agent does personal-agent work: it researches, writes, and runs multi-step jobs while you are doing something else. With Zambo connected, each of those jobs carries its own evidence.
Research
Ask Muse to check prices, gather sources, or audit a page, and every lookup it runs through Zambo is recorded as it executes: the tool, a hash of what it was asked, and the exact result bytes that came back. When the brief lands, each claim in it can be traced to a receipt instead of to the agent's confidence.
Writing
Drafts, summaries, and rewrites produced through connected tools carry the record of what was actually generated and from what inputs. The words in the chat are the deliverable; the receipt underneath shows which call produced them and that the saved result is the one you are reading.
Multi-step jobs
For a job with several steps, each step leaves its own receipt, and the steps bind into one workflow record with a single root. If a job stalls halfway and says nothing, the record shows it plainly: the steps that landed, and then a hole where the rest should be. That hole is the finding, and no summary can paper over it.
Check the record from anywhere
A receipt is not locked inside the Muse chat that produced it. Open its URL from any browser and you see what ran, what it was given, and the exact saved result. Check it at zambo.dev/verify/, or recompute the SHA-256 commitments yourself from the bytes on the page; the check needs no trust in Zambo and no trust in Muse.
Because the receipt is a portable record in the open AER-1 format (an IETF Internet-Draft), it also travels across AIs: hand the URL to a ChatGPT, Grok, or Cursor session and that session can fetch and recompute the same record before continuing the work. Work started in Muse stays provable everywhere else, which is the whole point of cross-AI memory: state tells the next AI what to do, receipts tell it what is true.
Start free
Connecting Zambo costs nothing and the free tier receipts real work from the first call. Start with the live demo to see the artifact, then add the connector and let your next Muse job leave its own. When you want a full day of it, a Day Pass ($0.99) keeps every call receipted for 24 hours. The wider map of receipts across Claude, ChatGPT, and Grok is in receipts for work your AI did in chat.
Zambo with Muse: FAQ
How do I add Zambo to Muse?
Ask Muse, in any chat, to create a custom connector for Zambo: give it the name Zambo, the MCP endpoint https://zambo.dev/mcp, the transport (remote streamable HTTP), and the auth (none). Muse builds the connector itself, connects, and tests the tools. There is no settings form for adding a server, nothing to install, and no API key to paste, because Zambo's free tier needs none. You can review or disconnect the connector any time under Settings, then Connectors.
What do I paste into Muse?
https://zambo.dev/mcp
Paste that URL in one message asking Muse to create a custom connector for Zambo, a remote MCP server (transport: remote streamable HTTP; auth: none, no API key). That single URL is the only thing Muse needs from you; it builds the rest itself.
Can a Muse agent leave receipts for its work?
Yes, for the work it does through Zambo's tools. When your Muse agent calls a Zambo tool, the executing server captures the record at the moment of the call: the tool, a hash of the arguments, the exact result bytes committed under SHA-256, and a timestamp. The answer comes back with a receipt at a public URL. Work your Muse agent describes only in its own summary, with no tool call behind it, leaves no receipt; the receipt covers what actually ran, which is the part worth proving.
How do I verify work my Muse agent did?
Open the receipt URL from the chat. The page shows what ran, what it was given, and the exact saved result. Check it at zambo.dev/verify/, or recompute the SHA-256 commitments yourself from the bytes on the page; nothing about the check requires trusting Zambo or Muse. Because a receipt is a portable record in the open AER-1 format, you can also hand the URL to a different AI, in ChatGPT, Grok, or Cursor, and that session can fetch and recompute the same record.
Does Zambo work with the Muse connector directory?
Yes, in two ways. Today, the custom connector path works with any Muse account: ask Muse in a chat to create a custom connector for https://zambo.dev/mcp, and Zambo's tools are available in your chats, no listing required. Separately, Zambo's own submission to the Muse connector directory is currently in review. When that review completes, adding Zambo becomes a one-tap pick from the directory itself; until then, the custom connector is the same server, the same receipts, one paste away.