Connect a client

One endpoint, one key, and the client never learns your upstream credentials. Bridge is a standard MCP server, so any MCP client that speaks Streamable HTTP works; the guides below cover a few popular ones.

The same URL and Bearer key work with any MCP client, including Windsurf, Cline, Zed, and custom clients built on the MCP SDK.

The key above acts as your workspace, so every call goes upstream as you. To have an agent act as each of your users instead, see Act on behalf of your users.

01Issue a key

Scope it to the one server this client should reach. Keys are shown once.

console

API keys → Issue key
  label   Claude · Dana
  server  Northbeam Ads
  policy  operator-write

02Add the server to your config

Restart Claude Desktop afterwards. Tools appear under the server name you set in Bridge.

claude_desktop_config.json

{
  "mcpServers": {
    "northbeam-ads": {
      "url": "https://api.kaiv.ai/api/bridge/mcp/northbeam-ads",
      "headers": {
        "Authorization": "Bearer kv_live_7Qm2..."
      }
    }
  }
}

03Confirm the connection

The first call reaches the audit log within a second, with key and policy attached.

console

Audit → filter key:kv_live_7Qm2
  18:04:11  list_campaigns  allow  212ms

troubleshooting

401 invalid_keyThe key was revoked or belongs to another organization. Issue a new one and restart the client.

403 tool_not_exposedThe tool exists upstream but is hidden in Bridge. Expose it under Server → Tools, then publish.

Tools do not appearClaude Desktop caches the server list. Quit fully and reopen rather than reloading the window.