Connect GoHighLevel
to Claude

Yes, GoHighLevel has an official MCP. Here is how to connect it, the one mistake that stops it cold, and what a morning looks like once your CRM answers you.

If you connected GoHighLevel to Claude before, you did it with a Private Integration Token: you made a token, checked the scopes it got, and hardcoded it into your config with your location ID. It works, but that token is a standing secret you have to store and rotate, and each connection loads about forty fixed tools into Claude. The new way drops all of that.

The old way handed Claude a fixed slab of about forty named tools per account. The new way gives it five generic ones that discover and run the whole catalog at the moment they are needed. Leaner for the model, and it scales when you run more than one account.

Here is the part that makes you stop. When you approve the connection, GoHighLevel shows you everything it is granting, and it is not a handful of scopes. As of 2026 that is around forty domains and hundreds of operations, and you grant it with one button. The old token gave Claude the slice you remembered to check. This gives it the whole account.

The endpoint is the same for every sub-account, so the thing that makes a connection specific is the location you approve. That means you connect them one at a time. Here is the whole flow.

{
  "mcpServers": {
    "ghl-yourbusiness-v2": {
      "type": "http",
      "url": "https://services.leadconnectorhq.com/mcp/anthropic/v2"
    }
  }
}

Talk to it like a teammate who can see the whole account:

Pull every open opportunity and tell me which have gone quiet more than 7 days.

Find every contact tagged quote-requested with no reply, and list them with phone numbers.

Draft this week's blog post from my last three jobs, then schedule it.

The connection is plumbing. What you get out of it depends on what you can say to it. On September 4, 2026 I wrote twelve skills for my own GoHighLevel accounts, one file each, in the words an owner actually uses. I say "morning read" and I get last night's calls, the tasks nobody worked, the deals that went quiet, three people worth calling, and two follow-ups drafted and waiting on my yes. I have not opened the CRM since.

I am not selling that pack and there is no price on it. It is how I work and what I show people on a screen share. You can write your own in an afternoon: a folder, a file per skill, plain sentences about which records to read and what to propose.

A CRM assistant that sounds confident and counts wrong is worse than no assistant. Every skill I wrote loads the same rules file first, and most of those rules exist because something lied to me once.

One from the day I built it. I asked a location for its open tasks and the search came back empty, while every task on the record read complete, one of them forty minutes old. The team had already worked the queue. An empty result is not "none," it is one instrument's answer, and the fix is to count from the other side and say which side you counted from.

You install this on your own computer and sign in to your own GoHighLevel. I never see your login and I never hold your token. Nobody should be asking you for one. If you are still on the older token setup, your Private Integration Token sits in a config file on your machine, where YOUR_PIT_TOKEN is the only version of it that ever belongs on a web page. The OAuth connection does not leave one behind at all, and you can revoke it from inside GoHighLevel whenever you want.