> ## 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. # Connect with Claude > Add Keebai as a custom connector in Claude or as a remote MCP server in Claude Code. You sign in with your Keebai account — no token to copy. Claude connects to Keebai over OAuth. You paste one URL, sign in to Keebai in your browser, pick the company, and approve what Claude can do. There is no API key to create or paste. ``` https://api.keebai.com/v1/mcp ``` ## Claude on the web and Claude Desktop **1. Open the connectors settings** Go to **Customize › Connectors**. **2. Add a custom connector** Click **+ Add**, then **Add custom connector**. **3. Name it and paste the URL** Name it `Keebai` and enter `https://api.keebai.com/v1/mcp` as the remote MCP server URL. Click **Continue**. **4. Keep OAuth as the authentication** Claude detects that Keebai uses OAuth. Leave the detected settings as they are — do not add request headers. Choose **Sign in now** to connect right away, or **Sign in when needed**, and click **Add**. **5. Sign in to Keebai** A Keebai window opens. Sign in, choose the company, and approve the permissions. See [What you see when you connect](#what-you-see-when-you-connect). To use it in a conversation, click **+** at the lower left of the chat, open **Connectors**, and turn Keebai on. Custom connectors are available in Claude Desktop too; follow the same steps. If your version of the app shows the settings somewhere else, look for the connectors section and follow the same flow. > [!NOTE] > > **Team and Enterprise plans.** An owner adds the connector once for the whole organization, under **Organization settings › Connectors** (**Add › Custom › Web**, then the same steps). Each member then opens **Customize › Connectors**, finds Keebai and clicks **Connect** to sign in with their own Keebai account. Every member gets their own connection, limited by their own Keebai role. Anthropic's reference for these screens: [Getting started with custom connectors using remote MCP](https://support.claude.com/en/articles/11175166-getting-started-with-custom-connectors-using-remote-mcp). ## Claude Code **1. Add the server** ```bash theme={"system"} claude mcp add --transport http keebai https://api.keebai.com/v1/mcp ``` Add `--scope user` to make it available in all your projects, or `--scope project` to share it with your team through `.mcp.json`. Each person still signs in with their own account. **2. Sign in** Inside Claude Code, run: ```text theme={"system"} /mcp ``` Pick `keebai` and follow the steps in your browser. From your shell, `claude mcp login keebai` does the same. Claude Code stores the tokens and refreshes them on its own. Anthropic's reference: [Connect Claude Code to tools via MCP](https://code.claude.com/docs/en/mcp). ## What you see when you connect **1. Sign in at accounts.keebai.com** The browser opens `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 Claude will work on. A connection always belongs to one company. To use another one, connect again and choose it. **3. Approve the permissions** Permissions come in [six groups](https://docs.keebai.com/dev/scopes.md#permission-groups) — messages and email, customers, calendar, products and sales, sell and invoice, agents and knowledge. 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 Claude to have. **4. Back to Claude** Click **Allow access** and the browser returns to Claude, already connected. If you cancel, nothing is created. The approval screen is valid for 10 minutes. If it expires, start the connection again from Claude. Every [tool](https://docs.keebai.com/dev/mcp/tools.md) stays visible to Claude, but a tool whose group you did not approve fails with `INSUFFICIENT_SCOPE`. See [how scopes are enforced](https://docs.keebai.com/dev/mcp/overview.md#scopes-are-enforced-per-tool-not-per-connection). ## Disconnect You can cut the connection from either side. * **From Keebai** — in the portal, go to **Developers › Connected apps** (**Desarrolladores › Apps conectadas**) and disconnect Claude. Claude can no longer refresh its access, so it has to sign in again; the access token it already holds keeps working until it expires, at most 15 minutes later. The company owner and superusers see every connection in the company; everyone else sees their own. * **From Claude** — go to **Customize › Connectors**, click **Remove** or the three dots next to Keebai, and follow the prompts. * **From Claude Code** — run `claude mcp logout keebai` before `claude mcp remove keebai`. Removing the server on its own only deletes the tokens on your machine; it does not end the connection in Keebai. You can always disconnect it from **Developers › Connected apps**. > [!TIP] > > To change which groups Claude has, connect again and approve a different set. The new approval replaces the old one for that company. ## Next steps > [card] [Tool catalogue](https://docs.keebai.com/dev/mcp/tools.md) > > Every tool and the scope it needs. > [card] [Permission groups](https://docs.keebai.com/dev/scopes.md#permission-groups) > > Which scopes each group grants. This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.