Setting up a client

All clients connect to the same endpoint:

https://api.kabeen.io/mcp

Authentication happens in the browser the first time you use the server: sign in to Kabeen and authorize the client. See Kabeen MCP server for how permissions are inherited.

Claude Code

Add the server from the terminal:

claude mcp add --transport http kabeen https://api.kabeen.io/mcp

Open a session and run /mcp to trigger authentication.

Claude (web and desktop)

• Team and Enterprise plans: open the connectors page in your workspace settings on claude.ai, then add a custom connector pointing to https://api.kabeen.io/mcp.
• Free and Pro plans: in the Claude desktop app, go to Settings → Connectors → Add custom connector and enter the same URL.

Cursor

Open Settings → MCP → Add new MCP server and use:

{
  "mcpServers": {
    "kabeen": {
      "url": "https://api.kabeen.io/mcp"
    }
  }
}

Codex

From the CLI:

codex mcp add kabeen --url https://api.kabeen.io/mcp

Or in ~/.codex/config.toml:

[features]
experimental_use_rmcp_client = true
 
[mcp_servers.kabeen]
url = "https://api.kabeen.io/mcp"

Visual Studio Code

Add the server to your MCP configuration:

{
  "mcpServers": {
    "kabeen": {
      "command": "npx",
      "args": ["-y", "mcp-remote", "https://api.kabeen.io/mcp"]
    }
  }
}

Zed

Open the settings (CMD + ,) and add:

{
  "context_servers": {
    "kabeen": {
      "source": "custom",
      "command": "npx",
      "args": ["-y", "mcp-remote", "https://api.kabeen.io/mcp"],
      "env": {}
    }
  }
}

Windsurf

Open the settings (CTRL/CMD + ,), go to Cascade → MCP servers, then add:

{
  "mcpServers": {
    "kabeen": {
      "command": "npx",
      "args": ["-y", "mcp-remote", "https://api.kabeen.io/mcp"]
    }
  }
}

Other clients

Any client that supports remote MCP servers works with the endpoint directly. For clients that only support local (stdio) servers, bridge through mcp-remote:

• Command: npx
• Arguments: -y mcp-remote https://api.kabeen.io/mcp

mcp-remote requires Node.js 18 or later.

Checking the connection

Once the client is connected, ask the assistant to run the ping tool, or simply ask a question against your data — for example "how many applications are marked as critical in my workspace?". If the answer matches what you see in the interface, the connection is working.

If a client fails to connect or the tools do not appear, see Troubleshooting.