Direct answer
Add Zambo MCP to Zed
Paste https://zambo.dev/mcp into Zed's settings as a context server and reload. Open settings.json, add the Zambo entry under context_servers below, save, and the Zed Agent Panel picks it up. Zed then has Zambo: 153 tools in total, 35 on the default surface, and a checkable receipt for every tool call.
Updated October 20, 2026.
The config snippet
Open your Zed settings.json (the command palette has an open settings action). Add this block, keeping any context servers you already have:
{
"context_servers": {
"zambo": {
"url": "https://zambo.dev/mcp"
}
}
}
Zed calls MCP servers context servers, so the block name differs from other editors even though the address is the same.
Verify the connection
Save the settings, then open the Agent Panel and check the tools or context server status area. Zambo should show as connected with its tools available to the agent. If Zed reports a settings error, the problem is in the JSON structure of the file, usually a missing comma in an earlier block.
Your first tool call
In the Agent Panel, ask for something small and checkable, for example: ask it to use Zambo to look up a current price or audit a web page. 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.
For $0.99, a Day Pass covers 24 hours of full use. 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 with USDC on Base via x402.
Troubleshooting
- Zambo does not appear in the Agent Panel. Confirm the entry sits inside
context_serversin settings.json, not in a project-local file for a different folder, then restart Zed once. - Zed flags the settings file. Validate the whole file as JSON; settings files accumulate edits, and the error may be above the block you just added.
- Connected but calls fail. The value must be exactly
https://zambo.dev/mcp. If a call hits a usage limit, a Day Pass or Zambo Pass raises it.
Honest limits
MCP support in Zed runs through the Agent Panel and its context server mechanism, so Zambo tools are available to agent threads rather than to plain text editing. Zambo receipts prove the saved result of a tool call was not changed after the fact. They do 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 MCP to Zed?
Open settings.json in Zed and add a zambo entry under context_servers with url set to https://zambo.dev/mcp, then save and open the Agent Panel. Zambo then appears as a connected context server with 153 tools in total and 35 on the default surface.
Why does Zed call MCP servers context servers?
Context server is the name Zed uses for an MCP server in its settings and Agent Panel. The setup is the same idea as in other editors: one block, one name, one URL. Only the block name, context_servers, is Zed-specific.
How do I verify Zambo is connected in Zed?
Check the Agent Panel for zambo in a connected state with its tools available, then run one small call and open the receipt link in the result. Pasting that receipt ID into zambo.dev/verify and getting a match confirms the full path from Zed to a checkable record is working.
What do I get once Zambo is connected to Zed?
The Agent Panel gains Zambo tools for prices, web checks, lead work, memory, handover, and more, and every tool call returns a public receipt page. Memory saved through Zambo is stored server-side, so context saved in Zed can be recalled later in Claude, Cursor, ChatGPT, or Grok when they are connected to the same Zambo account.
How much does Zambo cost in Zed?
You can start on the free tier. A Day Pass costs $0.99 one time for 24 hours of full use. The Zambo Pass is $29 a month or $290 a year, and $19 a month for $ZAMBO holders. Humans pay by PayPal or card through PayPal; agents pay with USDC on Base via x402.