> ## Documentation Index
> Fetch the complete documentation index at: https://docs.keebai.com/llms.txt
> Use this file to discover all available pages before exploring further.

# Other MCP apps

> Connect Cursor, VS Code, Gemini CLI or any MCP client that supports OAuth. Give it the URL; it finds the sign-in on its own.

Any MCP client that supports remote servers with OAuth can connect to Keebai with just the URL. The client discovers where to sign in from the server itself, opens your browser, and keeps the tokens.

```
https://api.keebai.com/v1/mcp
```

## Add the server

Add Keebai to the client's MCP configuration with the URL and **no `Authorization` header**. The exact file and key names belong to each client; these are the usual shapes.

```json Cursor (.cursor/mcp.json) theme={"system"}
{
  "mcpServers": {
    "keebai": {
      "url": "https://api.keebai.com/v1/mcp"
    }
  }
}
```

```json VS Code (.vscode/mcp.json) theme={"system"}
{
  "servers": {
    "keebai": {
      "type": "http",
      "url": "https://api.keebai.com/v1/mcp"
    }
  }
}
```

```json Gemini CLI (~/.gemini/settings.json) theme={"system"}
{
  "mcpServers": {
    "keebai": {
      "httpUrl": "https://api.keebai.com/v1/mcp"
    }
  }
}
```

The first time the client talks to Keebai it gets a `401` that points to the sign-in metadata. The client then opens your browser at `accounts.keebai.com`. Some clients do it on their own; others show a **Sign in** or **Authenticate** action in their MCP panel. If yours does not, check its documentation for how it handles OAuth on remote servers.

> [!NOTE]
>
> If the client has no OAuth support, connect it with a [Personal Access Token](https://docs.keebai.com/dev/mcp/overview.md#connect-with-a-personal-access-token) instead.

## What you see when you connect

**1. Sign in at accounts.keebai.com**

Sign in with your email and password, and your second factor if you have one. If you are already signed in, this step is skipped.

**2. Choose the company**

If you belong to more than one company, pick the one the app will work on. A connection always belongs to one company.

**3. Approve the permissions**

Permissions come in [six groups](https://docs.keebai.com/dev/scopes.md#permission-groups). You only see as available the groups your Keebai role allows; the company owner and superusers can grant all of them. Untick any group you do not want the app to have.

**4. Back to the app**

Click **Allow access** and the browser returns to the app, already connected.

The approval screen shows the app's name and the site it returns to. Check that both are what you expect before you click **Allow**.

## Disconnect

In the portal, go to **Developers › Connected apps** (**Desarrolladores › Apps conectadas**) and disconnect the app. The app can no longer refresh its access; the access token it already holds expires within 15 minutes. The company owner and superusers see every connection in the company; everyone else sees their own.

## Building your own client

If you are writing the client yourself, the [OAuth reference](https://docs.keebai.com/dev/mcp/oauth.md) has every endpoint, parameter and error.


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.