How to Connect Claude with GoHighLevel MCP in 2026

Last updated: October 7, 2026

To connect Claude to GoHighLevel (GHL), you add HighLevel’s official MCP (Model Context Protocol) server to Claude as a connector. HighLevel runs two official endpoints: a Claude-specific server at https://services.leadconnectorhq.com/mcp/anthropic/v2 that uses one-click OAuth and reaches more than 550 operations, and the original universal server at https://services.leadconnectorhq.com/mcp/ with 36 tools and Private Integration Token (PIT) sign-in. In Claude.ai or Claude Desktop you add it under Connectors with Add custom connector, and in Claude Code it takes one claude mcp add command.

You want Claude to actually do work inside GoHighLevel, not just chat about it. That is exactly what MCP (Model Context Protocol) does, and HighLevel’s official server has grown fast since launch. The biggest change this year: HighLevel launched a Claude-specific MCP endpoint with OAuth sign-in, multi-sub-account access for agencies and a much larger operation catalog, while the original 36-tool server (with blogs, email templates and social posting) stays fully supported. This guide covers the verified current setup, the full tool list, working test commands, security practices, and how Claude MCP compares to GHL’s built-in Ask AI.

What “Claude with GHL” Actually Means

Connecting Claude to GoHighLevel through MCP gives Claude secure, permission-scoped read and write access to your sub-account. You control exactly what it can touch through the scopes on your Private Integration Token. Before MCP, connecting Claude to GHL meant custom API builds, Zapier middleware, or brittle scripts. MCP replaces all of that with one HTTP endpoint. Think of it as USB for AI agents: one universal connector, no custom adapters.

What Claude Can Do Inside GHL Once Connected

• Read and update contacts, tags, tasks, and custom fields
• Search opportunities and move them between pipeline stages
• Read conversations and send SMS, email, and chat messages
• Pull calendar events and appointment notes
• Look up payment orders and transaction history
• Create, update, and publish blog posts (new in the expanded toolset)
• Create email templates (new)
• Create, edit, and schedule social media posts, plus pull social analytics (new)

HighLevel’s Official MCP Server: Two Endpoints Explained

Endpoint: https://services.leadconnectorhq.com/mcp/ (the original universal server: 36 tools, Private Integration Token or OAuth, still fully supported). Claude endpoint: https://services.leadconnectorhq.com/mcp/anthropic/v2, which uses OAuth and a small set of discovery tools (search, describe and execute operations) to reach more than 550 operations across about 40 areas, including invoices, forms, funnels, workflows and custom objects. The universal endpoint also works with Cursor, Windsurf, OpenAI Playground and n8n (v1.104+ with HTTP Streamable transport), and HighLevel does not list a separate fee for either one beyond your GHL and Claude plans.

The 36 Tools on the Universal /mcp/ Endpoint

Which GHL MCP Endpoint Should You Use?

HighLevel now offers two official MCP endpoints. Both are hosted by HighLevel, so there is nothing to install on a server, but they sign in and behave differently.

For most people searching how to connect Claude to GHL, the Claude endpoint is the better start. There is no token to copy, store or rotate, and HighLevel says the OAuth path exposes a wider set of scopes than a PIT.

Pick the universal endpoint when a tool only accepts header-based auth, or when you want a short, fixed tool list. That matters in clients that cap the number of active tools.

Whichever you choose, the data is the same CRM. Permissions still come from the scopes you approve, so a narrow grant limits what Claude can see and change.

What You Need Before Setup

1. A GoHighLevel account on any plan, with admin access to a sub-account (you need it to approve the OAuth sign-in or create a Private Integration; agency admins can authorize several sub-accounts at once on the Claude endpoint).
2. Claude installed: a Claude account on any plan (the Free plan is limited to one custom connector, and Claude Code needs Pro or higher), or another MCP-compatible client.
3. Your Location ID from Settings → Business Profile. Note: the locationId header is now optional. You can pass it in your prompt instead, which is useful for agencies working across multiple sub-accounts.
4. 10 to 15 minutes.

