Connect your AI assistant to HighLevel so it can find CRM records and perform supported actions from your instructions. The HighLevel MCP Server, also called the LeadConnector MCP Server, connects through OAuth: sign in, choose the sub-account or sub-accounts to include, and approve the requested permissions.

This guide covers setup for Claude, ChatGPT, Codex, Cursor, Muse, and Grok Bot, along with how to work across authorized sub-accounts and discover available operations.

TABLE OF CONTENTS

• What is the HighLevel MCP Server?
• Key benefits of the HighLevel MCP Server
• Before You Connect
• How to connect your AI client
  • Claude.ai
  • Claude Code
  • Claude Cowork
  • ChatGPT
  • Codex
  • Cursor
  • Muse
  • Grok Bot
• Confirm your connection
• Working with One or Multiple Sub-accounts
• How the Four MCP Tools Work
• What you can do
• Example: complete a task from one prompt
• Permissions and security
• Frequently asked questions
• Technical Reference

What is the HighLevel MCP Server?

MCP stands for Model Context Protocol. It gives AI assistants a standard way to discover and use tools from connected applications. With the HighLevel MCP Server, your assistant can work with supported CRM data and actions without you needing to know the underlying API.

The active catalog includes more than 550 read, create, update, and delete operations across 38 domains. The operations available to your connection depend on the OAuth scopes and permissions you approve.

Before You Connect

You need access to the HighLevel sub-account or sub-accounts you want to connect and a supported AI client. For a custom MCP connection, use the URL for your client below. Muse and Grok Bot offer officially listed apps.

These connections use OAuth. During authorization, sign in to LeadConnector, select the available sub-account(s), and approve the requested scopes. All connection options use the current active LeadConnector MCP operation catalog.

How to connect your AI client

Claude.ai

Watch the Claude setup walkthrough

1. Open Claude.ai → Settings → Connectors → Add custom connector.
   
   

2. Enter this server URL:

   https://services.leadconnectorhq.com/mcp/anthropic/v2

3. Click Connect and complete the LeadConnector sign-in and consent flow.
   
   

4. Choose the sub-account(s) to connect and approve access.
   
   

5. Start a new chat to use the LeadConnector tools.

Claude Code

Run this command in your terminal:

claude mcp add --transport http leadconnector https://services.leadconnectorhq.com/mcp/anthropic/v2

Alternatively, add this configuration to .mcp.json at your project root:

{
  "mcpServers": {
    "leadconnector": {
      "type": "http",
      "url": "https://services.leadconnectorhq.com/mcp/anthropic/v2"
    }
  }
}

On first use, Claude Code opens a browser for LeadConnector authorization. Sign in, select the sub-account(s), and approve access. Verify the connection with:

claude mcp list

Claude Cowork

1. Open the connectors / integrations settings in Claude Cowork.
   
   

2. Choose Add custom connector.
   
   

3. Enter https://services.leadconnectorhq.com/mcp/anthropic/v2.
   
   

4. Complete the LeadConnector OAuth flow: sign in, choose the sub-account(s), and approve access.

Your Cowork agents can then use the LeadConnector tools.

ChatGPT

Watch the ChatGPT setup walkthrough

1. Open Settings → Security and login in ChatGPT and turn on Developer mode.
   
   

2. Open ChatGPT Plugins, select the plus button, and create a new plugin.
   
   

3. Enter a name and description. Under Connection, add this MCP server URL and create the connection:

   https://services.leadconnectorhq.com/mcp/openai/v2/

4. Complete the LeadConnector OAuth flow: sign in, choose the sub-account(s), and approve access.
   
   

5. Start a new conversation and add the LeadConnector connection from the tools menu.

Codex

Add the server and start OAuth authorization:

codex mcp add leadconnector --url https://services.leadconnectorhq.com/mcp/openai/v2/
codex mcp login leadconnector

In the Codex IDE extension, open the gear menu → MCP servers → Add server, choose Streamable HTTP, and enter the same URL. Select Authenticate when prompted to complete OAuth.

Other compatible OpenAI clients can use this URL as a remote Streamable HTTP MCP server and complete the LeadConnector OAuth flow when prompted.

Cursor

Add this configuration to .cursor/mcp.json in your project, or to ~/.cursor/mcp.json to make the connection available across projects:

{
  "mcpServers": {
    "leadconnector": {
      "url": "https://services.leadconnectorhq.com/mcp/cursor/v2"
    }
  }
}

If you already have other servers configured, add the leadconnector entry to the existing mcpServers object.

Complete the LeadConnector OAuth flow when Cursor prompts you: sign in, choose the sub-account(s), and approve access.

Muse

Watch the Muse setup walkthrough.

