How to Connect Claude to GoHighLevel (MCP)

In short

• GoHighLevel ships an official MCP server that Claude can connect to directly.
• You need one token from GoHighLevel and a few minutes inside Claude settings.
• Claude only sees and touches what your token allows, nothing more.

What does "connecting Claude to GoHighLevel" mean?

MCP stands for Model Context Protocol. It is an open standard that lets an AI assistant call an outside tool through a defined set of actions instead of guessing at a screen. GoHighLevel publishes an official MCP server, and Claude is one of the AI tools built to speak that protocol.

Once the two are connected, you can ask Claude something like "find contacts who have not booked a call this week" in a normal chat, and Claude reaches into your GoHighLevel account through the MCP server to pull the real answer. No dashboard clicking, no exporting a spreadsheet first.

You are not installing anything inside GoHighLevel. You are giving Claude a key (the token from Step 1 below) and pointing it at an address GoHighLevel already runs. GoHighLevel controls what that key can see and do.

What do you need before you start?

Three things, and setup takes about 10 minutes:

• A GoHighLevel account on any plan, with admin access to Settings.
• Claude, either the web app, the desktop app, or Claude Code, on a plan that supports connecting outside tools.
• A few minutes to create one token and paste two values into Claude.

You do not need to write code for the web or desktop path below. Claude Code is the one option built for developers, and it is optional, not required.

Step 1: Create a Private Integration Token in GoHighLevel

In GoHighLevel, go to Settings, then Private Integrations, then Create New Integration. Give it a name you will recognize later, such as "Claude MCP."

Select only the scopes you want Claude to use. If you want Claude to read and summarize your contacts and conversations, choose the contacts and conversations scopes and stop there. Leave delete and write scopes off until you trust the setup, since some scopes let a connected tool remove data.

Copy the token before you close the screen. It starts with "pit-" and GoHighLevel shows it to you exactly once. This is the only piece GoHighLevel treats as a secret, so store it somewhere private, the same way you would a password.

Step 2: Find your GoHighLevel Location ID

The Location ID tells the MCP server which GoHighLevel sub-account to work in. Find it in Settings, then Company, then Locations, and copy the ID next to the account you want Claude to use.

You can also read it from the browser address bar while inside that sub-account. It is the long string of letters and numbers that follows "/location/" in the URL.

Step 3: Add the GoHighLevel MCP server to Claude

How you do this depends on which version of Claude you use. Most people use the web app or the desktop app, so start there.

Claude web app or Claude desktop app (no code)

Open Settings inside Claude and look for a section called Connectors or Integrations. Choose the option to add a custom or remote server connector.

Paste in the GoHighLevel MCP server address, then paste your token and Location ID into the fields the connector form asks for. The exact wording of these menus can shift as Anthropic updates the interface, so if the labels above look slightly different in your app, look for anything named Connectors, Integrations, or MCP servers.

Save the connector and restart Claude if it asks you to. GoHighLevel should now appear as a connected tool the next time you start a chat.

Claude Code (for developers)

Claude Code stores its MCP configuration in a file called ~/.claude.json. Add a block under mcpServers with the GoHighLevel address, your token, and your Location ID, or run the command "claude mcp add" and paste those values in when it prompts you.

~/.claude.json

{
  "mcpServers": {
    "ghl": {
      "url": "https://services.leadconnectorhq.com/mcp/",
      "headers": {
        "Authorization": "Bearer YOUR_PIT_TOKEN",
        "locationId": "YOUR_LOCATION_ID"
      }
    }
  }
}

Restart Claude Code, then type "/mcp" to confirm GoHighLevel shows up in the connected tools list.

Step 4: Confirm the connection works

Ask Claude something small and safe first, such as "list my 5 most recent GoHighLevel contacts." If Claude comes back with real names from your account, the connection works.

If Claude says it has no GoHighLevel tool available, recheck three things: the token starts with "pit-", the scopes you picked cover what you asked for, and you restarted Claude after adding the connector. Those three cover almost every setup miss.

What can Claude actually do once it is connected?

Exactly what your token allows, and nothing past that. The GoHighLevel MCP server reaches into contacts, conversations, calendars, opportunities, and a handful of other modules, but Claude only gets a door into the ones covered by the scopes you selected in Step 1.

In practice, once contacts, conversations, and opportunities are enabled, people ask Claude things like "summarize this week's conversations and flag anyone who sounds unhappy," "create an opportunity for this lead," or "pull a quick briefing before my next call." Claude reads or writes through the same rules GoHighLevel enforces for any other integration, it does not get special access.

How do you keep the connection safe?

The token is the entire control surface, so treat it that way.

• Start read-only. Grant only the scopes you need today. Add write access later once you trust what Claude returns.
• Skip delete scopes. Leave them off unless you have a specific reason to want them.
• Use one token per account. If you manage more than one GoHighLevel location, create a separate token for each so you can revoke one without touching the others.
• Revoke on exposure. If a token ever leaks, revoke it in GoHighLevel right away instead of waiting.

More from RocketLauncher

• GoHighLevel cost calculator