> ## 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.

# Claude

> Paste the CRM URL into Connectors on claude.ai, Claude desktop, or Cowork.

Ten minutes, no terminal. Claude talks to Sailer from **Anthropic's cloud**,
not from your laptop — the URL has to be exactly the public one below.

The first connection cannot write. That is deliberate.

<Steps>
  <Step title="What you need">
    A Claude account on Free, Pro, Max, Team, or Enterprise, and a Sailer
    account whose email belongs to a workspace.

    Free plans get **one** custom connector. Pick CRM.

    On Team or Enterprise, an **Owner** has to add the connector before anyone
    else can click Connect. Members cannot invent it themselves.
  </Step>

  <Step title="Add the CRM server">
    **Free, Pro, and Max**

    1. Open **Customize → Connectors** (on some builds: **Settings → Connectors**).
    2. Click **+**, then **Add custom connector**.
    3. Name it `Sailer CRM`.
    4. Paste `https://mcp.chatsailer.com/mcp/crm`.
    5. Leave Advanced OAuth Client ID and Client Secret **empty**. Sailer
       registers Claude itself.
    6. Click **Add**.

    **Team and Enterprise**

    An Owner goes to **Admin settings → Connectors → Add custom connector**,
    pastes the same URL, and leaves the OAuth fields empty. Members then see
    the connector and click **Connect**.
  </Step>

  <Step title="Authenticate">
    Click **Connect** on the new connector. 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. **"Claude 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.

    The connector shows a generic icon rather than the Sailer mark. Expected.
    Claude only renders a logo for connectors published in the directory.
  </Step>

  <Step title="Prove it">
    Start a **new** chat. If the client asks you to enable connectors on the
    conversation, enable Sailer CRM.

    Ask:

    > Which Sailer workspace am I connected to?

    Claude 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

Add a second custom connector named `Sailer Studio` with
`https://mcp.chatsailer.com/mcp/studio`, then Connect again. A CRM grant will
not work on Studio: each server is its own OAuth audience.

Free plans only have one custom connector slot. Stay on CRM.

[Studio tools](/mcp/studio).

## This client

**Settings labels move.** If you cannot find Connectors, look under Customize
or Settings. The URL you paste does not move.

**Team / Enterprise.** If Connect is missing, an Owner has not added the
connector yet. That is an admin step, not a Sailer outage.

**Switch workspace, or grant writes.** Remove the connector, add it again, pick
the other workspace (or the write scopes) at consent. One URL is one grant.

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