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

# MCP server setup

> Connect Claap to Claude, ChatGPT, Cursor and other AI assistants

The Claap MCP server lets AI assistants that support the [Model Context Protocol](https://modelcontextprotocol.io) work directly with your Claap data: meeting recordings and transcripts, deals, companies, contacts, emails, views and fields.

Once connected, you can ask things like:

* "Summarize my last call with Acme and list the next steps"
* "Which deals in the Negotiation stage had no call in the last 2 weeks?"
* "Search all transcripts from this month where a prospect mentioned Gong"
* "Prepare a briefing for my meeting with Jane Doe tomorrow"

# Server URL

```
https://api.claap.io/mcp
```

The server uses the Streamable HTTP transport. There is nothing to install locally.

# Authentication

<CardGroup cols={2}>
  <Card title="OAuth (recommended)" icon="user-check">
    Sign in with your Claap account in the browser. No key to create or store. Access matches what you can see in Claap.
  </Card>

  <Card title="API key" icon="key">
    For clients without OAuth support, or for automations. A key is created by a workspace admin and is bound to one workspace.
  </Card>
</CardGroup>

## OAuth

Add the server URL to your client: it will open a Claap consent page in your browser. Click **Authorize** and you are done.

* The connection gives access to every workspace where you are a Member or Admin. Guests cannot use the MCP server.
* The assistant sees the same recordings, folders and views as you do in Claap, and can only do what your role allows.
* Access tokens are refreshed automatically. You can disconnect at any time from your AI client.

## API key

Workspace admins can create an API key in Claap, under **Settings > API & Webhooks**. See [Authentication](/api-reference/authentication).

Pass it as a bearer token:

```
Authorization: Bearer cla_xxxxx
```

<Warning>
  The MCP server uses the `Authorization: Bearer` header, not the `X-Claap-Key` header used by the REST API.
</Warning>

<Note>
  An API key acts as a workspace admin and only gives access to its own workspace. Private recordings are only visible if the key was created with **Full access**. Anyone holding the key gets this access, so treat it like a password.
</Note>

# Setup by client

<Tabs>
  <Tab title="Claude">
    Works in Claude.ai and Claude Desktop, on Pro, Max, Team and Enterprise plans.

    <Steps>
      <Step title="Add the connector">
        Go to **Settings > Connectors**, click **Add custom connector**.
      </Step>

      <Step title="Configure it">
        Name: `Claap`. URL: `https://api.claap.io/mcp`. Click **Add**.
      </Step>

      <Step title="Connect">
        Click **Connect**, then **Authorize** on the Claap page that opens.
      </Step>
    </Steps>

    <Note>
      On Team and Enterprise plans, an owner must first add the connector in **Admin settings > Connectors**. Members then connect it from their own settings.
    </Note>
  </Tab>

  <Tab title="Claude Code">
    ```bash theme={null}
    claude mcp add --transport http claap https://api.claap.io/mcp
    ```

    Then run `/mcp` in Claude Code, select `claap` and follow the browser sign-in.

    With an API key instead:

    ```bash theme={null}
    claude mcp add --transport http claap https://api.claap.io/mcp \
      --header "Authorization: Bearer cla_xxxxx"
    ```
  </Tab>

  <Tab title="ChatGPT">
    Custom connectors require a plan and workspace settings that allow them (Plus, Pro, Business, Enterprise or Edu).

    <Steps>
      <Step title="Enable developer mode">
        Go to **Settings > Apps & Connectors > Advanced settings** and enable **Developer mode**.
      </Step>

      <Step title="Create the connector">
        Back in **Apps & Connectors**, click **Create**. Name: `Claap`. URL: `https://api.claap.io/mcp`. Authentication: **OAuth**.
      </Step>

      <Step title="Connect">
        Authorize on the Claap page that opens, then enable Claap in a new chat.
      </Step>
    </Steps>
  </Tab>

  <Tab title="Cursor">
    Add Claap to `~/.cursor/mcp.json` (all projects) or `.cursor/mcp.json` (one project):

    ```json theme={null}
    {
      "mcpServers": {
        "claap": {
          "url": "https://api.claap.io/mcp"
        }
      }
    }
    ```

    Then open **Cursor Settings > MCP** and click **Login** next to `claap`.

    With an API key instead:

    ```json theme={null}
    {
      "mcpServers": {
        "claap": {
          "url": "https://api.claap.io/mcp",
          "headers": {
            "Authorization": "Bearer cla_xxxxx"
          }
        }
      }
    }
    ```
  </Tab>

  <Tab title="VS Code">
    Add Claap to `.vscode/mcp.json`:

    ```json theme={null}
    {
      "servers": {
        "claap": {
          "type": "http",
          "url": "https://api.claap.io/mcp"
        }
      }
    }
    ```

    Click **Start** above the server entry and sign in when prompted.
  </Tab>

  <Tab title="Other clients">
    Any MCP client that supports remote servers over Streamable HTTP can connect:

    * **URL:** `https://api.claap.io/mcp`
    * **OAuth:** discovered automatically from `https://api.claap.io/.well-known/oauth-authorization-server`, with dynamic client registration and PKCE.
    * **Or header:** `Authorization: Bearer cla_xxxxx`
  </Tab>
</Tabs>

# Workspaces

Every request targets a single workspace. If you belong to several workspaces, the assistant asks which one to use, then keeps using it for the rest of the conversation. You can switch at any time by naming another workspace.

# What the assistant can do

The assistant can search and read your recordings, transcripts, deals, companies, contacts and emails, chart them, and manage views, AI fields, folders, contacts, users and admin automations. Write actions follow your Claap permissions.

<Card title="Available tools" icon="wrench" href="/mcp/tools">
  The full list of tools and ready-made prompts exposed by the Claap MCP server.
</Card>

# Troubleshooting

<AccordionGroup>
  <Accordion title="401 Unauthorized">
    Your OAuth session was revoked or your API key was deleted. Reconnect from your AI client, or ask an admin for a new key. Make sure the key is sent as `Authorization: Bearer`, not `X-Claap-Key`.
  </Accordion>

  <Accordion title="A workspace is missing">
    OAuth only gives access to workspaces where you are a Member or Admin, not a Guest. An API key only gives access to the workspace it was created in.
  </Accordion>

  <Accordion title="Search returns nothing">
    Check which workspace the assistant searched and ask it to try another one. With an API key, private recordings are only visible if the key has **Full access**.
  </Accordion>
</AccordionGroup>

Need help? Contact [support@claap.io](mailto:support@claap.io).