No coding needed for the basic setup.

Step-by-Step: Connect Claude to GHL via MCP

Option A: Add the GHL Claude Connector With OAuth (Recommended)

This is the quickest way to connect GHL to Claude, and it works the same in Claude.ai and the Claude Desktop app.

1. In Claude, open Connectors (under Customize or Settings, depending on your app version).
2. Choose Add custom connector and give it a clear name, such as HighLevel.
3. Paste https://services.leadconnectorhq.com/mcp/anthropic/v2 as the server URL and save.
4. Click Connect. HighLevel opens its sign-in and consent screen.
5. Pick the sub-account (agency users can pick several), review the scopes and approve.
6. Back in a chat, enable the connector and ask: “Find the last 5 contacts I added in HighLevel.”

On Team and Enterprise plans, an owner adds the connector once in the organization’s connector settings. Each member then connects it with their own HighLevel login.

For Claude Code, run claude mcp add –transport http leadconnector https://services.leadconnectorhq.com/mcp/anthropic/v2 and complete the sign-in when prompted. Check the result with /mcp.

Anthropic connects to custom connectors from its cloud, not from your computer. That is why HighLevel’s public endpoints work, while a server on a private network or behind a VPN will not.

Option B: Private Integration Token on the Universal Endpoint

Use the steps below if you need token-based auth, want the fixed 36-tool list, or are wiring GHL into a non-Claude client as well.

Step 1: Create a Private Integration Token in GHL

1. Log into your GoHighLevel sub-account
2. Go to Settings → Private Integrations
3. Click Create New Integration
4. Name it clearly: “Claude MCP” or “Claude Agent, [Client Name]”
5. Click Next to select scopes

Step 2: Select the Right Scopes

Start minimal. You can add scopes later in 30 seconds. Recovering from an over-permissioned leaked token is much harder. Core scopes (most users):

• View Locations
• View/Edit Contacts
• View/Edit Conversations and Conversation Messages
• View/Edit Opportunities
• View Calendars and Calendar Events
• View Custom Fields

Add these only if you use the new tools:

• Blogs: Create Blog Post, Update Blog Post, Check Blog Post Slug, View Blog Authors, View Blog Categories, blogslistreadonly, blogspostsreadonly
• Email: View Email Templates; Create, Update and Delete Email Templates
• Social: View/Edit Social Media Posts, View Social Media Accounts, socialplannerstatisticsreadonly
• Payments: View Payment Orders, View Payment Transactions

Step 3: Generate and Copy Your PIT Token

Click Create Token, confirm, and copy the token (it starts with “pit-”). You cannot view it again later, only regenerate. Store it somewhere safe.

Step 4: Get Your Location ID

Go to Settings → Business Profile and copy the Location ID. Or skip this step and simply tell Claude the location ID in your prompt when needed, since the header is now optional.

Step 5: Configure Claude

For Claude.ai or Claude Desktop (custom connector): Open Connectors (under Customize or Settings, depending on your app version), choose Add custom connector and paste https://services.leadconnectorhq.com/mcp/. Under Request headers, add Authorization with the value Bearer followed by your PIT, plus an optional locationId header. Do not paste the URL into claude_desktop_config.json, because that file only loads local servers; use the connector screen or a local bridge such as mcp-remote. For Claude Code (terminal):

claude mcp add --transport http ghl-mcp https://services.leadconnectorhq.com/mcp/ \
  -H "Authorization: Bearer YOUR_PIT_TOKEN" \
  -H "locationId: YOUR_LOCATION_ID"

Verify with /mcp inside Claude Code. You should see ghl-mcp connected with its tools listed.

Step 6: Test the Connection

"Connect to GHL. Pull all my pipelines, tags, and custom fields."

Success responses listing your data mean you are live. Authorization errors mean a bad PIT or Location ID. Scope errors mean you need to add permissions to the PIT.

Claude Plans and Where the GHL Connector Works

