How to Connect Claude with GoHighLevel MCP in 2026

Claude with GHL means connecting Anthropic’s Claude (Desktop, Code, or API) to GoHighLevel through the Model Context Protocol (MCP). Once connected, Claude can read contacts, update pipelines, send SMS and emails, book appointments, create workflows, and run reports from plain English commands. HighLevel’s official MCP server launched in early 2026 at https://services.leadconnectorhq.com/mcp/ with ~21 native tools (expanding to 250+). Community-built MCP servers offer 269 to 520+ tools for deeper access. Setup takes 10 to 15 minutes and requires a Private Integration Token (PIT) plus your Location ID. This guide covers the verified setup, sample commands, real use cases, and how it compares to GHL’s native Ask AI feature.

You want to use Claude to actually do work inside GoHighLevel, not just chat about it.

The answer is MCP (Model Context Protocol). It’s an open standard built by Anthropic that lets Claude connect directly to GoHighLevel through a secure HTTP endpoint. Once connected, Claude can read your CRM data and make changes inside your account using plain English commands.

This guide covers everything: the official HighLevel MCP server, exact setup steps, working commands to test, real workflow examples, security best practices, and how Claude MCP compares to GHL’s built-in Ask AI feature.

What “Claude with GHL” Actually Means

Claude with GHL refers to connecting Anthropic’s Claude AI to your GoHighLevel sub-account through a secure protocol so Claude can read and act on your CRM data.

Before MCP, connecting Claude to GHL meant:

• Custom API integrations (developer required)
• Middleware like Zapier or Make.com (limited and slow)
• Manual scripts calling the GHL API (technical and brittle)

MCP changes that. It’s a direct, secure, two-way connection between Claude and GoHighLevel. Claude can read your data AND write to your account through a single protocol you control with permissions.

Think of MCP like USB for AI agents. A universal standard that lets different tools plug into each other without custom adapters.

What Claude Can Do Inside GHL Once Connected

• Read contacts, pipelines, tags, custom fields
• Update opportunities and move them between pipeline stages
• Send SMS and emails to specific contacts or whole lists
• Book and reschedule appointments on calendars
• Analyze conversation history across SMS, email, and chat
• Create workflows and automation sequences
• Generate reports and pipeline analysis
• Segment contacts based on behavior or custom criteria
• Draft follow-up messages personalized to each contact
• Run bulk operations across hundreds of contacts in seconds

HighLevel’s Official MCP Server

HighLevel officially launched its MCP server in early 2026. This is the supported, secure connection point.

Endpoint: https://services.leadconnectorhq.com/mcp/

Current tool count: ~21 official tools covering core functionality (contacts, pipelines, calendars, conversations, tags, custom fields, opportunities).

Roadmap: Expanding to 250+ tools as part of a unified orchestrator layer.

Compatibility: Any client that supports HTTP-based MCP, including Claude Desktop, Claude Code, Cursor, Windsurf, OpenAI Playground, Gemini CLI, and n8n.

Security: Data access is scoped via Private Integration Tokens (PITs). All traffic is secured over HTTPS.

What You Need Before Setup

Before connecting Claude to GHL, gather:

1. A GoHighLevel account. Any plan works (Starter, Unlimited, SaaS Pro). Admin access to a sub-account is required to create Private Integrations.
2. Claude installed. Claude Desktop, Claude Code, or any MCP-compatible client.
3. Your GHL Location ID. Found in Settings → Business Profile.
4. 15 minutes. Setup is fast once you have the right pieces.

No coding experience required for basic setup. Some technical comfort helps if you’re customizing scopes or troubleshooting.

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

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]” (this name appears in your API logs)
5. Click Next to select scopes

Step 2: Select the Right Scopes

Don’t enable all scopes blindly. Start with what you actually need. You can add more later.

Minimum recommended scopes:

• View Locations — lets Claude see your account info
• View/Edit Contacts — read and update contact records
• View Pipelines — see deal stages and opportunities
• View/Edit Opportunities — move opportunities between stages
• View Conversations — read SMS, email, and chat threads
• Edit Conversations — send SMS, email, and chat messages
• View/Edit Calendars — manage appointment slots and bookings
• View/Edit Tags — segment contacts
• View Custom Fields — read custom data

Additional scopes for advanced use:

• Workflows (read/edit)
• Forms and Surveys
• Payments and Invoices (only if needed)
• Social Media (for content automation)
• Blog (for content creation)

Step 3: Generate and Copy Your PIT Token

