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

# Connecting a client

> Connect Claude, Cursor, or any MCP client to your Connect-CRM Workspace.

Connecting takes about a minute. You add the Connect-CRM server to your AI client, sign in through Connect-CRM, choose which Workspace to share, and approve the access. There are no API keys to copy and paste.

## Prerequisites

* An MCP-capable AI client (e.g. **Claude** or **Cursor**).
* A Connect-CRM plan that includes **API access** (Free and lapsed plans are refused — see [Billing](/workspace-management/billing)).
* Membership of the Workspace you want to connect.

## The Connect-CRM server address

Add this URL as a remote MCP server (your client may call it a "connector" or "custom integration"):

<CodeBlock>[https://mcp.connect-crm.com/mcp](https://mcp.connect-crm.com/mcp)</CodeBlock>

## Connect your client

<Steps>
  <Step title="Add the Connect-CRM server">
    In your AI client's settings, find where you add a remote MCP server or
    connector, and paste the address above.

    * **Claude:** Settings → Connectors → **Add custom connector**, then enter the URL.
    * **Cursor:** Settings → MCP → **Add new MCP server**, then enter the URL.

    The exact menu names vary by client and version, but you're always looking
    for "add a remote/custom MCP server by URL".
  </Step>

  <Step title="Sign in to Connect-CRM">
    Your client opens a Connect-CRM sign-in window in your browser. Sign in as you
    normally would. Your AI client never sees your password — it only receives a
    token after you approve.
  </Step>

  <Step title="Choose a Workspace">
    On the consent screen you'll be asked to pick **which Workspace** to grant
    access to. The connection is scoped to that one Workspace.

    <Note>
      If you belong to more than one Workspace, you'll see a selector here.
      Connect each Workspace separately — one connection grants access to one
      Workspace.
    </Note>
  </Step>

  <Step title="Approve the access">
    Review the access being requested and approve it. You'll grant the assistant
    permission to read your data and, if offered and you allow it, to create and
    update Records. The assistant can never delete Records.
  </Step>

  <Step title="Start using it">
    Back in your AI client, the Connect-CRM tools are now available. Try asking
    something like *"List the Objects in my CRM"* or *"Find the company Acme
    Corp"* to confirm it's working.
  </Step>
</Steps>

## Switching Workspaces

Because each connection is tied to a single Workspace, working in a different
Workspace means connecting again and choosing that Workspace on the consent
screen. Your AI client will then hold one connection per Workspace.

## Troubleshooting

<AccordionGroup>
  <Accordion title="The connection was refused after I signed in">
    This almost always means the Workspace you chose isn't on a plan that
    includes API access. Check [Billing](/workspace-management/billing), or pick
    a different Workspace that has API access.
  </Accordion>

  <Accordion title="My client didn't ask me to choose a Workspace">
    A Workspace is required. If you weren't prompted, your client may have
    reused an earlier connection. Remove the Connect-CRM server from your client
    and add it again, or revoke the existing connection from [Connected AI
    clients](/integrations/ai-clients/managing) and reconnect.
  </Accordion>

  <Accordion title="The assistant can read but can't create or update Records">
    The connection was granted read-only access. Remove and re-add the
    connection, approving read-and-write access when prompted. See [What your
    assistant can do](/integrations/ai-clients/tools) for how read and write
    access differ.
  </Accordion>
</AccordionGroup>

<Note>
  To review or remove a connection later, go to [Connected AI
  clients](/integrations/ai-clients/managing) in your settings.
</Note>