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

# ChatGPT

> Developer mode, a custom connector, then enable it on the chat — adding it is not enough.

Ten minutes, if Developer mode is already on. ChatGPT talks to Sailer from
OpenAI's cloud. This is a **custom connector**, not a listing in the Apps
directory.

The first connection cannot write. That is deliberate.

<Steps>
  <Step title="What you need">
    A **paid** ChatGPT plan: Plus, Pro, Business, Enterprise, or Edu. Free
    cannot add custom MCP.

    A Sailer account whose email belongs to a workspace. You do not need an
    API token.

    On Business / Enterprise / Edu, an admin may need to allow connectors for
    the workspace first.
  </Step>

  <Step title="Turn on Developer mode">
    In ChatGPT on the web:

    1. Open **Settings**.
    2. Open **Security and login** (on some builds: **Apps & Connectors →
       Advanced settings**).
    3. Turn on **Developer mode**. Accept the warning that custom connectors
       run third-party code on your behalf.
  </Step>

  <Step title="Add the CRM server">
    1. Go to **ChatGPT Plugins** (on some builds: **Settings → Connectors**)
       and click the plus / **Create**.
    2. Name it `Sailer CRM`. Give it a one-line description if asked.
    3. Paste `https://mcp.chatsailer.com/mcp/crm`.
    4. Authentication: **OAuth**. Leave Client ID and Client Secret **empty**.
       Sailer registers ChatGPT itself.
    5. Create.

    OpenAI's Settings labels move. The URL you paste does not.
  </Step>

  <Step title="Authenticate">
    ChatGPT starts the OAuth flow. Your browser opens.

    Three screens, in this order:

    1. **Auth0 sign-in** — your Sailer email and password. Already signed in?
       This step is skipped.
    2. **"ChatGPT wants to connect"** — one workspace is confirmed text;
       several is a dropdown. The permission list matches the workspace you pick.
    3. Click **Approve**. Close the tab.
  </Step>

  <Step title="Enable it on the chat">
    Adding the connector is not enough. ChatGPT will not call Sailer until the
    connector is on **this** conversation.

    1. Start a **new** chat.
    2. Open the composer **+** / **More** menu.
    3. Choose **Developer mode** (or the Apps picker) and select **Sailer CRM**.

    Then ask:

    > Which Sailer workspace am I connected to?

    ChatGPT will call `whoami` and name the workspace, the parent organization,
    who authorized the connection, and the scopes you granted.
  </Step>

  <Step title="Do something real">
    > How many contacts are in this workspace?

    > Describe the CRM schema — what custom fields does this workspace have?

    > Find contacts created in the last 7 days.

    [CRM tools](/mcp/crm) is the catalogue. Writes need a reconnect —
    [Authentication](/mcp/auth).
  </Step>
</Steps>

## Add Studio too

Create a second connector named `Sailer Studio` with
`https://mcp.chatsailer.com/mcp/studio`, complete OAuth again, and enable it on
the chat. A CRM grant will not work on Studio: each server is its own OAuth
audience.

[Studio tools](/mcp/studio).

## This client

**No tools in the picker.** Open the connector's details page and refresh it so
ChatGPT re-fetches `tools/list`. Then start a new chat and enable it again.

**Free plan.** Custom MCP is a paid-plan feature. There is no workaround on
this page.

**Switch workspace, or grant writes.** Delete the connector, create it again,
pick at consent. One URL is one grant.

Shared failures (wrong URL, unknown email, missing scope) are on
[Troubleshooting](/mcp/troubleshooting).