Direct answer

Add an MCP Server to Grok

To give Grok tools, connect it to an MCP server. For Zambo, the server address is https://zambo.dev/mcp, one URL and no API key. Where the connection happens depends on where you run Grok, and this page is honest about that map: a surface or stack that accepts MCP servers, your own API or agent code, or the Receipt Bot for bot work. Every route ends at the same place: Grok doing real work, with a verifiable receipt for each routed call.

See what you are adding first: the live demo runs one real Zambo call and hands you its receipt, no signup. The endpoint you will paste is zambo.dev/mcp.

Updated October 20, 2026.

What "add an MCP server to Grok" actually means

MCP stands for Model Context Protocol: a standard way for an AI to plug in outside tools, the same way a browser plugs in extensions. Grok on its own is a strong reasoner with live flavor, but its work product is the conversation. Grok with an MCP server connected can also act: look things up at the moment of asking, run audits and checks, work with files and data, save facts for later, and produce a record of what it did that someone else can verify.

The honest complication is that "Grok" is not one surface. It lives in chat apps, in agent stacks, behind an API, and inside other people's bots, and those surfaces do not all offer the same place to paste a server address. Guides that print one universal set of clicks are guessing at your surface. The routes below are the ones that actually exist. Find yours, follow its steps, and finish with the same test either way: one small call, checked by its receipt.

The three routes, and which one is yours

Route 1: a surface or stack that accepts MCP servers. If the Grok surface you use, or the agent stack you run Grok inside, has a place for MCP servers or external tool calls, that is your route. You add the server address there, once, and new sessions can call the tools. The steps in the next section are this route.

Route 2: API or agent code. If you drive Grok through the API or from an agent harness, there is no settings screen, and there does not need to be: your code routes the tool calls to the endpoint. The load-bearing steps of the job, the lookups, audits, extractions, and checks, execute through Zambo during the run, and each result comes back with its receipt.

Route 3: bot work. If your Grok usage is a bot doing jobs, the Zambo Receipt Bot on x.ai is the surface built for it: it collects, verifies, and files a verifiable receipt for every job your bots do, then sends a short nightly digest of links. That is a separate product from the MCP route, and the distinction matters: receipts exist for work that runs through a Zambo surface, and not for work that never touches one.

Step by step: the MCP-accepting route

Step 1. Open the MCP servers or external tools settings in your Grok surface or agent stack.

Step 2. Add a new remote server.

Step 3. Paste https://zambo.dev/mcp as the server URL. Leave any API key field alone: no key is needed for this server.

Step 4. Save, and start a new session. Existing sessions can predate the server list, so a fresh session is the reliable test.

Step 5. Confirm the Zambo tools are listed before you trust the connection with real work.

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

If your surface has no step 1, you are not doing it wrong: your surface does not take custom servers, and route 2 or route 3 is your route. The endpoint, the tools, and the receipts are identical either way. What changes is only where the connection is made: in a settings screen, in your harness code, or through the bot.

Your first tool call, and how to check it

Ask for something small, current, and checkable: a current 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: current data in the result is the giveaway. 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 was not changed after the fact. If it matches, the full path works: Grok reached the server at zambo.dev/mcp, the tool ran, the result was saved, and the record can be verified by anyone, including a client who was never in the session. 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 Grok gains once it is connected

Tools. The connected session can call Zambo tools directly: 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 price, or the state of a long job once, and any AI connected to the same Zambo account can recall it later, Grok included. 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. Grok work delivered this way travels as a record, not as a thread only you can open; the full pattern is on Grok proof of work.

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.

Default surface or full surface: which URL should you paste?

The address above, https://zambo.dev/mcp, loads the default surface: 35 tools, the everyday set most sessions actually reach for, so tool choices stay fast and easy to follow. The full catalogue is one small change away: https://zambo.dev/mcp?full=true shows all 153 tools. Full makes sense on exploration days and for deliberate audits across the whole set. Keep your normal setup on the default URL and switch to full only for the session that needs a specialist tool, then switch back.

Troubleshooting: when the server does not show up

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 a Zambo surface: Grok work that never touches the endpoint or the bot 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, Grok surfaces change: if a surface adds or moves its server settings, the steps here that name the surface may age, while the endpoint, the routes, and the receipt check do not.

Frequently asked questions

How do I add an MCP server to Grok?

It depends on where you run Grok. Where your Grok surface or agent stack accepts MCP servers or external tool calls, add the Zambo endpoint, https://zambo.dev/mcp, one URL and no key, then start a new session and confirm the tools are listed. Where you drive Grok through API or agent code, route the tool calls from your harness to the same endpoint. For bot work, the Zambo Receipt Bot on x.ai files receipts for bot jobs. Every route ends the same way: run one small call and check its receipt free at https://zambo.dev/verify/.

Does every Grok surface accept custom MCP servers?

No, and any guide that pretends otherwise is guessing. Grok ships in several surfaces, and they do not all expose a place to paste a custom server. The reliable routes are the ones on this page: a Grok surface or agent stack that accepts MCP servers or external tool calls, your own API or agent code routing calls to the endpoint, or the Receipt Bot for bot work. If your surface has no server setting, that is a property of the surface, not a failure of your setup.

Do I need an API key to connect Zambo to Grok?

No API key is needed for the Zambo endpoint. The server is hosted at https://zambo.dev/mcp, so there is nothing to install, no local process to run, and no key to create, store, or rotate. You add the URL where your surface or stack takes a server address, start a fresh session, and check that the tools are listed. If a guide asks you to generate a key for this step, it is describing a different kind of server.

What can Grok do once an MCP server is connected?

Grok can call the connected tools inside the work: live lookups and current prices instead of memory, site audits, web and data checks, file work, and lead finding. Through Zambo it also gains memory you save on purpose with memory_remember and recall with memory_recall, handover links for finished work, and a verifiable receipt for every routed tool call, checkable free at https://zambo.dev/verify/ by anyone you share it with.

How much does it cost to add an MCP server to Grok this way?

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.

Related