Goose

An extension, added by the CLI or the desktop app.

Kind MCP client

Transport Remote HTTP, declared as an extension.

Config ~/.config/goose/config.yaml

Setup

Run `goose configure` and choose to add a remote extension, or edit the config directly.
Give it the URL and your key as a header.
Start a session — `goose session` — and confirm the tools are listed.

extensions:
  unzoi:
    enabled: true
    type: streamable_http
    uri: https://api.unzoi.com/mcp
    headers:
      x-api-key: nai_your_key_here
    timeout: 30

What differs here

Goose calls MCP servers "extensions", so the MCP documentation and the Goose documentation describe the same thing in different words.
The interactive `goose configure` flow is more reliable than hand-editing, because it writes whatever shape the installed version expects.
Goose is unusually willing to chain tool calls, which makes it good at multi-step research and quick at spending quota. Watch the first few sessions.

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

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