unlob Docs
Console
Browse documentation

Cline and Windsurf

Two editors, one config shape, one file each.

Cline

Open the MCP Servers panel from the Cline sidebar and edit the configuration — that opens cline_mcp_settings.json, whose location depends on your editor and platform, which is why going through the UI is easier than finding it.

{
  "mcpServers": {
    "unlob": {
      "type": "streamableHttp",
      "url": "https://api.unlob.com/mcp",
      "headers": { "x-api-key": "ulb_…" }
    }
  }
}

If your build does not recognise the remote form, use the bridge below.

Windsurf

~/.codeium/windsurf/mcp_config.json, reachable from Settings → Cascade → MCP Servers.

{
  "mcpServers": {
    "unlob": {
      "serverUrl": "https://api.unlob.com/mcp",
      "headers": { "x-api-key": "ulb_…" }
    }
  }
}

Windsurf has used serverUrl where most clients use url. If the server never appears, that key name is the first thing to check.

The bridge, for either

Works regardless of what the build supports:

{
  "mcpServers": {
    "unlob": {
      "command": "npx",
      "args": ["-y", "mcp-remote", "https://api.unlob.com/mcp",
               "--header", "x-api-key:ulb_…"]
    }
  }
}

No space after the colon.

Both

Reload the window after editing, then check the server lists eleven tools. Neither editor is loud about a failed handshake — an empty tool list is what you will see, so Troubleshooting is the next stop rather than the config file.

These two move quickly. Where this page and their own documentation disagree, believe theirs, and the Inspector will tell you whether the problem is the client or the server.

Next