Skip to main content
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).
  • 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”): 
https://mcp.connect-crm.com/mcp

​
Connect your client

1

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”.
2

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

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

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

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.

​
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

This almost always means the Workspace you chose isn’t on a plan that includes API access. Check Billing, or pick a different Workspace that has API access.
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 and reconnect.
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 for how read and write access differ.
To review or remove a connection later, go to Connected AI clients in your settings.