Home/HighLevel/AI/Claude with the HighLevel MCP

HighLevel AI · MCP

Claude, connected to HighLevel. Your CRM, run from a conversation.

Can GoHighLevel connect to Claude? Yes. HighLevel's MCP server lets AI assistants like Claude work directly with your HighLevel account: find contacts, read pipelines, create records and take supported actions from plain language. I use it every day to run CRM Pros. Here is how to connect it and use it safely.

  • 625operations
  • 40product domains
  • OAuthsign in, no API keys
A Claude conversation joined to HighLevel contacts, pipelines and calendars by the MCP connector

The short answer

The HighLevel MCP server, also called the LeadConnector MCP server, connects AI assistants including Claude, ChatGPT, Codex and Cursor to your HighLevel account through an OAuth sign in. They can then read and change records in the subaccounts and scopes you approve. The catalog includes 625 read, create, update and delete operations.

Michael is a sponsored HighLevel affiliate. Links to HighLevel use his partner link at no extra cost to you. HighLevel prices and product facts on this page come from HighLevel's own pricing page and help center, checked on the date above.

Connect

Connecting Claude in five steps.

  1. In claude.ai, open Settings, Connectors, and add a custom connector.
  2. Use HighLevel's Claude connection URL: https://services.leadconnectorhq.com/mcp/anthropic/v2
  3. Click Connect and sign in to LeadConnector when prompted.
  4. Select the subaccount or subaccounts to include.
  5. Approve the requested permissions, then ask Claude to list your subaccounts to confirm.

What it can do

Things to ask Claude to do.

Find and summarize

Look up a contact and summarize their history, or list open opportunities in a stage.

Create and update

Add contacts, tags, notes and tasks, or move an opportunity.

Report

Count new leads this week by source, or list appointments for tomorrow.

Chain steps

Find everyone tagged webinar, add a task for each and draft a follow up.

A Claude conversation completing a multi step HighLevel task over MCP: found the contact, moved the opportunity, booked the appointment

Safety

Use it carefully.

  • Approve only the scopes you need
  • Start with read only tasks until you trust the results
  • Ask Claude to show you what it will change before bulk updates
  • Review changes in HighLevel after any bulk action
  • Disconnect access you no longer use

Worked example

What does a working session with Claude and HighLevel look like?

The easiest way to understand the connection is to see a morning with it. These are the kinds of requests I type, in order.

  1. Orient. Work in the main subaccount. How many new contacts came in since Friday, and from which sources?
  2. Review. List the open opportunities in the proposal stage, oldest first, with the last note on each.
  3. Decide. Which of these have had no activity in two weeks?
  4. Act, with a preview. For those, show me the task you would create for the owner. Do not create anything yet.
  5. Confirm. That looks right. Create the tasks, due tomorrow.
  6. Verify. Show me the tasks you created.

Notice the pattern: read first, preview before any change, then check the result. It takes a few minutes and replaces a long session of clicking. For more request patterns, see the AI prompt library.

Limits

What should you not hand to an AI assistant?

An assistant with access to your account is powerful, so decide the limits before you need them.

  • Bulk deletes. Do these yourself, or not at all, after an export.
  • Messages to customers without review. Let it draft. You approve what gets sent.
  • Anything touching consent. Opt outs, do not disturb settings and compliance records should not be changed in bulk by an assistant.
  • Guesses. If the assistant is unsure which record you mean, it should ask. Tell it so.
  • Work in the wrong subaccount. Each request runs against one subaccount. Name it at the start of the session.

Good data makes all of this safer. If your records are messy, clean up your contact data first. And remember that an assistant has the access you approved, so review who on your team can connect one. The user permissions guide covers roles.

Compare

How is this different from Managed Agents and Ask AI?

  • An assistant on MCP works from outside HighLevel, when you ask, across whatever you approve. It is best for analysis, housekeeping and one off jobs.
  • Managed Agents live inside HighLevel and run on their own when a CRM event happens. They are best for jobs that repeat. See the Managed Agents guide.
  • Ask AI is the copilot inside the HighLevel app. It is best for quick help while you are already working there.

They are not competitors. I use the assistant to figure out what should be automated, then build the repeatable part as a Managed Agent in Agent Studio.

The Claude and MCP integration page is the shorter reference for this setup, and the HighLevel MCP server voice agent demo shows the server at work in a video. HighLevel's own AI pricing is in the GoHighLevel AI plans overview, and a 30 day trial through Michael's link gives you an account to connect.

Michael Reimer
Michael's takeFounder of CRM Pros · HighLevel Commander

This changed how I work. Most of my CRM housekeeping now happens in a conversation instead of twenty clicks. Start with questions, then let it take actions once you trust it.

Questions

Common questions.

Can Claude connect to GoHighLevel?

Yes. Claude connects to GoHighLevel through HighLevel's MCP server, also called the LeadConnector MCP server, with an OAuth sign in. Once connected, Claude can read and change records in the subaccounts and scopes you approve. No API key is needed, and Claude acts only when you ask.

What is the HighLevel MCP server URL for Claude?

The HighLevel MCP server URL for Claude is https://services.leadconnectorhq.com/mcp/anthropic/v2. In claude.ai, open Settings, Connectors, and add a custom connector with that URL. Click Connect, sign in to LeadConnector, select the subaccounts to include and approve the requested permissions.

What can Claude do in HighLevel?

Claude can run supported read, create, update and delete operations in HighLevel: 625 operations across 40 product domains. In practice that means finding contacts, reading pipelines, creating records and taking supported actions from plain language. It is limited to the subaccounts and permissions you approve during sign in.

Can I connect multiple subaccounts?

Yes, where the multi subaccount installation is enabled, which HighLevel is still rolling out. Select them during authorization.

Do I need an API key?

No. The HighLevel MCP server uses an OAuth sign in, not an API key. You click Connect in the assistant, sign in to LeadConnector, select the subaccounts to include and approve the requested permissions. The assistant can then work only inside what you approved.

Does Claude act on its own in my HighLevel account?

No. It acts when you ask, inside the subaccounts and permissions you approved during sign in.

Which AI assistants can connect to the HighLevel MCP server?

Claude, ChatGPT, Codex and Cursor are among the assistants that can connect through an OAuth sign in.

How do I keep bulk changes safe?

Start with read only requests, ask for a preview before any bulk update and review the changes in HighLevel afterward.

Does GoHighLevel have an MCP server?

Yes. GoHighLevel has an MCP server, also called the LeadConnector MCP server. It connects AI assistants including Claude, ChatGPT, Codex and Cursor to your HighLevel account through an OAuth sign in. The catalog includes 625 read, create, update and delete operations, limited to the subaccounts and scopes you approve.

Next step

See it in your own account. Thirty days, every feature.

Start a trial, build the first system and test it before the first invoice. Usage fees for phone, SMS, email and AI can apply during the trial.

HighLevel has three plans at a flat monthly price, each with unlimited users and contacts. See what each one includes and what it costs.

Compare the PlansStarter, Unlimited and Founder
⌃

Site preview

Explore the next page

This destination is reserved in the page inventory and is not built yet.