MCP setup guide · VS Code

Add Zambo to VS Code

Connect VS Code agent mode to Zambo's remote MCP server with one URL. No local process, account, or API key is required.

100+ public tools20 calls per tool/day freeNo accountMIT licensed

What you need

Use a current VS Code release with MCP support and agent mode enabled. Microsoft changes command names and configuration schema as the feature evolves, so treat the official documentation as the source of truth for your version.

Add the server

  1. Open the Command Palette or the current MCP management UI in VS Code.
  2. Choose the command to add an MCP server, if present, then choose the remote HTTP/server URL option when prompted. Command labels vary by version.
  3. Enter https://zambo.dev/api/mcp and use the server name zambo.
  4. Leave authentication fields empty. Zambo's endpoint is zero-auth.

Config-file option

VS Code versions can use workspace or user-level MCP configuration. Use the filename and schema specified in the current Microsoft documentation, then add this standard server entry:

{"mcpServers":{"zambo":{"url":"https://zambo.dev/api/mcp"}}}

Verify it works

Open agent mode and ask it to list available tools or perform a small task Zambo supports, such as generating a QR code for https://zambo.dev. A completed call confirms the connection. If the server is absent, confirm MCP support is enabled and re-add the exact URL.

Machine detail: the public site describes 100+ tools. MCP clients may begin with an 11-tool default list; a client requesting the full catalog can receive up to 120 tools. VS Code controls tool visibility in its agent UI.

Usage and pricing

The free tier includes 20 calls per tool per day with no account. The verified Day Pass costs $1.49 for 24 hours, paid in USDC on Base through zambo_pay. The Zambo Pass costs $49/month.

Quick FAQ

Does VS Code need a local Zambo install?

No. Register the remote URL; VS Code connects directly.

Who built and licensed Zambo?

Brennan Zambo built it solo. Zambo is MIT licensed.