Direct answer
Add Zambo to Lindy
Lindy connects to any hosted MCP server by URL, and Zambo is one: the server address is https://zambo.dev/mcp, one URL and no API key. Lindy's own docs put it plainly: if a product publishes an MCP server, you can hand Lindy the URL and it gains that product's tools without waiting for a native integration. Follow the five steps below, run one test call, and Lindy works with 153 tools, memory that carries across AIs, and a verifiable receipt for every routed call.
Updated October 22, 2026. Steps verified against Lindy's MCP documentation the same day.
What "add Zambo to Lindy" actually means
Lindy already ships with a large catalogue of built-in integrations. An MCP connection is different: it is how Lindy gains the tools of a product it has never integrated, on the day that product publishes them. 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. Lindy stays the teammate you talk to in Slack or iMessage. Zambo is the layer underneath that lets its work travel and be checked.
That split matters for a specific Lindy-shaped problem. Lindy's memory, threads, and work product live inside Lindy. The moment a job has to continue in a different AI, or be shown to a client, or be audited later, the record is only as strong as Lindy's own screens. Route the load-bearing calls through Zambo and each one leaves a receipt anyone can recompute, plus a handover record addressed to whoever comes next.
Step by step, from Lindy's own docs
Step 1. Go to Integrations in Lindy and click + Add.
Step 2. Choose MCP. The other option in that menu, Integration, is for the built-in tools; MCP is the route for a published server like Zambo.
Step 3. In the Connect MCP server dialog, paste https://zambo.dev/mcp as the Server URL and set the Display name to Zambo. Lindy identifies connections by hostname otherwise, and a real name beats a bare hostname in the list.
Step 4. Skip the credential. Lindy's dialog offers an Advanced section for servers that authenticate with a static credential; Zambo needs nothing there to start, so leave it empty.
Step 5. Click Connect. The server appears in your list with its host and its tool counts, and its tools arrive switched on.
Lindy's documentation states one requirement worth knowing: the server has to be reachable over public HTTPS as a streamable-HTTP endpoint. The Zambo endpoint is exactly that, hosted, with nothing to install and no local process to run. If the tool counts ever show zero available, Lindy's own troubleshooting applies: the endpoint is wrong, the catalogue is empty, or the definitions are incompatible. Check the URL character by character first; it is the usual cause.
Your first tool call, and how to check it
Ask Lindy for something small, current, and checkable through the new connection: 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: Lindy 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 Lindy. 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 Lindy 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 chat by hand. There are 153 tools in total, with 35 on the default surface.
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 Lindy. 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.
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.
Managing the tool list: everything arrives switched on
Lindy does no action-picking or field-mapping at connect time: everything the server publishes arrives switched on, and you turn off what you do not want afterwards. Open the Zambo server under Integrations and use Availability, Guardrails, and Actions to trim it, or Disable all and re-enable selectively. Guardrails are per person, Always allow or Ask for approval, so the tools that spend money or send messages can sit behind a prompt while lookups run free.
One URL choice helps here. The plain address, https://zambo.dev/mcp, loads the default surface of 35 tools, the everyday set. The full catalogue is https://zambo.dev/mcp?full=true with all 153. If you connect the full URL, expect Lindy's own warning to apply: a large server adds well over a hundred tools to the picker. Most Lindy setups are better served by the default URL plus deliberate trimming.
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. Lindy's MCP documentation states no plan-tier requirement for connecting a server.
Honest limits
Three limits, stated plainly. First, receipts exist only for work that runs through Zambo: Lindy work done through its native integrations 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, the connection starts visible only to you; sharing it with your workspace is your call inside Lindy, and the steps here follow Lindy's documentation as of October 22, 2026.
Frequently asked questions
How do I add Zambo to Lindy?
In Lindy, go to Integrations, click + Add, and choose MCP. In the Connect MCP server dialog, paste https://zambo.dev/mcp as the Server URL, set the Display name to Zambo, and click Connect. No credential is needed: leave the Advanced section alone, because Zambo accepts anonymous connections to start. Lindy reads the tools the server publishes and adds them switched on; the server appears in your list with its host and tool counts.
Does Lindy accept any MCP server, or only built-in integrations?
Any hosted MCP server. Lindy's own documentation says that if a product publishes an MCP server, you can hand Lindy the URL and it gains that product's tools without waiting for a native integration. The server has to be reachable over public HTTPS as a streamable-HTTP endpoint, which is exactly the shape of the Zambo endpoint at https://zambo.dev/mcp. Local stdio servers are not the documented route.
What does Lindy gain once Zambo is connected?
Lindy gains the Zambo tool set inside its own work: 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.
Lindy switched every Zambo tool on. Can I trim the list?
Yes. Lindy turns on everything a connected server publishes and lets you switch tools off afterwards: open the server under Integrations and use Availability, Guardrails, and Actions to disable what you do not want, or Disable all and re-enable selectively. Guardrails are per person, Always allow or Ask for approval, so you can keep sensitive tools behind a prompt. If the full catalogue feels noisy, connect https://zambo.dev/mcp?full=true only for sessions that need a specialist tool and keep the plain default URL as your everyday connection.
How much does it cost to add Zambo to Lindy?
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.