Home/HighLevel/Features/AI Employee/HighLevel Anthropic MCP: full scope OAuth setup for Claude

AI

HighLevel Anthropic MCP: full scope OAuth setup for Claude

In short

The HighLevel MCP for Anthropic is an OAuth based endpoint that gives Claude clients access to the entire HighLevel operation catalog, 625 operations across 40 domains. It uses per client OAuth isolation, user controlled scope selection, and works at the subaccount (location) level.

AreaAI Employee · MCP Server
Used forSaaS startup, Digital marketing agency, Real estate brokerage
Setup steps7 steps in 1 task
Last updatedNovember 17, 2026

01Who this is for

  • Founders who need AI assistants to read and write data across all HighLevel modules, because the endpoint offers the full set of operations.
  • Agency owners managing multiple client locations, as each connection is limited to a single location, keeping data separate.
  • Developers building custom Claude integrations, because the OAuth flow and 5 tool facade simplify secure API access.

02HighLevel MCP for Anthropic, explained

The Anthropic MCP endpoint provides Claude with OAuth based access to every HighLevel operation. Users approve specific scopes on the consent screen, and the system filters operations according to those grants. The integration follows a per client pattern, so scopes granted to Claude do not affect other AI clients.

All calls run through the URL https://services.leadconnectorhq.com/mcp/anthropic/v2. The endpoint enforces the latest v3 API RBAC rules and injects the locationId automatically, ensuring each connection works only for the chosen subaccount. The model interacts with the catalog via five core tools, search, fetch, search_operations, describe_operation, and execute_operation, keeping the context window small.

The endpoint lives in the HighLevel platform under the MCP service. It is accessed by configuring the Claude client’s integration settings, completing the OAuth flow, and selecting the desired location. Once authorized, Claude can discover and execute any operation allowed by the granted scopes.

03How businesses use HighLevel MCP for Anthropic

  • SaaS startup. The team opens Claude.ai, adds the Anthropic MCP endpoint URL, runs the OAuth flow, selects scopes for customer data access, and picks the startup's HighLevel location. Claude can then create, read, and update subscription records directly.
  • Digital marketing agency. An agency user launches Claude Code, inputs the Anthropic endpoint, authorizes scopes for campaign management, and links each client location separately. Claude can automate campaign reporting for each location without cross client data sharing.
  • Real estate brokerage. A broker accesses Claude Cowork, configures the MCP endpoint, grants read/write scopes for property listings, and selects the brokerage's location. Claude assists agents by fetching listing details and updating status within HighLevel.

04The numbers and rules that matter

  • Endpoint URL: Https://services.leadconnectorhq.com/MCP/anthropic/v2.
  • Total operations in catalog: 625.
  • Active operations: 571.
  • Read operations: 243.
  • Write operations: 244.
  • Delete operations: 84.
  • Domains covered: 40.
  • Per client OAuth isolation via dedicated OAuth apps.

05Before you start

  • A supported Claude client (Claude.ai, Claude Code, or Claude Cowork) must be available.

06How to set up and use HighLevel MCP for Anthropic in HighLevel

Set up the HighLevel MCP for Anthropic

  1. Open a supported Claude client and go to its MCP or integrations settings.
  2. Enter the Anthropic specific endpoint URL: https://services.leadconnectorhq.com/mcp/anthropic/v2.
  3. Click the connect or authorize button to start the OAuth flow and be redirected to HighLevel.
  4. On the consent screen, review the list of scopes and select the permissions you wish to grant.
  5. Choose the HighLevel subaccount (location) that the integration should use.
  6. Press Authorize or Allow to finish the OAuth flow, which uses Authorization Code with PKCE and returns a refresh token.
  7. Return to the Claude client and verify that the HighLevel MCP connection appears in the active integrations list.

07Settings that matter

  • OAuth consent screen. Displays the list of scopes requested by the Claude integration and lets the user approve or deny each permission.

08Things to know before you rely on it

  • The Anthropic endpoint provides the widest scope set, covering 625 operations across 40 domains.
  • Each OAuth connection is limited to a single HighLevel location; agency wide connections are not supported.
  • Scopes granted to Claude are isolated from other AI clients through dedicated per client OAuth applications.
  • Operations are automatically filtered based on the granted scopes and RBAC checks.

09How it connects to the rest of HighLevel

Michael's take

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

OAuth isolation adds a layer of security that can catch people off guard; if a token is leaked, only the specific Claude integration is affected, not any other AI clients you might be using. The per client design also means that you have to think about which locations you connect and manage each grant separately.

When you have a supported Claude client, the expanded scope provides access to the full HighLevel operation catalog across 40 domains via the five tool facade.

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

Common questions

Common questions about HighLevel MCP for Anthropic.

What is the difference between the Anthropic endpoint and the original universal endpoint?

The Anthropic endpoint (/mcp/anthropic/v2) exposes the full catalog of 625 operations across 40 domains using a dedicated OAuth app, while the original universal endpoint provides a limited scope surface for general MCP clients.

Can I connect multiple HighLevel locations to Claude?

Yes. Each OAuth connection is tied to a single subaccount (location). To use multiple locations, you must create a separate connection for each one.

How does the 5 tool facade keep the model context small?

Instead of exposing hundreds of individual tools, the MCP surface offers five core tools, search, fetch, search_operations, describe_operation, and execute_operation, allowing Claude to discover and run operations efficiently.

What does per client OAuth isolation mean?

It means the scopes granted to Claude are kept separate from those granted to other AI clients, each using its own dedicated OAuth application to prevent permission leakage.

Will the original universal endpoint be deprecated?

No. The original universal endpoint remains fully supported and continues to work for any MCP client, though it only provides the limited scope surface.

Which Claude clients are currently supported?

The endpoint supports Claude.ai, Claude Code, and Claude Cowork. Additional clients such as OpenAI and VS Code are planned for future support.

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.