> For the complete documentation index, see [llms.txt](https://docs.leadbay.app/doc/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.leadbay.app/doc/leadbay-mcp/installation.md).

# Installation

Pick your client below. Each takes a couple of minutes and **none of them need an API token** — you add a server URL, sign in once with your Leadbay account in the browser, and you're connected.

There are **two server URLs** — pick the one that matches the Leadbay instance your account is on:

| Region            | Server URL                       |
| ----------------- | -------------------------------- |
| 🇺🇸 US (default) | `https://mcp.leadbay.app/mcp`    |
| 🇫🇷 France / EU  | `https://mcp.leadbay.app/fr/mcp` |

The steps below show the US URL — French users just swap in `/fr/mcp`.

You need a [Leadbay account](https://leadbay.ai/) (the same login as the web app) and one of the assistants below.

***

## Claude.ai (web)

Add Leadbay as a **custom connector**.

1. [**Add the Leadbay connector →**](https://claude.ai/customize/connectors?modal=add-custom-connector\&connectorName=Leadbay\&connectorUrl=https%3A%2F%2Fmcp.leadbay.app%2Fmcp) — the form opens with the name and URL prefilled. Leave the Advanced settings as they are, then click **Add**.
2. Open the **Leadbay** connector in the directory (search "Leadbay" under **Custom connectors**), click **Connect**, and sign in.

The Leadbay tools become available in your chats. You can scope them per-project in Claude Projects.

> **Not an org admin?** Members can't add a custom connector — your workspace admin adds it once (step 1), then you **Connect** (step 2). See [Admin setup](/doc/leadbay-mcp/admin-setup.md). Custom connectors require a paid Claude plan (Pro, Max, Team, or Enterprise).

***

## Claude Desktop

Same **custom connector** as Claude.ai, same URL.

1. **Settings → Connectors → + → Add custom connector**
2. **Name:** `Leadbay` · **URL:** `https://mcp.leadbay.app/mcp` → click **Add**
3. Open the **Leadbay** connector, click **Connect**, sign in.

If your first message gets *"I don't see any Leadbay tools"*, the tools are still loading — send any second message and Claude picks them up. Not an org admin? The admin adds the connector first (see [Admin setup](/doc/leadbay-mcp/admin-setup.md)), or use the extension fallback below.

### Fallback: install the extension

No **Add custom connector** option, or not an org admin? Skip the connector and install Leadbay as a **`.dxt` extension** — a per-user double-click install with no admin gate.

1. [**⬇ Download the Leadbay extension (.dxt)**](https://github.com/leadbay/mcp/releases/latest/download/leadbay-latest.dxt)
2. Double-click it → **Install** → toggle to **Enabled**.
3. Open a new chat, click **Connect** on the extension, sign in.

Double-click didn't open Claude? Install from inside the app: **Settings → Extensions → Advanced → Install extension**, then pick the downloaded `.dxt`. On a new release, download and install again — Claude replaces it in place and your sign-in carries over.

***

## Claude Code

One command registers Leadbay for every project:

```bash
claude mcp add --scope user --transport http leadbay https://mcp.leadbay.app/mcp
```

1. Run `/mcp` inside Claude Code.
2. Select **leadbay → Authenticate** — your browser opens for sign-in.
3. Log in and approve. The status flips to **connected** and the tools load.

Ran `add` in an open session? Restart it once so the server shows up in `/mcp`. Remove it anytime with `claude mcp remove leadbay -s user`.

***

## Codex

Codex has a built-in command for remote MCP servers:

```bash
codex mcp add leadbay --url https://mcp.leadbay.app/mcp
```

Codex detects OAuth automatically and opens your browser for the **Sign in with Leadbay** flow — log in and approve. Confirm with `codex mcp list` (you should see `leadbay` with **Status: enabled**, **Auth: OAuth**). Remove it with `codex mcp remove leadbay`.

***

## ChatGPT

Add Leadbay as a custom plugin connection (MCP connector).

1. Enable developer mode: open **Settings → Security and Login**, scroll to the bottom, and turn on **Developer mode**.
2. Open **Plugins** in ChatGPT.
3. Click **+** to add a new connection.
4. **Name:** `Leadbay`
5. **Connection URL:** use the URL for your Leadbay workspace:
   * US: `https://mcp.leadbay.app/mcp`
   * France / EU: `https://mcp.leadbay.app/fr/mcp`
6. Click **Connect**, then sign in with your Leadbay account and approve.

In a chat, enable **Leadbay** from the composer **+** / plugin menu so ChatGPT can call its tools.

> Custom MCP connectors require a paid ChatGPT plan (Plus, Pro, Business, or Enterprise). On Business/Enterprise an admin may need to allow custom plugins/connectors first. If Leadbay disconnects, open **Plugins**, select **Leadbay**, and reconnect.

***

## After you connect — your first leads

Whichever client you used, open a new conversation and try:

> *Show me today's leads and tell me which two are worth opening first.*

A successful reply is a **ranked shortlist** — each lead with a fit score, a one-line "why it fits", and the best contact. If you see that, you're fully connected. 🎉

{% content-ref url="/pages/alp1pPMtNOaF49Nro0F4" %}
[Example prompts](/doc/leadbay-mcp/example-prompts.md)
{% endcontent-ref %}

***

## Troubleshooting

| Symptom                                                                       | Fix                                                                                                                                                                                                                                                                                 |
| ----------------------------------------------------------------------------- | ----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| "Not authenticated" / 401 errors                                              | Your sign-in expired or was revoked. Trigger any Leadbay tool again and approve the **Sign in with Leadbay** prompt.                                                                                                                                                                |
| Connected, but "show me leads" returns an empty list                          | You're signed in fine — there's just nothing to show right now. Ask *"show me my lenses"* to check which audience is active.                                                                                                                                                        |
| Tools don't appear after connecting                                           | Open a new chat and wait a few seconds; send a second message and the tools finish loading.                                                                                                                                                                                         |
| Tools appear but the assistant won't call them                                | Open the connector settings and set the Leadbay tool groups to **Always allow** (Claude) or enable the Leadbay plugin in the composer (ChatGPT).                                                                                                                                    |
| Custom connector/plugin option missing (Claude.ai / Claude Desktop / ChatGPT) | Custom connectors/plugins need a paid plan, and your workspace admin may need to enable them — see [Admin setup](/doc/leadbay-mcp/admin-setup.md). On **Claude Desktop** you can skip the connector entirely with the [`.dxt` extension fallback](#fallback-install-the-extension). |
| Other issue                                                                   | File a bug at [github.com/leadbay/mcp/issues](https://github.com/leadbay/mcp/issues).                                                                                                                                                                                               |

***

## Where to next

{% content-ref url="/pages/j2EqO1Nixo2ZDXQ5nKeO" %}
[What is Leadbay MCP?](/doc/leadbay-mcp/what-is-leadbay-mcp.md)
{% endcontent-ref %}

{% content-ref url="/pages/KYxczcA4BfuwR6LTxaMQ" %}
[Tools reference](/doc/leadbay-mcp/tools-reference.md)
{% endcontent-ref %}


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://docs.leadbay.app/doc/leadbay-mcp/installation.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.