LeadConnector is available as an official app in Muse. Connect the app and complete the LeadConnector OAuth flow:

sign in, choose the sub-account(s), and approve access.

Muse uses https://services.leadconnectorhq.com/mcp/muse/v2/ for its OAuth connection.

Grok Bot

Watch the Grok Bot setup walkthrough.

1. Open Grok Bot → Connect apps.
   
   

2. Search for HighLevel and choose Add.
   
   

3. Complete the LeadConnector OAuth flow: sign in, choose the sub-account(s), and approve access.

To attach the app to a specific task, you can type @ in chat and select HighLevel.

Confirm Your Connection

Start with a simple request:

Find the last 5 contacts I added in HighLevel.

Your assistant can discover the available contact operations and retrieve records within the permissions you granted. 

For an agency connection, name the sub-account you want to use.

Working with One or Multiple Sub-accounts

Single sub-account

A single-sub-account connection is bound to the sub-account you choose during OAuth authorization for the lifetime of that connection.

Agency connection

Where agency-wide access is available, you can connect once and work across the sub-accounts selected during installation.

1. Choose the sub-accounts during installation. Select one, several, or all of the sub-accounts offered by the agency installation.
   
   

2. Name the sub-account in your request. If the intended sub-account is unclear, the assistant uses list_locations and asks you to choose.
   
   

3. Switch within the same chat. Ask about another authorized sub-account without reconnecting.

For example:

List the contacts tagged “vip-2026” in Downtown Clinic, then compare the count with Uptown Med Spa.

The assistant resolves the sub-account names, queries each sub-account separately, and compares the results. Every request targets one sub-account and is authorized against your installation. The connection cannot access sub-accounts you did not include.

Availability: Single-sub-account connections are available today. Agency-wide connections are rolling out through the multi-sub-account, or bulk, installation option. If installation offers only one sub-account, the multi-sub-account option is not enabled for your app yet.

Watch the multiple-sub-account walkthrough.

How the Four MCP Tools Work

The server exposes four unified tools. Your assistant uses these tools to find and run the operations available to your connection.

You can ask your assistant to use search_operations to check what is available to your connection at any time.

What You Can Do

The active catalog covers the following areas. Availability depends on your OAuth scopes and permissions.

Example: complete a task from one prompt

After connecting, you can give your assistant a request such as:

Find the contact with email jane@example.com, add the tag “vip-2026”, and create an opportunity for them in “Sales Pipeline” worth $5,000.

The assistant uses search_operations to discover the contact lookup, tagging, and opportunity operations. It checks their inputs, scopes, and safety information with describe_operation, then uses execute_operation to find the contact and perform the supported actions. It reports the results back in natural language.

Permissions and Security

• You select the sub-accounts. Each request is authorized against the installation and can access only a sub-account included in that connection.
  
  

• OAuth scopes limit actions. The assistant can perform only the operations allowed by your grant.
  
  

• Sensitive actions have additional checks. Sensitive and irreversible operations are subject to confirmation and safety checks before execution.
  
  

• You control ongoing access. Review or revoke the connection's access from your LeadConnector account.

Frequently Asked Questions

Q: Do I need a Private Integration Token?

The client connections in this guide use OAuth. Complete the LeadConnector sign-in and consent flow to authorize access; you do not need to manually create or rotate a token for these connections.

Q: Which server URL should I use?

Use the URL for your client in the connection table above. Claude clients use the Anthropic endpoint, ChatGPT and Codex use the OpenAI endpoint, and Cursor uses its own endpoint. Muse and Grok Bot also offer officially listed apps.

Q: Why do I see four tools instead of hundreds?

The four tools let the assistant discover and run the active operation catalog. Individual CRM operations are found through search_operations, inspected through describe_operation, and run through execute_operation.

Q: How many operations are available?

The active catalog includes more than 550 operations across 38 domains. Your connection can use only the operations allowed by its OAuth scopes and permissions. Ask your assistant to search for the operation you need.

Q: Can my assistant create, update, or delete records?

Yes, where the operation is supported and your OAuth grant permits it. Sensitive and irreversible actions also have confirmation and safety checks.

Q: Can I use one connection for several sub-accounts?

Agencies can use a multi-sub-account installation where it is enabled. Each operation still runs against one authorized sub-account. If installation only offers a single sub-account, the multi-sub-account option is not yet enabled for your app.

Q: Can the assistant access a sub-account I did not select?

No. Requests outside the sub-accounts included in the installation are refused.

Q: How do I remove access?

Review or revoke the integration's access from your LeadConnector account.

Technical Reference

For the source documentation, see LeadConnector MCP Server in the HighLevel Marketplace documentation.