Windsurf

Cascade’s MCP config, with a header block.

Kind MCP client

Transport Remote HTTP, declared in mcp_config.json.

Config ~/.codeium/windsurf/mcp_config.json

Setup

Open Cascade → MCP servers → Configure, which opens the file.
Add the block below.
Press refresh in the MCP panel.
Ask Cascade something that needs current reporting.

{
  "mcpServers": {
    "unzoi": {
      "serverUrl": "https://api.unzoi.com/mcp",
      "headers": { "x-api-key": "nai_your_key_here" }
    }
  }
}

What differs here

Windsurf has used both `serverUrl` and `url` across versions. If the block above does not connect, try `url` — the rest of the shape is the same.
The MCP panel has an explicit refresh; use it rather than restarting the editor.
Cascade counts tool calls against its own per-conversation budget as well as your Unzoi quota, so a chatty research loop hits its ceiling before it hits yours.

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.
Windsurf's own MCP documentation — authoritative for anything about the client itself, including config paths, which move.

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