Troubleshooting the MCP connection

The client returns an error on connection

Most connection errors come from a stale authentication cache left by mcp-remote. Clear it and reconnect:

rm -rf ~/.mcp-auth

If the error persists, check that your Node.js version is 18 or later — older versions cannot complete the OAuth flow.

The tools do not appear in the assistant

The client connected but did not load the tool list. Disconnect the server from your client's MCP settings, then reconnect it. In Claude Code, run /mcp and reconnect from there.

The connection drops after a while

Remote MCP sessions expire. Disconnect and reconnect the server from the client's MCP settings to open a fresh session.

The assistant does not see all my data

The MCP session inherits the permissions of the account you authenticated with. If applications, costs or teams are missing, check your role in the Roles and permissions guide — an assistant can never see more than you do in the interface.

I need to connect several Kabeen workspaces

Reconnecting alone does not switch the workspace inside an existing authentication session. For clients bridged through mcp-remote, give each workspace its own configuration directory:

MCP_REMOTE_CONFIG_DIR=~/.mcp-auth/kabeen-workspace-a npx -y mcp-remote https://api.kabeen.io/mcp

Declare one server entry per workspace, each with its own directory.

WSL on Windows

Running the bridge through WSL requires invoking it explicitly:

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

Revoking a client

Open your Kabeen account settings and revoke the authorization granted to the client. Access is cut immediately; the client will ask you to authenticate again on its next connection.

Still stuck?

Contact your Kabeen representative with the name and version of your client, and the exact error message returned on connection.