HighLevel MCP Multi-Account Support for Claude

What is HighLevel MCP for Claude?

Key Benefits

Multi-Account Connection Overview

When connecting as an individual user, you authorize Claude to access a single sub-account. This is the default connection mode and works identically to previous MCP implementations — the connection remains tied to that one location for its lifetime.

Agency installations allow you to select multiple sub-accounts during the authorization flow. You can choose one sub-account, several specific locations, or all available sub-accounts under your agency. Claude can then work across only those authorized locations in the same conversation, switching between them as you direct.

During installation, agencies choose which sub-accounts to include. The connection then operates on exactly those sub-accounts and no others. Each request runs against a single sub-account — either the one you name in your prompt, or one Claude identifies through the list_locations tool when the context is ambiguous.

Available MCP Tools

Finds customer or business records by name, email, phone, tag, or similar criteria. This is typically the first tool Claude calls when you ask about existing data.

Retrieves the full details of one or more records returned by search. Use this to get complete information about a contact, opportunity, or other entity.

Discovers available operations by intent (list, create, update, delete, etc.). Claude calls this to find which operations match your request before executing anything.

Inspects an operation's required and optional inputs before running it. This ensures Claude knows what data to pass and in what format.

Runs one operation against the HighLevel API, subject to your OAuth scopes and built-in safety checks. All create, update, and delete actions flow through this tool.

Lists the sub-accounts this connection can access. Claude calls this when the target sub-account is ambiguous or when you ask to see available locations. For single-location connections, this simply returns the one authorized sub-account.

When you ask Claude to "Find the contact with email jane@example.com, add the tag 'vip-2026', and create a new opportunity worth $5,000," Claude uses search to find Jane, search_operations to discover the tag and opportunity operations, describe_operation to inspect their inputs, and execute_operation twice to complete both actions. You receive a single confirmation message.

Authentication Methods

One-click sign-in through the HighLevel consent flow. When you authorize the connection, you review and approve the scopes on the consent screen. OAuth requires no manual token storage or rotation and provides access to the widest set of scopes.

You can review or revoke OAuth access at any time from your HighLevel account settings.

Create a token under Settings → Private Integrations, selecting the scopes you want the token to have. Pass the token in the Authorization header (Bearer pit-your-token) when connecting your MCP client.

A PIT offers a more limited set of scopes compared to OAuth, which may restrict the operations Claude can perform.

In both authentication methods, you choose which scopes to grant the integration. The operations Claude can perform are filtered by these scopes — the assistant can only access data and features your authorization permits.

How to Connect Claude Clients

1. Open Claude.ai and navigate to Settings → Connectors → Add custom connector.
2. Set the server URL to https://services.leadconnectorhq.com/mcp/anthropic/v2.
3. Click Connect and complete the HighLevel sign-in flow (sign in → pick sub-account(s) → approve scopes).
4. Start a new chat. The HighLevel MCP tools are now available.
5. Test the connection by asking: "Find the last 5 contacts I added in HighLevel."

Run this command in your terminal:

Alternatively, add it 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 HighLevel authorization. Verify the connection with claude mcp list.

1. In Claude Cowork, open the connectors / integrations settings.
2. Choose Add custom connector.
3. Set the server URL to https://services.leadconnectorhq.com/mcp/anthropic/v2.
4. Complete the HighLevel sign-in flow (sign in → pick sub-account(s) → approve).

Your Cowork agents can now use the HighLevel MCP tools.

Instead of OAuth, you can pass a Private Integration Token in the Authorization header (Bearer pit-your-token). Create the token under Settings → Private Integrations and select the desired scopes before connecting.

Switching Between Sub-Accounts

You: "Show me the latest opportunities in Downtown Clinic."

Claude retrieves and displays the opportunities for Downtown Clinic.

You: "Now create a contact in Westside Dental."

Claude switches to Westside Dental and creates the contact — no reconnection required.

If you connected to only one sub-account (the default for individual users), list_locations simply returns that location. You don't need to name the sub-account in your requests — Claude always knows which one to use.

Security & Permissions

Available Operations & Coverage

Use the search_operations tool at any time to discover the exact operations available to your grant. Claude can help you explore capabilities by domain or intent (list, create, update, delete, etc.).

Related Articles

Frequently Asked Questions