1. After selecting scopes, click Create Token
2. Click Confirm
3. Copy the Private Integration Token (starts with “pit-“)
4. Store it somewhere safe — you can’t view it again later, only regenerate

Step 4: Get Your Location ID

1. Go to Settings → Business Profile
2. Find the Location ID field
3. Copy the value

Step 5: Configure Claude

The exact configuration depends on which Claude client you’re using.

For Claude Desktop:

1. Open Claude Desktop
2. Go to Settings → Developer → Edit Configuration
3. Open the config file (claude_desktop_config.json)
4. Add the MCP server configuration (below)
5. Save the file
6. Close Claude Desktop completely (File → Exit)
7. Reopen Claude Desktop

Configuration to paste:

{
  "mcpServers": {
    "ghl-mcp": {
      "type": "http",
      "url": "https://services.leadconnectorhq.com/mcp/",
      "headers": {
        "Authorization": "Bearer YOUR_PIT_TOKEN",
        "locationId": "YOUR_LOCATION_ID",
        "Version": "2021-07-28"
      }
    }
  }
}

Replace YOUR_PIT_TOKEN with your actual PIT (starts with pit-) and YOUR_LOCATION_ID with your Location ID.

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"

After running this, verify the connection by typing `/mcp` inside Claude Code. You should see ghl-mcp listed as connected with available tools.

Step 6: Test the Connection

Open Claude and try a simple read command:

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

You should see success responses listing your data. If you get authorization errors, your PIT token or Location ID is wrong. If you get scope errors, you need to add more permissions to your PIT.

5 Working Commands to Test After Setup

Once connected, try these prompts to see what Claude can do.

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."

Claude will pull pipeline data, count contacts per stage, identify deals that haven’t moved recently, and prioritize your follow-up list.

2. Bulk Contact Tagging

"Find all contacts who opted in through my website 
form in the last 30 days and tag them 'Fresh Lead'. 
Then add them to the 'New Lead Nurture' workflow."

Claude reads recent submissions, applies the tag, and enrolls contacts in the workflow.

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."

Claude pulls opportunity data, reads recent conversation history, and drafts contextual follow-ups for your review.

4. Workflow Creation

"Create a lead nurture workflow:
- Tag new leads 'Fresh'
- Send SMS Day 1
- Send Email Day 3
- Move to 'Hot' stage if they reply
- Book consultation if they click the calendar link"

Claude builds the workflow structure (you’ll review and activate it before going live).

5. 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 and average deal value."

Claude generates the report from your live CRM data without needing manual exports.

Official vs Community MCP Servers

There are two routes for connecting Claude to GHL via MCP.

HighLevel’s Official MCP Server

• Endpoint: https://services.leadconnectorhq.com/mcp/
• Tools: ~21 official tools (expanding to 250+)
• Maintained by: HighLevel
• Security: Officially supported with HTTPS and PIT scoping
• Best for: Most coaches, consultants, and agencies

Community-Built MCP Servers (GitHub)

Multiple open-source MCP server projects expose more of the GHL API. Examples:

• mastanley13/GoHighLevel-MCP: 269+ tools across 19 categories
• BusyBee3333/Go-High-Level-MCP-2026-Complete: 520+ tools across 40 categories, including Voice AI, Proposals, and Agent Studio

Pros: Much deeper access (invoices, payments, media library, social planner, store, advanced workflows).

Cons: Community-maintained (not officially supported). You self-host the server, manage updates yourself, and accept the security responsibility.

Recommendation: Start with the official server. Only move to community servers if you have a specific gap that requires the additional tool coverage.

Security Best Practices When Connecting Claude to GHL

When you connect an AI agent to your CRM with read AND write access, security matters a lot.

1. Use minimum scopes. Only enable what you actually need. Adding more scopes later takes 30 seconds. Recovering from a compromised broad-scope token is much harder.

2. Rotate PITs every 90 days. Settings → Private Integrations → select your PIT → Rotate Token. HighLevel offers a “Rotate and expire later” option that keeps the old token valid for 7 days so you can update agent configs without downtime.

3. Use environment variables, not hardcoded tokens. Store your PIT in environment variables like ${env:GHL_PIT_TOKEN} instead of pasting it directly into config files. Prevents accidental exposure if you share a config or commit it to Git.

4. Separate tokens per client. If you’re an agency managing multiple GHL sub-accounts, create a separate PIT for each client. Never use one token across multiple accounts.

5. Monitor API logs. Settings → Private Integrations shows API usage. Review periodically for unusual patterns.

