Free · the toolbox · the new connection

The new way to connect
GoHighLevel to Claude

HighLevel shipped a new MCP. One click, your whole account, and the one mistake that stops it cold.

By J Ritter, AutoJate·Last updated July 2026
The short version

HighLevel shipped a new way to connect Claude to GoHighLevel. The old way made you create a Private Integration Token, hand-pick its scopes, and hardcode it into a config file. The new way is OAuth: you click connect, pick the location, and approve. Nothing to store, nothing to rotate. Instead of forty fixed tools it gives Claude five that reach the whole catalog, hundreds of operations across around forty domains. The one thing to get right: every account uses the same URL, so connect them one at a time and pick the location each time.

What changed

Old way vs new way

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.

Auth
OldA token you create, scope, store, and rotate
NewOAuth. Click connect and approve. Nothing to store
Endpoint
Old/mcp/ with a Bearer token + locationId header
New/mcp/anthropic/v2, no headers
Tools
Old~40 fixed tools loaded per account
New5 generic tools that reach the whole catalog
Reach
OldThe scopes you remembered to check
NewHundreds of operations across ~40 domains
Secret
OldA standing token sitting in a file
NewNone left behind for anyone to find
The new surface

Five tools instead of forty

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.

The five tools
  • search: find records by name, email, phone, or tag
  • fetch: pull the full detail on anything search returns
  • search_operations: discover what it can do, by intent
  • describe_operation: check an operation's inputs before running it
  • execute_operation: run one operation, inside your scopes and safety checks
One approve

Look at everything it grants

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.

ContactsConversationsOpportunitiesCalendarsPaymentsInvoicesProductsWorkflowsSocial PlannerBlogsEmailsFormsMediaBusinessesLocationsObjectsVoice AIConversation AIUsersSurveysFunnelsStoreCampaignsLinksCoursesKnowledge basesDocuments & contractsPhone numbersCustom fieldsTasks & tags+ more
Why it wins

Three reasons the new way is better

Security · Reach · Lean
  • Security. OAuth does not leave a token in a file for someone to find. The old way put a standing secret on your disk.
  • Reach. One approval and Claude can touch the whole account, not the slice you pre-selected.
  • Lean. Five tools per account instead of forty means Claude's context is not buried, and it scales across accounts.
Set it up

Connect it right, one account at a time

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.

01

Add one connection

Point your client at HighLevel's v2 server. No token, no headers. In Claude Code that is one entry in your .mcp.json. Name it after the account so you and Claude both know where a call lands:
.mcp.json
{
  "mcpServers": {
    "ghl-yourbusiness-v2": {
      "type": "http",
      "url": "https://services.leadconnectorhq.com/mcp/anthropic/v2"
    }
  }
}
On the Claude app, add it as a custom connector with the same URL.
02

Authorize that one

Run /mcp in Claude Code, or open the connector consent in the Claude app, and sign in to GoHighLevel.
03

Pick the one location, then approve

Choose the single sub-account this connection owns, and approve. This is the one-click moment where the whole account gets granted.
04

Repeat, one at a time

Only after it connects, add and authorize the next account the same way. Never authorize several at once. See below for why.
The one mistake that breaks it

Every account points at the exact same URL. So the only thing that tells one connection apart from another is the location you approve during sign-in. Add all your accounts first, then try to authorize them together, and the location picker collides. It will not connect right. Add one, authorize it, pick its location, confirm it connected, then do the next one.

Try it

Once it's connected

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

Starter prompts
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.
Quick answers

Before you ask

The boring, useful part of AI for people who run real businesses.

Want to see what Claude can actually do once it's on your account? That's the rundown here. Or if you'd rather someone wire your systems so they run right the first time, that's what I do.

Get your systems wired to run like this→

Starts with a free call, no pitch. I'll tell you straight what's worth automating and what isn't.