# Connect your AI tool

<!-- PLACEHOLDER TO CONFIRM BEFORE PUBLISHING:
  https://mcp.leadfeeder.com — confirm exact endpoint with Engineering (base vs /mcp path)
-->

Pick your AI tool below and follow its steps. Every tool connects to the same server URL and signs you in with your own Leadfeeder account.

:::info
You sign in using OAuth, so there is no API key to paste. You approve access when you connect, and you can disconnect at any time.
:::

## Set up your AI tool

<Tabs>
  <Tab title="Claude">
    Add Leadfeeder as a custom connector in Claude (Desktop or web).

    1. Go to **Customize → Connectors**.
    2. Click **Add**, then **Browse connectors**.
    3. Search for `Leadfeeder` and click on it.
    4. Click on **Connect to Claude** and sign in to Leadfeeder.
      
![image.png](https://api.eu.apidog.com/api/v1/projects/358386/resources/339614/image-preview)
    On Team and Enterprise, an Owner adds the connector once under **Organization settings → Connectors**, then each member connects.

![image.png](https://api.eu.apidog.com/api/v1/projects/358386/resources/339615/image-preview)
  </Tab>
<Tab title="Claude Code">
    Add the server from the command line, then authenticate.

```bash
claude mcp add --transport http leadfeeder https://mcp.leadfeeder.com --scope user
```

    Run `/mcp` in a session to sign in, then `claude mcp list` to confirm.
  </Tab>
    <Tab title="ChatGPT">
    Available on the web, with Developer mode enabled.

    1. Go to **Plugins**, search for `Leadfeeder`, and click the **+** sign.
![image.png](https://api.eu.apidog.com/api/v1/projects/358386/resources/339616/image-preview)
    2. Sign in with Leadfeeder, provide your Leadfeeder credentials and you are done.

On Business, Enterprise, and Edu, the Owner or Admin enables Developer Mode once, then each member adds the connector and signs in.
</Tab>
    <Tab title="Microsoft 365 Copilot">
Microsoft 365 Copilot does not add MCP servers from the chat itself. You connect Leadfeeder to a Copilot Studio agent, then use that agent in Microsoft 365 Copilot. You need access to Copilot Studio to set this up.

1. In Copilot Studio, open the agent you want to extend, or create a new one.
2. Go to the **Tools** page and select **Add a tool → New tool**.
3. Select **Model Context Protocol**.
4. Enter a **Server name** (for example, Leadfeeder), a short **Server description**, and the **Server URL** `https://mcp.leadfeeder.com/mcp` For authentication, select **OAuth** and keep the selection on **Dynamic discovery**.
5. On the **Add tool** screen, find the **Connection** row. It shows **Not connected**. Open the dropdown next to it, create a connection, and sign in to Leadfeeder to approve access. Wait until the row shows as connected.
6. Click **Add and configure**. This button stays disabled until the connection is set up.
7. Save, then publish or share the agent so your team can use it in Microsoft 365 Copilot.
        
:::note
The Leadfeeder tools can take a little time to load after you connect. If you do not see them yet (or there is an error), refresh the page until they appear.
:::
</Tab>
    <Tab title="Gemini Enterprise">

Add Leadfeeder as a custom MCP server in Gemini Enterprise. First you create an OAuth application in Leadfeeder, then you register it in Gemini.

### Step 1: Create an OAuth application in Leadfeeder

Your user needs the **OAuth Applications** right under **Company Access Rights**. If you don't see it, ask a company admin to grant it.

![1793286992563_image.png](https://api.eu.apidog.com/api/v1/projects/358386/resources/339640/image-preview)

1. Go to **Companies → Applications**.
2. Click **Create a new application** and fill in:
   - **Application Name:** `Google Gemini`
   - **Application Type:** `Internal` (preselected)
   - **Authorized redirect URLs:** `https://vertexaisearch.cloud.google.com/oauth-redirect`
   - **Scopes:** Select at least **View account details**. Select the rest based on what you want Gemini to do. You will use the same scopes in the Gemini MCP configuration.
3. Click **Save**.
4. Copy the **Client ID** and **Client Secret**.

:::warning
The client secret is shown only once. Save it in a secure place before you leave the page.
:::

### Step 2: Add the MCP server in Gemini

1. Go to [business.gemini.google](https://business.gemini.google) and click **Add MCP server**.


![1793287157042_image.png](https://api.eu.apidog.com/api/v1/projects/358386/resources/339641/image-preview)

2. On the **MCP info** step, enter:
   - **Server URL:** `https://mcp.leadfeeder.com/mcp`
   - **Name:** `Leadfeeder`

![1793287208946_image.png](https://api.eu.apidog.com/api/v1/projects/358386/resources/339642/image-preview)

3. Click **Next**.
4. On the **Auth** step, select **OAuth 2.0** as the authentication method and enter:
   - **Authorization URL:** https://api.leadfeeder.com/v1/oauth/authorize
   - **Token URL:** https://api.leadfeeder.com/v1/oauth/token
   - **Client ID:** the Client ID you copied in Step 1
   - **Client Secret:** the Client Secret you copied in Step 1
   - **Scopes:** the same scopes you selected in Step 1, separated by spaces. See the [List Accounts](https://docs.leadfeeder.com/api/public/list-accounts-4008950e0) endpoint documentation as an example.
5. Click **Add**.

### Step 3: Connect Leadfeeder

1. Go back to the chat and click the puzzle icon (connectors).
2. Search for `Leadfeeder` and click **Connect**.
![1793287733181_image.png](https://api.eu.apidog.com/api/v1/projects/358386/resources/339643/image-preview)

3. Authorize the request in the popup window.

Leadfeeder is now connected. Use the toggle next to **Leadfeeder** in the connectors list to enable or disable it for a conversation.

![1793287791570_image.png](https://api.eu.apidog.com/api/v1/projects/358386/resources/339644/image-preview)

</Tab>
    <Tab title="Perplexity">

Add Leadfeeder as a custom remote connector in Perplexity (web or desktop app).

:::highlight yellow 💡
Custom MCP connectors require a paid Perplexity plan (Pro, Max, or Enterprise). Free accounts cannot add custom connectors.
:::

1. In Perplexity, go to **Settings → Connectors**.
2. Click **+ Custom connector** and choose **Remote**.
3. Enter the Leadfeeder MCP Server details">
        - **Name:** `Leadfeeder`
        - **MCP Server URL:** `https://mcp.leadfeeder.com/mcp`
        - **Description** (optional): B2B website visitor intent, company and contact data from Leadfeeder.
        - **Authentication:** `OAuth`
4. Accept the risk acknowledgement and click **Add**.
5. When prompted, sign in to Leadfeeder and approve access. There is no API key to paste.

Actions that change data — creating or updating lists, tags, or custom fields — ask for confirmation before they run.

:::highlight blue 📌
On **Enterprise** plans, a workspace admin may need to add or approve the connector before members can use it. Adding a custom connector makes it available to your own account or workspace only — it does not list Leadfeeder in Perplexity's public connector directory.
:::

</Tab>
    <Tab title="Codex">
Add Leadfeeder as a remote MCP server in Codex. Codex connects over Streamable HTTP and signs in with OAuth, so there is no API key to paste.

1. Open **Settings → Integrations → MCP servers**.
2. Click **Add server**.
3. For the connection type, choose **Streamable HTTP**.
4. Enter a name (for example, Leadfeeder) and the server URL `https://mcp.leadfeeder.com/mcp`.
5. Save the server.
6. Click **Authenticate** on the Leadfeeder row and sign in to Leadfeeder to approve access.

Prefer the command line? Run `codex mcp add leadfeeder --url https://mcp.leadfeeder.com/mcp`, then `codex mcp login leadfeeder` to sign in. The app and CLI share the same config, so the server shows up in both.
</Tab>
  <Tab title="Cursor">
    Add the server in **Settings → Tools & MCP → New MCP Server**, or edit `~/.cursor/mcp.json`:

```json
    {
      "mcpServers": {
        "leadfeeder": {
          "url": "https://mcp.leadfeeder.com/mcp"
        }
      }
    }
```

    Save the file and connect to the Leadfeeder MCP server. Cursor will open a browser window where you can sign in to Leadfeeder.
  </Tab>
</Tabs>

## Use it in a conversation

Once connected, enable the Leadfeeder connector for the conversation, then ask in plain language. Actions that change data ask you to confirm before they run.

## Troubleshooting

<AccordionGroup>
  <Accordion title="I am asked to sign in again">
    Your session expired. Reconnect and sign in once more.
  </Accordion>
  <Accordion title="The connector does not appear on Claude (Team or Enterprise)">
    An admin has to add or approve the connector first. Ask your workspace administrator.
  </Accordion>
  <Accordion title="The connection fails">
    The server must be reachable over the public internet from your AI tool's provider, which it is by default. A private or VPN-only endpoint will not connect.
  </Accordion>
    <Accordion title="I can't find &quot;+ Custom connector&quot; in Perplexity">
Custom connectors are only available on paid Perplexity plans (Pro, Max, Enterprise). On Enterprise, your workspace admin may also need to allow custom connectors first.
</Accordion>
</AccordionGroup>