6. Test in a sandbox first. Before running bulk Claude operations on a live client account, test in your own sandbox sub-account. AI can move 95 contacts to the wrong stage in 5 seconds.

7. Add human-in-the-loop for sensitive actions. For actions like sending mass SMS, deleting data, or refunding payments, ask Claude to confirm before executing.

8. Implement memory/recall mechanisms. Without proper context management, Claude may perform unintended actions. Always have it summarize what it’s about to do before executing destructive operations.

Common Setup Errors and Fixes

1. “Authorization failed” or “Invalid token”

• Your PIT is wrong. Check for spaces or missing characters.
• You used a legacy v1 API key (deprecated since mid-2024). Create a new Private Integration Token.
• The token was rotated and the old one expired.

2. “Location not found”

• Your Location ID is wrong. Verify in Settings → Business Profile.
• Your PIT doesn’t have access to that location. Check scopes.

3. “Tool not available” / “Unauthorized action”

• Your PIT is missing the required scope. Edit the integration and add the needed scope.
• The action requires a scope you didn’t enable. Add it.

4. Claude shows MCP server as disconnected (red status)

• Restart Claude Desktop completely (File → Exit, then reopen)
• Verify your config file syntax (valid JSON, no missing commas)
• Check that the MCP endpoint URL is exactly https://services.leadconnectorhq.com/mcp/

5. Tool limit hit in Cursor (40-80 tools)

• Cursor has an active tool cap. Disable tools you don’t need in the Cursor settings panel.
• Or use the official MCP server (~21 tools) instead of community servers.

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 and have it do tasks. No MCP setup required. Built into the platform.

Both approaches work. They serve different needs.

When to Use Each

Use GHL Ask AI when:

• You need quick in-platform actions (move contacts, message lists, update stages)
• You don’t want to set up external tools
• The task fits cleanly inside GHL’s feature set
• You’re a non-technical user who wants the simplest path

Use Claude MCP when:

• You want Claude’s reasoning power for complex analysis
• You need to connect GHL data to other tools (other MCP servers, scripts, custom workflows)
• You want custom file outputs (CSV exports, Python scripts, custom dashboards)
• You’re building advanced automations that span multiple systems
• You’re a developer or technical user who can leverage Claude Code for deeper integration

For most operators, both have a place. Ask AI handles the daily in-platform work. Claude MCP handles the analytical, multi-tool, and custom output work.

Real Use Cases Where Claude with GHL Saves Real Time

These are the patterns that actually pay back the setup time.

1. Pipeline Cleanup at Scale

Tell Claude: “Find all opportunities that haven’t moved in 30 days and aren’t tagged ‘cold’. Add a ‘Stuck Deal’ tag and put them in the re-engagement workflow.”

Manual time: 2 to 4 hours.
Claude MCP time: 30 seconds.

2. Pipeline Performance Analysis

“Pull my pipeline data for the last 90 days. Calculate conversion rates between each stage. Identify the stage where I lose the most deals and suggest 3 ways to improve it.”

This is the kind of analysis that takes a marketer 3 to 5 hours with Excel. Claude does it in seconds with full visualization output.

3. Personalized Outreach at Volume

“For each contact who attended my webinar last week, draft a personalized follow-up email referencing the specific topic they asked questions about in the chat.”

Claude reads conversation history, identifies each contact’s interests, and writes contextual follow-ups. Then you review and approve before sending.

4. Snapshot Customization Without Manual Work

After importing a snapshot, tell Claude: “Update all Custom Values in this sub-account using the client’s info: business name ‘Riverside HVAC’, phone ‘555-1234’, email ‘info@riversidhvac.com’, service area ‘Phoenix AZ’.”

Claude updates every Custom Value across the snapshot in seconds instead of you clicking through 12 settings.

5. Cross-Tool Workflow Automation

If you have multiple MCP servers connected (GHL + Google Drive + Gmail), Claude can orchestrate across them:

“For every new GHL contact tagged ‘Premium’, create a folder in Google Drive named after them, generate a welcome PDF, and send it via Gmail with their first onboarding steps.”

This kind of multi-system workflow used to require Zapier with 5 zaps. With Claude MCP, it’s one prompt.

The Honest Take on Claude with GHL

Claude MCP is genuinely powerful when used right. It gives you Claude’s full reasoning ability against your live CRM data, with read and write access, controlled by scopes you set.

But three things to know:

1. The setup is one-time but real. 10 to 15 minutes is fast for what you get, but it’s not zero. If you only need basic in-platform actions, GHL’s native Ask AI is faster to start using.

