Direct answer

Add Zambo to Gemini

To give Gemini tools it can prove, connect it to the Zambo MCP at https://zambo.dev/mcp. The working routes are Gemini CLI and Gemini agent stacks that accept MCP servers; the endpoint is one URL, no API key, and every routed tool call files a verifiable receipt as it runs. This page walks the connection, the first checked call, and how Gemini work gets delivered with its record attached.

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 20, 2026.

The routes that actually exist

Gemini CLI. Google's terminal agent reads MCP servers from a settings file, and it is the route most people mean by "connect MCP to Gemini". One config entry, a restart, and Gemini CLI sessions have the tools. The deep walkthrough, with verification and troubleshooting, is on add Zambo MCP to Gemini CLI; the short version is the next section.

Gemini inside an agent stack or editor setup. Where a stack or editor surface running Gemini accepts MCP servers, the same endpoint goes into that surface's server settings. The address does not change, and neither do the receipts: any routed call files one.

API-driven Gemini work. If you call Gemini from your own code, your harness routes the tool calls: the load-bearing steps, lookups, audits, extractions, execute through the endpoint during the run, and each result returns with its receipt attached.

What is not a route: the Gemini chat app itself. It has no field for a custom MCP server, and this page will not invent one. If your Gemini use is the app, the honest way to give that work tools and proof is to run the work sessions in Gemini CLI or a connected stack, and keep the app for conversation.

The connection, short version (Gemini CLI)

Step 1. Open settings.json in your Gemini config folder, usually ~/.gemini/settings.json. For a project-only setup, the same block works in the project's .gemini/settings.json.

Step 2. Add the Zambo entry under mcpServers, keeping any servers you already have:

{
  "mcpServers": {
    "zambo": {
      "httpUrl": "https://zambo.dev/mcp"
    }
  }
}

Note the field name: for a remote HTTP server, Gemini CLI uses httpUrl. There is no command to add, because Zambo is hosted, not run locally.

Step 3. Save, and start a new Gemini CLI session. Settings are read at session start.

Step 4. Verify inside the session with its MCP listing command (the /mcp command): Zambo should show as connected with its tools discovered. If the list is empty, the CLI is reading a different settings file than the one you edited.

Step 5. Run the first test call in the next section, and check its receipt.

Your first tool call, and how to check it

Ask Gemini to use Zambo for something small and checkable: look up a current price, or audit a web page you own. The answer comes back with a receipt link. Open the receipt page, then paste its ID into zambo.dev/verify: the check confirms the saved result was not changed after the fact. That one loop, Gemini to endpoint to receipt to public check, is the whole product in miniature. If it works on the small call, it works on the real ones, and you can stop wondering whether the connection took.

What Gemini gains once Zambo is connected

Tools. 153 tools in total, 35 on the default surface: live prices instead of training data, web and data checks, site audits, document and file work, lead finding with the leadsignal tool, and the everyday jobs that used to mean copying results between tabs by hand. Ask in plain words; the client picks the tool; you judge the result the way you would judge any work product.

Memory that crosses clients. Zambo memory holds only facts you explicitly save, through memory_remember, and returns them through memory_recall. Because the store is server-side, a fact saved in a Gemini CLI session can be recalled later in Claude, Cursor, ChatGPT, or Grok connected to the same Zambo account. Gemini becomes one doorway into a memory the others share, instead of another silo.

Receipts for Gemini work. Every routed call files a verifiable receipt in the AER-1 format (IETF Internet-Draft draft-zambo-aer1-24), naming the tool, the time, and the saved result. That record is what the searches for a Gemini receipt or Gemini proof of work are really asking for: not a badge, a record a stranger can recompute free at the verifier. The delivery pattern built on it is on Gemini proof of work.

Handover. A finished Gemini job packages as a handover: one link with the goal, the steps in order, the outputs, the receipts, and any open items. The receiver opens it with no account and clicks Accept or Flag, and only the receiver can record that acceptance.

Troubleshooting: when Zambo does not show up

The MCP list is empty. Confirm the field is httpUrl, not url, and restart the CLI; settings are read at session start. Then confirm you edited the settings file the CLI is actually reading: user settings and project settings are different files.
The settings file will not parse. Validate the whole file as JSON. One broken earlier block stops every server from loading, including the new one.
Tools discovered but calls fail. The value must be exactly https://zambo.dev/mcp. Check for added paths, spaces, or a pasted ?full=true you did not mean to add (that variant is valid; it just loads all 153 tools).
A call hits a usage limit. Checking receipts stays free at https://zambo.dev/verify/. A Day Pass or Zambo Pass raises the working limits; see the cost section below.

What it costs

You can start on the free tier, and checking a receipt is always free. A Day Pass costs $0.99 one time for 24 hours of full access: connect in the morning, run a day of Gemini work through real tools, and deliver it with the 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, a settings entry in the user folder applies to every Gemini CLI session on that machine; a project settings entry applies only inside that project, so pick the scope you actually want. Second, receipts exist only for steps that ran through Zambo: Gemini work done entirely outside the routed calls has no receipt, and an honest delivery lists it as unchecked. Third, a verifiable receipt proves the saved result of a tool call was not changed after the fact; it does 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 to Gemini?

The working route today is Gemini CLI or a Gemini agent stack that accepts MCP servers. In Gemini CLI, open settings.json in your Gemini config folder, usually ~/.gemini/settings.json, and add a zambo entry under mcpServers with httpUrl set to https://zambo.dev/mcp. Save and start a new session, then check the MCP list in the session to confirm Zambo is connected with its tools discovered. The full walkthrough is on the Gemini CLI page linked from this one.

Can the Gemini chat app itself connect to an MCP server?

The Gemini chat app does not take custom MCP servers: there is no settings field in the app where a server address goes. The routes that work are Gemini CLI, Gemini inside an agent stack or editor setup that accepts MCP servers, and API-driven Gemini work where your own code routes the tool calls to the endpoint. Anyone selling you an app-side paste for this is guessing. The endpoint and the receipts are the same on every real route.

Why does the Gemini config use httpUrl instead of url?

Gemini CLI uses httpUrl for a remote MCP server reached over HTTP. Other clients use url or serverUrl for the same idea under different names. Using the wrong field name is the most common reason a saved config produces no server at all: the file loads, the entry is ignored, and the MCP list stays empty. Keep the address itself exactly https://zambo.dev/mcp and the field name exactly httpUrl.

What does Gemini get once Zambo is connected?

Gemini gains Zambo tools for live prices, web checks, site audits, lead work, file work, memory, and handover: 153 tools in total, 35 on the default surface. Every routed tool call returns a verifiable receipt, checkable free at https://zambo.dev/verify/. Memory saved through Zambo is stored server-side, so a fact saved in a Gemini session can be recalled later in Claude, Cursor, ChatGPT, or Grok when they are connected to the same Zambo account.

How much does it cost to add Zambo to Gemini?

You can start on the free tier, and checking a receipt is always free at https://zambo.dev/verify/ with no signup. A Day Pass costs $0.99 one time for 24 hours of full access. 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.