Direct answer
Add Zambo to Manus
Manus accepts custom MCP servers by URL, and Zambo is one: add https://zambo.dev/mcp under Settings, Integrations, Custom MCP Servers, and Manus gains 153 tools, memory that carries across AIs, and a verifiable receipt for every routed call. The steps below follow Manus's own documentation, including the second documented entry through its Connectors page, and they end the way every connection on this hub ends: one small call, checked by its receipt.
Updated October 22, 2026. Steps verified against Manus's custom MCP documentation the same day.
What "add Zambo to Manus" actually means
Manus is a worker: you hand it a job, it runs in its own sandbox, and it returns finished work with a session you can replay. A custom MCP server is how that worker gains tools its makers did not build in. Zambo is the verifiable work layer for AI: one MCP endpoint carrying 153 tools, continuity that carries a job across different AIs, and an AER-1 verifiable receipt for every call that runs. Manus stays the agent doing the job. Zambo is the layer that lets parts of the job be checked by people who were never in the session, and continued by AIs that are not Manus.
That distinction is the honest reason to connect them. Manus replay is genuinely good transparency, and it lives where the work happened: inside Manus, behind your login. A client, a teammate on a different stack, or the next AI in a chain cannot open it. Work routed through Zambo leaves a record addressed to those people instead: a receipt anyone can recompute, and a handover link that carries the job onward.
Step by step, from Manus's own docs
Step 1. In Manus, navigate to Settings, then Integrations, then Custom MCP Servers.
Step 2. Click Add Server.
Step 3. Enter the server name: Zambo. Enter the server URL: https://zambo.dev/mcp. Manus's documentation asks that a custom server be hosted and accessible via HTTPS, which the Zambo endpoint is.
Step 4. Leave the authentication field empty. The form accepts an API key or bearer credential for servers that require one; Zambo requires none to start, and a credential you do not need is a credential you do not paste.
Step 5. Save, and let Manus run its Test Connection: it verifies it can communicate with the server and retrieves the list of available tools.
Step 6. Once connected, the tools appear in Manus's available integrations. Reference them in prompts just like the prebuilt connectors, and run the test call in the next section before trusting the connection with real work.
The second documented entry. Manus's connectors page describes the same add from a different door: open Connectors, choose Create, then Add MCP by URL, and enter a name and the server URL. If your build of Manus shows the Connectors surface first, that path is documented too; it lands in the same place. What neither page documents is a plan-tier requirement for custom MCP servers, so this page claims none.
Your first tool call, and how to check it
Ask Manus to use Zambo for something small, current, and checkable: a live price you can compare against a source you trust, or an audit of a page you own. Watch for two things. First, the answer should come from a tool call, not from the model answering from memory. Second, the result should carry a receipt link, the record of that call.
Open the receipt, then run the free check on it at zambo.dev/verify, with no signup. The check confirms the saved result has not changed since it was saved. If it matches, the full path works: Manus reached the server, the tool ran, the result was saved, and the record can be verified by anyone, including a client who has never opened Manus. Before connecting at all, you can watch the same loop with zero setup: the live demo runs one real call and hands you its receipt in about 10 seconds.
What Manus gains once it is connected
Tools. Live lookups and current prices instead of training-data guesses, site audits, web and data checks, document and file work, lead finding with the leadsignal tool, and the everyday jobs that used to mean pasting results into the session by hand. There are 153 tools in total, with 35 on the default surface. The full catalogue loads as https://zambo.dev/mcp?full=true if a session needs a specialist tool.
Memory. Zambo memory holds only facts you explicitly save, through memory_remember, and brings them back through memory_recall. Save a project rule, a client preference, or the state of a long job once, and any AI connected to the same Zambo account can recall it later, not just Manus. The store does not import your conversations and it does not guess.
Handover. When a job is finished, package it as a handover: one link carrying the goal, the steps in order, the outputs, and any open items. The receiver opens it with no account and clicks Accept or Flag. You cannot accept your own handover, which is exactly what makes the acceptance on it worth showing later. This is the piece replay cannot do: it moves the job, with its record, to a different AI or a human who was never in Manus.
Receipts. Every routed tool call returns a verifiable receipt for its saved result, in the AER-1 format (IETF Internet-Draft draft-zambo-aer1-24). Anyone can check a receipt free at zambo.dev/verify. The check proves what ran and what came back, unaltered. It does not prove the result was right, and this page will not pretend otherwise.
What it costs
Connecting costs nothing to set up, and checking a receipt is always free. When the connection becomes part of a real working day, a Day Pass at $0.99 covers 24 hours of full access: enough to connect in the morning, run real jobs through the day, save the facts that matter, and hand the finished work over with its record attached. Ongoing use is the Zambo Pass at $29 a month or $290 a year, and $19 a month for $ZAMBO holders. Humans pay by PayPal or card through PayPal; agents pay USDC on Base through x402.
Honest limits
Three limits, stated plainly. First, receipts exist only for work that runs through Zambo: Manus work done entirely inside its own sandbox and native connectors leaves no Zambo record, and an honest delivery lists that work as unchecked rather than pretending it is covered. Second, a verifiable receipt proves a saved result was not changed after the fact; it never proves the answer was right, so your review remains the quality gate. Third, Manus documents two add paths and no plan tier for custom servers as of October 22, 2026; if its surfaces change, the endpoint, the routes, and the receipt check do not.
Frequently asked questions
How do I add Zambo to Manus?
In Manus, navigate to Settings, then Integrations, then Custom MCP Servers, and click Add Server. Enter Zambo as the server name and https://zambo.dev/mcp as the server URL, and leave the authentication field empty, because Zambo needs no credential to start. Manus then runs a Test Connection, verifies it can communicate with the server, and retrieves the list of available tools. Once connected, the tools appear in Manus's available integrations, and you reference them in prompts just like the prebuilt connectors.
Manus shows me a Connectors page instead of Custom MCP Servers. Which path is right?
Both are documented by Manus, and they reach the same result. The documentation path is Settings, Integrations, Custom MCP Servers, Add Server. The connectors page describes a second entry: open Connectors, choose Create, then Add MCP by URL, and enter a name and the server URL, https://zambo.dev/mcp. Builds differ in which surface they show first. Use the one your Manus shows you, and judge the result the same way either route ends: the server connected, its tools listed, and one test call checked by its receipt.
What does Manus gain once Zambo is connected?
Manus gains the Zambo tool set inside its own sessions: 153 tools in total, 35 on the default surface, covering live lookups and prices, site audits, web and data checks, file work, and lead finding. It also gains memory you save on purpose with memory_remember and recall with memory_recall, handover links that carry a finished job to another AI or a client, and a verifiable AER-1 receipt for every routed call, checkable free at https://zambo.dev/verify/ by anyone you share it with, including people who never open Manus.
Does Manus replay not cover this already?
Replay and a receipt answer different questions. Manus replay lets you roll back a session timeline inside Manus and watch each step, which is the best in-product transparency in its class. A verifiable AER-1 receipt is a record that leaves the product: anyone can recompute it at https://zambo.dev/verify/ with no Manus account, and it can travel inside a handover to a different AI or a client. Replay is how you review work while it stays home. The receipt is how the work stays checkable after it leaves.
How much does it cost to add Zambo to Manus?
Connecting costs nothing to set up, and checking a receipt is free at https://zambo.dev/verify/ with no signup. For $0.99, a Day Pass covers 24 hours of full access, enough to connect in the morning and run a full day of real work through it. Ongoing use is the Zambo Pass at $29 a month or $290 a year, and $19 a month for $ZAMBO holders. Humans pay by PayPal or card through PayPal; agents pay USDC on Base through x402.