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
- Open Claude.ai and go to Settings then Connectors then Add custom connector.
- Enter https://services.leadconnectorhq.com/mcp/anthropic/v2 as the server URL.
- Click Connect and follow the HighLevel sign in flow, selecting subaccounts and approving scopes.
- Start a new chat so the HighLevel MCP tools become available.
- Test the link by asking Claude to find the last five contacts added in HighLevel.
Connect Claude Code (CLI)
- Run claude mcp add --transport http leadconnector https://services.leadconnectorhq.com/mcp/anthropic/v2 in a terminal.
- Optionally add the endpoint to a .mcp.json file at the project root using the provided JSON snippet.
- When Claude Code launches for the first time, a browser opens for HighLevel authorization; complete the sign in and scope approval.
- Confirm the connection works by running claude mcp list.
Connect Claude Cowork
- Open the connectors or integrations settings inside Claude Cowork.
- Select Add custom connector.
- Set the server URL to https://services.leadconnectorhq.com/mcp/anthropic/v2.
- Complete the HighLevel sign in flow, choosing subaccounts and approving scopes.
- 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

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.