2. Security is your responsibility. Connecting AI to your CRM with edit access is powerful. Use minimum scopes, rotate tokens, test in sandbox first. AI can fix problems fast and break things even faster.

3. The official MCP server is still expanding. ~21 tools today, 250+ on the roadmap. If you need deeper access right now (invoices, payments, advanced workflows), community servers fill that gap but require self-hosting and trust in unofficial code.

For agencies and operators serious about leverage, Claude MCP is worth the 15-minute setup. For occasional in-platform tasks, GHL’s Ask AI is simpler.

Article verified and updated for 2026.

Frequently Asked Questions

What is Claude with GHL?

Claude with GHL refers to connecting Anthropic’s Claude AI to GoHighLevel through the Model Context Protocol (MCP). Once connected, Claude can read your CRM data and perform actions inside your account (managing contacts, pipelines, sending messages, booking appointments, creating workflows) using natural language commands. HighLevel’s official MCP server launched in early 2026.

How do I connect Claude to GoHighLevel?

Three steps: (1) Create a Private Integration Token in GHL at Settings → Private Integrations. (2) Get your Location ID from Settings → Business Profile. (3) Add the MCP server configuration to Claude Desktop’s config file (or use the Claude Code command) with your PIT and Location ID. Total setup time: 10 to 15 minutes. The MCP endpoint is https://services.leadconnectorhq.com/mcp/.

What is MCP (Model Context Protocol)?

MCP is an open standard developed by Anthropic that lets AI agents like Claude communicate directly with external platforms through structured endpoints. Think of it as USB for AI agents — a universal connector. It replaces custom API integrations, middleware like Zapier, and manual scripts. MCP is HTTP-based and works with any compatible client (Claude, Cursor, Windsurf, OpenAI Playground, Gemini CLI).

Is the Claude GHL MCP integration free?

Yes. HighLevel’s official MCP server is free with any GHL subscription. Claude Desktop is free, Claude Pro is $20/month for higher usage limits. The MCP connection itself has no separate cost — you pay for your GHL plan and your Claude plan separately. No middleware fees.

What can Claude do inside GoHighLevel?

Claude can read contacts, pipelines, tags, and custom fields; update opportunities and pipeline stages; send SMS and emails; book and reschedule appointments; analyze conversation history; create workflows; generate reports; segment contacts; draft personalized follow-ups; and run bulk operations across hundreds of contacts. The exact capability depends on the scopes you grant to your Private Integration Token.

How many tools does the official HighLevel MCP server have?

HighLevel’s official MCP server currently provides approximately 21 tools covering contacts, pipelines, calendars, conversations, tags, and custom fields. HighLevel’s roadmap includes expanding to 250+ tools for full automation across all platform modules. Community-built MCP servers (on GitHub) already offer 269 to 520+ tools but are community-maintained, not officially supported.

Is Claude with GHL secure?

Yes, when configured correctly. Access is scoped via Private Integration Tokens (PITs) which you control. All traffic uses HTTPS. To stay secure: use minimum scopes (only what you need), rotate PITs every 90 days, store tokens in environment variables (not hardcoded), use separate tokens per client account, and test bulk operations in a sandbox first. Never share or expose your PIT.

What’s the difference between Claude MCP and GHL Ask AI?

Claude MCP connects external Claude (Desktop, Code) to your GHL account for advanced reasoning and cross-tool workflows. GHL Ask AI is HighLevel’s native built-in AI for in-platform actions. Ask AI is zero-setup and works inside the GHL dashboard. Claude MCP requires 10 to 15 minutes of setup but offers stronger reasoning, custom file outputs, and the ability to orchestrate across multiple MCP servers. Most operators use both for different jobs.

Do I need Claude Pro to use MCP with GHL?

No, but it helps. Claude Desktop’s free tier works for testing and light use. For regular agency or business use, Claude Pro ($20/month) provides higher usage limits, more requests per day, and access to the most capable Claude model. Claude Code (used in terminals) has separate pricing based on usage.

Can I connect multiple GHL sub-accounts to Claude?

Yes. Claude Code supports project-level MCP configs through .mcp.json files placed in each project root. Create a separate folder for each client, drop a .mcp.json with that client’s PIT and Location ID, and Claude Code automatically scopes to the correct account when you cd into that folder. This prevents cross-contamination between client CRM data. For Claude Desktop, you can add multiple MCP servers in the config with different names (ghl-client1, ghl-client2, etc.).