Zed

A context server entry in settings.json.

Kind MCP client

Transport Remote HTTP, declared as a context server.

Config settings.json (cmd-, → Open Settings)

Setup

Open settings.json and add the block below under context_servers.
Open the Agent panel and check the server is listed as running.
Use it from the Agent panel.

{
  "context_servers": {
    "unzoi": {
      "source": "custom",
      "url": "https://api.unzoi.com/mcp",
      "headers": { "x-api-key": "nai_your_key_here" }
    }
  }
}

What differs here

Zed’s MCP support has moved between releases and between the "context servers" and "agent servers" naming. Check the version you are on if the block above is rejected.
The agent panel reports server status inline, so a failed connection is visible rather than silent.
Zed prefers stdio servers in some versions; if remote HTTP is not accepted, the mcp-remote bridge works.

Next

Get a key at console.unzoi.com, if you have not.
The tool reference — what the model is reading when it chooses between the six tools.
Stories for context windows — the one habit that most changes how well an agent works against this API.
Limits — an agent that loops can spend a monthly quota faster than you expect.
Zed's own MCP documentation — authoritative for anything about the client itself, including config paths, which move.

Endpoint, for copying: https://api.unzoi.com/mcp