You do not need a paid Claude plan to try this. Custom connectors are available on Free, Pro, Max, Team and Enterprise, and the Free plan is limited to one custom connector.

• Free: one custom connector in Claude.ai and Claude Desktop. Enough to test GHL, but not Claude Code.
• Pro: $20/month, or $17/month billed annually. Adds Claude Code and higher usage limits.
• Max: from $100/month for heavier daily use.
• Team and Enterprise: owners add the connector for the organization, and members connect individually.

A connector added in Claude.ai also shows up in Claude Desktop, because both use the same account settings. Claude Code keeps its own MCP list, so add the server there separately.

One common mix-up: the claude_desktop_config.json file is for local servers that run on your computer. HighLevel’s server is remote, so add it as a custom connector instead of editing that file.

7 Working Commands to Test After Setup

1. Pipeline Analysis

"How many contacts do I have in each pipeline stage? Show me which
stages have the most stuck deals and suggest which ones need follow-up first."

2. Bulk Contact Tagging

"Find all contacts added in the last 30 days and tag them 'Fresh Lead'."

3. Personalized Follow-Up Drafts

"Show me my top 10 stuck opportunities. For each one, draft a
personalized SMS follow-up based on their last conversation.
Don't send them yet, just show me the drafts."

4. Custom Reporting

"Pull all opportunities closed in the last 30 days. Group them by
source. Show me which lead source has the highest close rate."

5. Blog Publishing (new)

"Check if the slug 'gohighlevel-pricing-2026' is available on my blog.
If yes, create a draft blog post with the article I paste below,
under the category 'GHL Guides', with me as the author."

6. Email Template Creation (new)

"Create an email template called 'Webinar Follow-Up' with a subject
line, a personalized greeting using the first name field, and a
booking link CTA."

7. Social Media Scheduling (new)

"Show me my connected social accounts. Then create a post for
Facebook and Instagram announcing our new service, scheduled for
Thursday 10am. Show me the draft before publishing."

Official vs Community MCP Servers

Official server (recommended starting point): maintained and hosted by HighLevel, and the Claude OAuth endpoint now covers invoices, forms, funnels, workflows and custom objects, which used to be the main reason to look elsewhere. Community GitHub servers such as mastanley13/GoHighLevel-MCP list hundreds of API tools, but you self-host them, maintain updates and accept the security risk of running unofficial code against your CRM. Move to one only if you hit a specific gap the official endpoints cannot cover.

Hosted option, no self-hosting: GHL MCP (ghlmcp.io) is a hosted service, branded Lead Spine, that connects Claude and other AI assistants to GoHighLevel through a Marketplace app sign-in, with a focus on building and auditing workflows. It has a free tier and paid plans, and you do not run a server yourself. Disclosure: it was built by Muhammad Waseem, the founder of AutogenCRM, so weigh it the same way you would any vendor tool and start with minimum scopes.

Prefer to have it set up for you? We connect Claude to GHL, scope the token safely and build the first automations as part of a custom workflow pack. See our pricing or call +1 (681) 276-7045.

Connecting Multiple Sub-Accounts as an Agency

Agencies are the ones who search for a GHL MCP for Claude most, because the value grows with every client account. The setup choice changes how you manage that.

With OAuth on the Claude endpoint

During the HighLevel consent step, an agency admin can choose one sub-account, several, or all of them. Claude can then switch between those locations in the same conversation without reconnecting.

Name the client in every prompt, such as “in the [client name] sub-account”. That keeps Claude from acting on the wrong location when several are authorized.

With Private Integration Tokens

Create one PIT per sub-account and add each one as its own connector or server entry, named after the client. Revoking one client’s access then never touches the others.

This is more work up front, but it keeps a clean boundary when you hand an account back or offboard a client.

Agency guardrails we recommend

• Start with read-only scopes, and add write scopes only for the jobs you actually run.
• Keep sending, publishing and bulk updates behind a “show me first” instruction.
• Remove a client’s sub-account from the grant, or delete its token, the day the engagement ends.
• Write down which connector maps to which client so your team does not guess.

