Home/HighLevel/Features/AI Employee/HighLevel MCP multi account integration for Claude

AI

HighLevel MCP multi account integration for Claude

In short

The HighLevel Model Context Protocol (MCP) server lets Claude AI assistants read and write data in your HighLevel subaccounts. Agencies connect once and can switch between authorized locations in the same conversation, using natural language to run any of the platform’s operations.

AreaAI Employee · MCP Server
Used forDigital marketing agency, Real estate brokerage, Healthcare clinic network
Setup steps14 steps in 3 tasks
Last updatedNovember 16, 2026

01Who this is for

  • Agency owners who manage several client subaccounts need a single Claude connection to handle all locations without repeated authorizations.
  • Marketing teams that want to tag contacts and create opportunities across multiple locations using plain English commands.
  • Support managers who must look up records or add notes in different subaccounts without leaving their chat window.

02MCP multiaccount support, explained

The MCP server is an integration point that exposes the full HighLevel API to Claude, Claude Code, and Claude Cowork. It uses a standard Anthropic endpoint and accepts either OAuth or a Private Integration Token for authentication. Once authorized, the assistant can call six built in tools to search, fetch, discover operations, describe inputs, execute actions, and list available subaccounts.

Each request runs against a single subaccount, selected by name in the prompt or resolved via the list_locations tool. The connection respects the OAuth or token scopes you grant, and short lived location tokens protect data during execution. All 625 operations across 40 product domains become reachable through natural language.

The MCP settings live in the HighLevel account under Settings. Connectors let you add the custom endpoint, and Private Integrations let you generate tokens if you prefer header authentication.

03How businesses use MCP multiaccount support

  • Digital marketing agency. The agency authorizes Claude for all its client subaccounts during the OAuth flow. An account manager then asks Claude to pull recent leads from a specific client by naming that subaccount, and Claude returns the data without any additional setup.
  • Real estate brokerage. A broker connects Claude Code in a terminal, runs the add command to register the MCP endpoint, and approves the OAuth screen. The broker then runs CLI commands to create new property listings in the appropriate office subaccount by specifying the office name.
  • Healthcare clinic network. Clinic staff use Claude Cowork to add a custom connector, authenticate, and then ask the AI to schedule appointments in a particular clinic location. Claude switches to that subaccount automatically and books the slot.

04The numbers and rules that matter

  • Endpoint URL: Https://services.leadconnectorhq.com/MCP/anthropic/v2.
  • 625 operations across 40 product domains.
  • Security layers include subaccount selection at install, single subaccount per request, scope based authorization and safety checks on destructive actions.

05How to set up and use MCP multiaccount support in HighLevel

Connect Claude.ai

  1. Open Claude.ai and go to Settings then Connectors then Add custom connector.
  2. Enter https://services.leadconnectorhq.com/mcp/anthropic/v2 as the server URL.
  3. Click Connect and follow the HighLevel sign in flow, selecting subaccounts and approving scopes.
  4. Start a new chat so the HighLevel MCP tools become available.
  5. Test the link by asking Claude to find the last five contacts added in HighLevel.

Connect Claude Code (CLI)

  1. Run claude mcp add --transport http leadconnector https://services.leadconnectorhq.com/mcp/anthropic/v2 in a terminal.
  2. Optionally add the endpoint to a .mcp.json file at the project root using the provided JSON snippet.
  3. When Claude Code launches for the first time, a browser opens for HighLevel authorization; complete the sign in and scope approval.
  4. Confirm the connection works by running claude mcp list.

Connect Claude Cowork

  1. Open the connectors or integrations settings inside Claude Cowork.
  2. Select Add custom connector.
  3. Set the server URL to https://services.leadconnectorhq.com/mcp/anthropic/v2.
  4. Complete the HighLevel sign in flow, choosing subaccounts and approving scopes.
  5. Agents in Claude Cowork can now use the HighLevel MCP tools.

06Settings that matter

  • Settings → Connectors → Add custom connector. Defines the custom MCP endpoint that Claude clients will call.
  • Settings → Private Integrations. Allows creation of a Private Integration Token that can be used instead of OAuth.

07Things to know before you rely on it

  • Agency connections can authorize multiple subaccounts, but each request is limited to a single subaccount.
  • Operations are filtered by the OAuth or token scopes you grant, so not all 625 actions may be available.
  • OAuth provides broader scope access than a Private Integration Token.
  • The endpoint is specific to Claude; other MCP clients use a different path.

08If something goes wrong

  • Claude selects the wrong subaccount or cannot determine which one to use. Mention the correct subaccount name in the request or let Claude call the list_locations tool to choose from the authorized locations.
  • Connection fails because required scopes are missing. Review the OAuth scopes or Private Integration Token permissions in HighLevel account settings and grant the needed scopes, then re authorize the connection.

09How it connects to the rest of HighLevel

  • Detailed guide to set up the HighLevel MCP server for Claude and other AI assistants MCP server setup
  • Learn how to automate workflows with HighLevel MCP and n8n integrations MCP automation
  • Review pricing and plan options for HighLevel features Pricing

Michael's take

Michael Reimer
Michael ReimerFounder of CRM Pros, HighLevel Commander and Certified Admin

For a small agency this feature is a huge timesaver. One connection that lets Claude hop between all your client locations means you can automate contacts, opportunities and appointments without logging in to each account separately.

Don’t forget to select every subaccount you need during the initial consent flow.

Get More InformationOpens on HighLevelPublished November 2, 2026 · Updated November 16, 2026

Common questions

Common questions about MCP multiaccount support.

What is the difference between the /mcp/anthropic/v2 endpoint and the original /mcp/ endpoint?

The Anthropic version is built for Claude, offers the full catalog of 625 operations across 40 domains, and adds multi subaccount support for agencies. The original endpoint works with any HTTP MCP client but provides fewer tools and only one subaccount per connection.

Can I connect to multiple subaccounts at once?

Yes, when you install the connection as an agency you can select one, several, or all subaccounts during the authorization flow. Claude can then switch between those locations in the same conversation.

How does Claude know which subaccount to use when I don’t specify one?

If the target subaccount is not clear, Claude calls the list_locations tool to retrieve the authorized locations and asks you to choose. For a single subaccount connection the tool automatically returns the only authorized subaccount.

Should I use OAuth or a Private Integration Token?

OAuth is recommended because it provides one click sign in, a broader set of scopes, and no manual token handling. A Private Integration Token can be used for header authentication but limits the available scopes.

Can Claude access subaccounts I didn’t authorize during installation?

No. The connection is restricted to the subaccounts you selected in the authorization flow. Requests for any other location are rejected, and you must re authorize to add new subaccounts.

Next step

Pick the features that matter. Then get the plan that unlocks them.

Explore the features you want, start with the five at the top, and upgrade through my link when you are ready. The bonuses and the team come with it.

The features directory explains every HighLevel feature in plain English. Browse it to see what the platform can do.

Back to the FeaturesSee the full details
⌃

Site preview

Explore the next page

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