Skip to content

Cline / Roo Code / Smithery

Both Cline and Roo Code support MCP servers via the VS Code extension settings.

In your VS Code settings.json (Cmd+Shift+P → “Open User Settings (JSON)”):

{
"cline.mcpServers": {
"klozeo": {
"url": "https://mcp.klozeo.com/mcp",
"headers": { "Authorization": "Bearer sk_live_your_key" }
}
}
}

Restart VS Code. Klozeo tools appear in the Cline/Roo sidebar under MCP Tools.

Every client on this page can also connect without an API key if it supports MCP authorization: configure only the URL https://mcp.klozeo.com/mcp, without headers. The client opens Klozeo in your browser to sign in and approve access.

Browser login gives the twelve assistant tools with read access first; writing needs a separate approval in Klozeo. Keys, webhooks, scoring, attributes, deletions and batches need an API key. See Authentication.

Use the URL https://mcp.klozeo.com/mcp with browser login, or with an explicit Authorization header carrying your dashboard API key. These extension and managed-connector recipes have not been tested as part of the CLI connection checks.

Add to your Goose config (~/.config/goose/config.yaml):

mcp:
servers:
- name: klozeo
url: https://mcp.klozeo.com/mcp
headers:
Authorization: "Bearer sk_live_your_key"

Restart Goose. Run goose mcp list to verify the klozeo server appears with 38 tools.