Security Best Practices When Connecting Claude to GHL

1. Minimum scopes only. Add more later when needed.
2. Rotate PITs every 90 days. Settings → Private Integrations → Rotate Token. The “rotate and expire later” option keeps the old token valid 7 days so you can update configs without downtime.
3. Environment variables, not hardcoded tokens. Use ${env:GHL_PIT_TOKEN} style references where your client supports it.
4. One PIT per client sub-account. Never share a token across accounts.
5. Test in a sandbox sub-account first. One bulk prompt can change hundreds of records before you spot a mistake.
6. Human-in-the-loop for sends and publishes. Always tell Claude “show me the draft first” for mass SMS, blog publishing, and social posts.
7. Review connected apps and tokens in Settings → Private Integrations regularly, and revoke OAuth grants or tokens you no longer use.

Common Setup Errors and Fixes

“Authorization failed” / “Invalid token”: PIT copied wrong, a legacy v1 API key (API v1 has reached end-of-life), or a rotated token that expired. Create a fresh Private Integration Token. “Location not found”: wrong Location ID, or your PIT does not have access to that location. Since the locationId header is optional now, you can also just state the location ID in your prompt. “Tool not available” / “Unauthorized action”: missing scope. Edit the integration and add it. MCP server shows disconnected in Claude Desktop: remember that claude_desktop_config.json only loads local servers, so add the URL as a custom connector instead, and confirm the endpoint URL is exactly https://services.leadconnectorhq.com/mcp/. Tool cap in Cursor: Cursor limits active tools. Disable unused ones, or stick with the official server’s 36 tools instead of a 500-tool community server.

Claude MCP vs GHL’s Native Ask AI

HighLevel has its own native AI feature called Ask AI that lets you talk to your CRM inside the platform. No MCP setup required.

Use Ask AI for quick in-platform actions with zero setup. Use Claude MCP for complex analysis, multi-system workflows, custom file outputs, and content operations. The new blog and social tools make Claude a real content pipeline for GHL sites. Most operators end up using both.

Real Use Cases That Pay Back the Setup Time

1. Pipeline Cleanup at Scale

“Find all opportunities that haven’t moved in 30 days and aren’t tagged ‘cold’. Add a ‘Stuck Deal’ tag.”

2. Content Pipeline Into GHL Blogs (new)

Draft an article with Claude, have it check the slug, create the post in the right category with the right author, and publish, all in one conversation. This was impossible on the official server before the blog tools shipped.

3. Social Calendar From One Prompt (new)

“Create a week of posts for my HVAC client across Facebook and Instagram, based on their top 3 services. Show me all drafts before scheduling.”

4. Snapshot Personalization

After importing a snapshot, have Claude update contact data and messaging templates with the client’s business info in seconds instead of clicking through settings.

5. Cross-Tool Orchestration

With GHL + Google Drive + Gmail MCP servers connected, one prompt can handle a multi-step task that would otherwise need several Zapier steps: “For every new GHL contact tagged ‘Premium’, create a folder in Drive, generate a welcome PDF, and send it via Gmail.”

The Honest Take on Claude with GHL

The official server’s new OAuth endpoint for Claude closed its biggest gaps: easy sign-in, multi-sub-account access and broad API coverage. For most agencies, there is no longer a reason to start with a community server. Three things to keep in mind. The setup is one-time but real; if you only need quick in-platform actions, Ask AI is faster to start. Security is your responsibility; scoped tokens and sandbox testing are not optional. And if you need invoices, forms, funnels or workflow data, try the Claude OAuth endpoint before reaching for a self-hosted community server. For agencies and operators serious about leverage, Claude MCP is worth the 15 minutes. A properly done GoHighLevel setup makes everything Claude touches cleaner, because AI on top of a messy account just makes messes faster.

Related: GoHighLevel API guide: auth, endpoints and rate limits · GoHighLevel Zapier integration.

