Continue

A YAML block in the assistant config.

Kind MCP client

Transport Remote HTTP, declared in config.yaml.

Config ~/.continue/config.yaml, or .continue/ in a workspace

Setup

Open the Continue config (config.yaml).
Add the mcpServers block below.
Reload the Continue extension.
Use it from Agent mode.

mcpServers:
  - name: unzoi
    type: streamableHttp
    url: https://api.unzoi.com/mcp
    requestOptions:
      headers:
        x-api-key: ${{ secrets.UNZOI_KEY }}

What differs here

Continue supports a secrets indirection, so the config file can be committed and the key supplied separately — worth using rather than inlining.
MCP tools are available in Agent mode only.
Continue’s config format changed from JSON to YAML; a config.json example found elsewhere will not apply cleanly.

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

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