Connect GoHighLevel to Claude Code

Make Claude create contacts and move opportunities in GoHighLevel. From the terminal, inside the sessions where you already work.

Build my connector Talk to us

How do you connect GoHighLevel to Claude Code?

Claude Code reaches outside tools through MCP servers. To connect GoHighLevel, you add a GoHighLevel MCP server: a small hosted service that exposes GoHighLevel's data and actions over the Model Context Protocol. With a custom connector we build for you, that is one command in the terminal, then an OAuth sign-in with your own GoHighLevel account. No API keys pasted into config files.

claude mcp add --transport http gohighlevel https://your-connector-url/mcp

Then run /mcp inside a Claude Code session to sign in. Add it with --scope project and the connector is checked into the repo for your whole team.

What can Claude Code do in GoHighLevel once connected?

Full read-write GoHighLevel access lets Claude create and update contacts, move opportunities through a pipeline stage, log notes and tasks, and queue a message after you approve it. The data entry and stage hygiene that used to mean clicking through sub-accounts happen where the records already live.

Create or update a contact and tag it inside a specific location
Move an opportunity to a new pipeline stage and update its value
Log a note or create a follow-up task on a contact record
Add or remove tags to segment contacts for a campaign
Draft an SMS or email to a contact and queue it for your approval
Enroll a contact in a workflow once you confirm the step

One connector, every Claude surface

The connector we build is a remote MCP server, which is the same standard claude.ai and Claude Desktop use. Add it once and the same GoHighLevel access works in Claude Code for you, in claude.ai for the rest of the team, and in Claude Desktop. One build, one set of permissions, one monthly plan covering all of them.

Build it yourself, or have it built?

If you live in the terminal, you can absolutely write your own MCP server against the GoHighLevel API. The protocol is open. What you take on is everything around the happy path: OAuth token refresh, hosting, monitoring, keeping up when GoHighLevel changes its API and when the MCP spec itself moves, and scoping write actions so an agent can never do more than you intended. We build GoHighLevel connectors with separated read and write tools and approval gates on destructive actions, then host and maintain them so they keep working while you work.

Frequently asked questions

Does the same GoHighLevel connector work in claude.ai and Claude Code?

Yes. It is one remote MCP server. Claude Code adds it with a single "claude mcp add" command; claude.ai and Claude Desktop add it as a custom connector in Settings. Each person signs in with their own GoHighLevel account, so access always matches what that person can already see and do.

Do I need to host or maintain anything myself?

No. The connector runs as a hosted service we operate: we handle uptime, token health, API changes on GoHighLevel's side, and MCP spec migrations under the monthly plan. Your side is one command in the terminal and an OAuth sign-in.

Is it safe to give a coding agent write access to GoHighLevel?

Write access is scoped, not blanket. Read tools and write tools are separated, destructive actions like deleting or sending are gated behind your explicit approval, and the connector can never exceed the permissions of the GoHighLevel account it signs in with. Revoking access is one click in GoHighLevel.

More on the GoHighLevel connector

GoHighLevel connector for claude.ai Freshsales + Claude Code Insightly + Claude Code SugarCRM + Claude Code

Tell us what you run. We'll build the connector.

Pick your tool, choose what Claude should do, and get an instant scope and price. No call required.

Build my connector Talk to us