Frequently Asked Questions

How many tools does the official HighLevel MCP server have?

It depends on the endpoint. The universal /mcp/ server has 36 tools covering contacts, conversations, opportunities, calendars, payments, blogs, email templates, social posting and location data. The Claude endpoint (/mcp/anthropic/v2) uses a few discovery tools to reach more than 550 operations across about 40 areas.

What changed in the latest HighLevel MCP update?

HighLevel launched a Claude-specific endpoint with one-click OAuth, multi-sub-account access for agencies and a catalog of more than 550 operations. Before that, the universal server grew from about 21 to 36 tools, adding blogs, email templates and social posting, and the locationId header became optional.

How do I connect Claude to GoHighLevel?

In Claude.ai or Claude Desktop, open Connectors, choose Add custom connector, paste https://services.leadconnectorhq.com/mcp/anthropic/v2 and approve the HighLevel sign-in. In Claude Code, run claude mcp add –transport http with the same URL. If you prefer tokens, use the /mcp/ endpoint with a Private Integration Token sent as a Bearer header.

Is the Claude GHL MCP integration free?

Yes. HighLevel does not list a separate fee for its official MCP server, so you pay only for your GHL plan and your Claude plan. Claude Free allows one custom connector. No middleware fees.

Can Claude publish blog posts to my GHL website?

Yes, as of the 36-tool update. Claude can check slug availability, create posts, update existing posts, and assign authors and categories through the official blogs tools, provided your PIT has the blog scopes enabled.

Can Claude schedule social media posts through GHL?

Yes. The official server now includes tools to list connected accounts, create and edit posts across supported platforms, and pull social media statistics. Enable the social media scopes on your PIT.

Is Claude with GHL secure?

Yes, when configured correctly. Access is scoped via Private Integration Tokens over HTTPS. Use minimum scopes, rotate tokens every 90 days, keep one token per client account, and test bulk operations in a sandbox first.

Do I need Claude Pro to use MCP with GHL?

No, but it helps. The Free plan can add one custom connector, which is enough to test GHL in Claude.ai or Claude Desktop. Claude Code and higher usage limits need Pro ($20/month, or $17/month billed annually) or Max (from $100/month).

Can I connect multiple GHL sub-accounts to Claude?

Yes. In Claude Code, use project-level .mcp.json files, one per client folder, each with that client’s PIT. In Claude Desktop, add multiple named servers (ghl-client1, ghl-client2). Since locationId can now be passed in prompts, agencies can also manage location switching conversationally, though separate tokens per client remain the safer pattern for PIT setups. On the Claude OAuth endpoint, agency admins can authorize several sub-accounts in one connection and switch between them in the same chat.

Does the GHL MCP work with tools other than Claude?

Yes. Any HTTP-based MCP client works: Cursor, Windsurf, OpenAI Playground, Gemini CLI, and n8n (v1.104 and later with the HTTP Streamable transport and header-based auth).

What is the GHL Claude connector?

It is HighLevel’s official MCP server added to Claude as a custom connector. The Claude version lives at https://services.leadconnectorhq.com/mcp/anthropic/v2 and signs in with OAuth, so you approve access on a HighLevel consent screen instead of pasting a token. Once connected, Claude can search, read and update CRM data within the scopes you granted.

Should I use OAuth or a Private Integration Token for GHL MCP?

Use OAuth on the Claude endpoint if you work in Claude.ai, Claude Desktop, Claude Code or Cowork. HighLevel recommends it because it covers more scopes and there is no token to store or rotate. Use a PIT on the universal /mcp/ endpoint for tools that only accept header-based auth, such as many n8n or custom setups.

Why does my GHL MCP server not show up in Claude Desktop?

The most common cause is adding the HighLevel URL to claude_desktop_config.json. That file only loads local servers, so remote URLs are ignored. Add the endpoint under Connectors with Add custom connector instead, then enable it in the chat. If it still fails, reconnect and check that your scopes were approved.