Disclosure: some links in this post are affiliate links. If you sign up through them I may earn a commission, at no extra cost to you.
Want to go deeper? I run a live Claude Code workshop — check the latest dates and see if you can still grab a seat.
Here’s the direct answer: a GoHighLevel Claude integration runs through something called an MCP server, and you can wire it up in four steps — create a private integration token inside GoHighLevel, grab your location ID, drop one config block into Claude Code, then test it live. No Zapier, no third-party middleware, no custom API calls. Claude talks straight to your account.
Here’s the thing about MCP — Model Context Protocol — that makes this different from every other GoHighLevel automation you’ve probably tried. It’s not a Zap, it’s not a webhook chain, and it’s not a third-party tool sitting between two apps guessing what you meant. It’s GoHighLevel’s own official server, documented in their marketplace docs, that gives an AI direct instructions for what it’s allowed to do inside your account. Once it’s connected, you can type one plain-English sentence and Claude will pull contacts, read conversations, move pipeline deals, check calendars, or even draft social posts — all inside GoHighLevel, without you touching the interface.
I tested this myself on a clean test account with no real client data in it, on purpose, so I could show you exactly what happens when it connects and what happens when it doesn’t. Let’s go through the four steps in the order that actually gets you working, not the order that trips people up.
What is the GoHighLevel MCP server, and what can it actually do?
The GoHighLevel MCP server is GoHighLevel’s own official connection point that gives Claude a defined set of permissions inside your account — things like viewing contacts, editing calendars, or managing pipelines. The official server currently offers 39 permissions, which is plenty for most agencies running an AI executive assistant; a self-hosted MCP opens up a much larger number of permissions, though the exact count mentioned in the video isn’t fully clear — that’s a more advanced build for another day.
Where to find the setup instructions
GoHighLevel documents the whole thing at their marketplace docs, under MCP in the index. The steps are there, but a few of them are easy to get wrong the first time, so walk through it with me below.
Step 1: Create your private integration token in GoHighLevel
Inside your GoHighLevel account, go to Settings, then Private Integrations, then Create New Integration. Name it something you’ll recognize later — “Claude Code MCP” works fine. Then you’ll see a long list of permissions (scopes) you can turn on.
This is the part people rush, and it’s the one honest gotcha in this whole setup: don’t just select all. As I said while building this out,
“Don’t give it all, because if you give it all, it can delete users, add users, and it can create a bunch of problems if you give it the wrong kind of availability.”
Turn on only what you actually need — viewing locations is one of the important ones, along with calendar access if you want scheduling. Once you hit create, GoHighLevel will show you the token exactly once. Copy it right away and store it somewhere safe, because it won’t show up again. If you ever lose it or get nervous about exposure, you can rotate or delete the token from the same screen.
Step 2: Grab your GoHighLevel location ID
Next, go to your business profile inside that same GoHighLevel account and copy the location ID. This is the identifier that tells Claude which sub-account it’s talking to — important if you manage more than one client account, since each one needs its own token and location ID pairing.
Step 3: Drop the config block into Claude Code
This is where VS Code and a terminal come in. Open a terminal, switch it to PowerShell if you’re on a PC, and make sure Claude Code, git bash, and Node.js are already installed — that’s a separate setup covered in an earlier video, so don’t try to do it cold here.
Before running anything you copy from the internet, including this, ask Claude itself to check it. That’s a habit worth keeping any time you paste in a config block from a tutorial:
“I just received a code that will help install a GoHighLevel MCP on my Cloud Code in my terminal. Please make sure that this code is not malicious and that it’s right for my PC.”
Once it checks out, open the config code in a text file. You’ll see a placeholder that says “Authorization Bearer your PIT token here” — replace only the token portion with the private integration token you saved in Step 1, keeping the “Bearer” prefix. Then find the location ID field and paste your location ID exactly between the quotation marks — don’t remove the quotes or change anything else in the file.
Back in your terminal, paste the full command and hit enter. If it worked, you’ll see a confirmation that the GoHighLevel MCP was added. Then type a quick command to Claude asking it to check MCP status, and you should see it listed as GoHighLevel MCP connected.
Step 4: Test it live and build your first GoHighLevel agent
Once GoHighLevel shows connected, the real test is asking Claude to do something with it. A simple first prompt: ask it to run a discovery — connect to GoHighLevel, pull all pipelines, tags, and custom fields, and save that information. If your token and location ID are right, you’ll get a string of “success: true” responses as Claude hits each endpoint.
From here you’re not just running a one-off command, you’re laying the groundwork for an actual AI agent — a folder structure with a main agent file (a CLAUDE.md, in this setup) that tells the bot its rules, where the MCP server lives, and where the token and location ID are stored as environment variables. Once that’s filled in and saved as your live .env file, you now actually have the GoHighLevel connected, and you can ask things directly, in plain English:
- “Who’s in the lead management pipeline, and how many contacts are in the new lead section?”
- “What calendars do I have available?”
- “Add this person to the new lead pipeline.”
One real limitation worth knowing up front: the current GoHighLevel MCP tools don’t include a list-calendars endpoint. If Claude can’t find a calendar by name, you’ll need to go grab the calendar IDs manually from GoHighLevel and add them into the agent’s instructions yourself — this is running a GoHighLevel agent for the specific location, so those IDs matter. It’s a small workaround, but it’s the kind of thing that’ll stump you for ten minutes if you don’t expect it.
Frequently asked questions
Do I need to know how to code to set up the GoHighLevel Claude integration?
No. You’re editing a couple of placeholders in a text file — a token and a location ID — and pasting a command into a terminal. If you can follow a checklist, you can do this part. Having Claude Code, git bash, and Node.js already installed is the real prerequisite.
Is this the same as connecting GoHighLevel through Zapier or an API?
No, and that’s the point. MCP is GoHighLevel’s own server that gives Claude direct instructions for what it’s allowed to do inside your account. There’s no third-party middleware sitting in between and no Zap to maintain.
What permissions should I turn on for the private integration token?
Only what you actually need. Viewing locations and calendar access cover a lot of common use cases. Avoid giving full access, since that opens the door to Claude being able to delete or add users and make changes you didn’t intend.
Can I connect Claude to more than one GoHighLevel sub-account?
Yes. Each sub-account needs its own private integration token and location ID, and you’d set up a separate agent (or separate MCP connection) per location if you’re managing multiple client accounts.
If you want the fuller walkthrough on building out an entire AI agent team on top of this — not just the GoHighLevel connection, but multiple agents talking to each other — that’s covered start to finish inside the GoHighLevel Masterclass. And if you’re new here, this is the kind of setup we cover constantly for free on the @AutomatedMarketer YouTube channel — see what Automated Marketer is and check the FAQ for common GoHighLevel questions.