Connect Claude to GoHighLevel With the Official MCP Server
Want Claude to find leads, summarize CRM records, review opportunities, or help with customer follow-ups? HighLevel's LeadConnector MCP server gives compatible Claude clients a way to work with supported CRM tools through an authorized connection. This guide walks you through setup, permissions, practical prompts, and troubleshooting.
Explore GoHighLevel Official MCP DocumentationWhat Is GoHighLevel MCP for Claude?
MCP stands for Model Context Protocol, an open standard that allows compatible AI applications to connect to external services and use tools exposed by those services.
HighLevel's LeadConnector MCP server allows Claude to work with supported HighLevel operations. After you connect and authorize the integration, Claude can discover available tools and use them within the permissions you grant. Depending on the tools and scopes available, this may include searching contacts, reviewing opportunities, retrieving calendar information, updating records, or carrying out other supported CRM tasks.
The important part is that Claude does not need to know the implementation details of every HighLevel API endpoint. The MCP server provides a structured interface that the assistant can use to discover and execute supported operations.
Search CRM records
Ask Claude to find a contact or retrieve available information using a clear identifier, such as an email address, and summarize the result.
Review opportunities
Where the necessary operations are available, Claude can help find opportunities and prepare summaries for sales or account reviews.
Support follow-up tasks
Use CRM context to draft follow-ups, organize tasks, or prepare next steps. Keep customer-facing actions under human review until the process is tested.
Respect access permissions
OAuth authorization and approved scopes determine which account data and operations the connection can access.
Which Claude Setup Should You Use?
The official LeadConnector MCP server supports several Claude environments. Choose the one that matches how you work.
| Claude environment | Best for | Connection method |
|---|---|---|
| Claude.ai | People who want to work from the Claude web interface without configuring a development environment. | Add a custom connector in Claude settings and authorize LeadConnector. |
| Claude Code | Developers and technical users who work in a terminal or code editor. | Register the remote HTTP MCP server with the Claude Code CLI. |
| Claude Cowork | Supported Cowork workflows that need access to connected CRM tools. | Add a custom connector through the available connectors or integrations settings. |
The endpoint for the Claude-specific connection is:
https://services.leadconnectorhq.com/mcp/anthropic/v2Use the endpoint shown in the current official LeadConnector MCP documentation. Avoid using an endpoint copied from an old tutorial or from a different AI client.
Before You Connect Claude to HighLevel
Make sure you have the following items ready:
- Access to the HighLevel account or sub-account you want Claude to use.
- A Claude environment that supports the relevant custom MCP connector method.
- Permission to authorize the LeadConnector integration and approve its requested scopes.
- A simple test task, such as finding a known test contact.
- A safe way to check results directly in HighLevel before relying on the connection.
For the standard Claude-specific OAuth connection, you do not normally need to create and manually paste a Private Integration Token. Follow the OAuth flow documented for the Anthropic endpoint. The older or general HighLevel MCP connection methods may have different requirements, so don't mix instructions from those setups.
How to Set Up GoHighLevel MCP in Claude.ai
This is the simplest route for most people who want Claude to work with HighLevel records from the web interface.
Open Claude's connector settings
Sign in to Claude.ai. Open Settings, go to Connectors, and choose the option to add a custom connector. The exact label or placement may vary as Claude's interface changes.
Add the LeadConnector MCP endpoint
Enter a clear connector name, such as GoHighLevel CRM, and use the official Claude-specific endpoint:
https://services.leadconnectorhq.com/mcp/anthropic/v2Check the URL carefully before saving. Use the Claude endpoint rather than the OpenAI-compatible endpoint intended for other clients.
Click Connect and sign in to LeadConnector
Claude should initiate the authorization flow. Sign in to the appropriate HighLevel account and check which sub-account or locations the connection is allowed to access.
Review the permissions carefully
Read the requested scopes and approve only the access you need. Depending on the grant, the connection may be able to access read operations and certain create, update, or delete operations. Do not approve broader permissions just to make the connection work if you do not understand why they are required.
Start a new Claude conversation
After authorization, return to Claude and start a new chat. Ensure the connector is available to the conversation. If Claude offers connector or tool selection, make sure the LeadConnector connection is enabled.
Run a read-only test
Try a prompt that should return a known record without changing anything:
Find the last 5 contacts I added in HighLevel. Show the available contact details and do not make any changes.Check the results directly in HighLevel. If Claude cannot find the records, verify the selected location and authorized scopes before trying a more complex request.
How to Connect Claude Code to GoHighLevel MCP
Claude Code is designed for terminal-based development workflows. If you use Claude Code, you can register the remote LeadConnector server from the command line.
Open your terminal
Make sure Claude Code is installed and that you can run the claude command. Open a terminal in the environment where you want to use the connection.
Register the remote server
Run the documented command:
claude mcp add --transport http leadconnector https://services.leadconnectorhq.com/mcp/anthropic/v2This registers a server named leadconnector using HTTP transport. If your installed Claude Code version uses different command options, check its current CLI help and HighLevel's official setup guide.
Complete OAuth authorization
When Claude Code first uses the server, it should prompt you to complete the LeadConnector authorization flow in a browser. Sign in, choose the intended account or location, and review the requested permissions.
Confirm the server is registered
Use the CLI to inspect the connection:
claude mcp listConfirm that leadconnector appears in the list. If the server is registered but cannot connect, inspect its status and authentication flow rather than adding the same server repeatedly.
Test a simple request
Ask Claude Code to find a known test contact without modifying it. Verify the result in HighLevel before allowing any write operation.
For configuration alternatives and current Claude Code commands, refer to the official LeadConnector MCP guide and the Anthropic documentation.
How Claude Cowork Connects to HighLevel
If you use Claude Cowork, HighLevel documents a similar custom connector process:
- Open the connectors or integrations settings in Claude Cowork.
- Choose the option to add a custom connector.
- Enter the Claude-specific LeadConnector MCP URL.
- Complete the HighLevel sign-in and OAuth consent flow.
- Confirm the intended location and permissions.
- Test the connection with a read-only CRM request.
Available features depend on your Claude environment and account. Use the connector controls and current documentation for your version rather than assuming every Claude product has identical settings.
What Can Claude Do With HighLevel MCP?
The current LeadConnector MCP server exposes a compact tool interface for discovering and running supported HighLevel operations. Instead of requiring Claude to select from hundreds of separate tool names, the connection can use tools to discover operations, inspect their requirements, and execute an approved operation.
| MCP tool | Purpose | Example use |
|---|---|---|
list_locations | Identify the sub-accounts the connection can access. | Check which location to use before searching for a contact. |
search_operations | Discover available operations by intent. | Find the supported operation for searching contacts. |
describe_operation | Inspect inputs, required scopes, examples, and safety details. | Check required fields before creating an opportunity. |
execute_operation | Run an operation permitted by the connection. | Search for a test record or perform an approved update. |
The actual operation catalog and available actions depend on your authorization scopes, account permissions, and the active HighLevel implementation. Ask Claude to inspect available operations instead of assuming every possible API action is enabled.
Find contacts and review details
Use clear identifiers to retrieve records and summarize available information. For ambiguous names, ask Claude to show possible matches rather than choosing one automatically.
Inspect opportunities and pipelines
Ask Claude to locate matching opportunities, review current stages, or prepare a pipeline summary where the relevant operations are available.
Draft follow-up messages
Use authorized CRM context to prepare a response for review. Drafting is a safer starting point than immediately sending messages to customers.
Support calendars and appointments
Where supported, Claude can retrieve appointment-related information or help prepare scheduling actions. Verify the calendar, contact, date, and time zone before committing changes.
Update records with approval
Supported write operations can change CRM data when the connection is authorized. Begin with a test record and inspect the final result directly in HighLevel.
Help with other CRM areas
Depending on available operations and scopes, the catalog may include conversations, tasks, custom fields, forms, invoices, workflows, and other HighLevel areas.
Useful Claude Prompts for GoHighLevel
Clear prompts make it easier to control the task and check the result. These examples are starting points. The actions Claude can actually perform depend on the tools available and permissions you have granted.
1. Search for a contact
Search HighLevel for the contact with this email: [test email]. Return the matching record's available name, email, phone, tags, and relevant notes. If there is no exact match or more than one possible match, tell me. Do not change anything.2. Summarize sales opportunities
Find the opportunities in [location] that match [criteria]. Summarize the available opportunity name, current stage, value, and associated contact. Do not update stages, values, or records. Tell me if any requested field is unavailable.3. Draft a lead follow-up
Find the specified lead and review the CRM details that I am authorized to access. Draft a short, personalized follow-up based only on those details. Show me the proposed message and recipient. Do not send it or update the contact.4. Prepare a record update
Find this test contact and show me the current value of [field]. Propose changing it to [new value]. Explain the change and wait for my explicit approval before executing any write operation. After approval, verify the final value.5. Review appointments
Check the supported appointment or calendar information for this contact. Summarize the matching appointments and their time zones. Do not book, cancel, reschedule, or message anyone. If the calendar or time zone is unclear, ask me first.6. Investigate an integration issue
Help me troubleshoot why this HighLevel operation is failing. First identify the operation and required inputs, then review the error and likely permission or data issues. Do not expose credentials, widen permissions, or make changes without asking me.Can Claude Work Across Multiple HighLevel Sub-Accounts?
HighLevel's updated LeadConnector MCP documentation describes multi-account support for agencies. Depending on the connection setup, an agency can authorize access to multiple selected sub-accounts and use the same connection to work across those locations. Each request still operates against a specific selected location.
This is useful if you manage multiple client accounts and want Claude to help with authorized work across them without creating a completely separate connection for every location.
However, multi-account access is not the same as unrestricted access to every account in an agency. You must select the locations included in the authorization and grant the relevant scopes. Claude should identify the intended location before performing a task if your request is ambiguous.
Read the official HighLevel MCP multi-account guide for Claude for the current setup and account-selection details.
Claude MCP vs. HighLevel API, Workflows, and n8n
Claude MCP is not the right answer for every automation. Choose the connection method based on whether you need an AI assistant to interpret flexible requests or a predictable process to run repeatedly.
| Method | Best fit | What to consider |
|---|---|---|
| Claude + MCP | Natural-language CRM research, summaries, and approved tool use. | Results depend on available tools, scopes, prompts, and the selected account. |
| HighLevel API | Custom software and precise, repeatable programmatic operations. | Requires developer setup, authentication, endpoint handling, and error management. |
| HighLevel Workflows | Automations triggered by known events and conditions. | Best when rules and outcomes can be defined in advance. |
| n8n | Multi-step integrations between HighLevel and other apps. | Requires configuration, data mapping, credentials, and error handling. |
| Zapier | Common app connections with limited coding. | App support, task limits, and subscription costs affect the design. |
For example, use a HighLevel workflow when a defined event should always trigger the same follow-up. Use Claude with MCP when a person wants to investigate a CRM record, ask follow-up questions, or prepare a suggested action based on context. Use an API or n8n when you need a controlled multi-step process connecting several systems.
You can combine these approaches rather than choosing only one. For more detail, read our guides to GoHighLevel API, HighLevel workflows, HighLevel automation, and GoHighLevel n8n integration.
Security: Keep Claude's CRM Access Under Control
Connecting an AI assistant to a CRM can expose customer data and allow changes to business records. Treat the integration as a privileged business connection, not simply another chat feature.
- Grant the minimum access needed. Review the requested OAuth scopes and choose permissions appropriate to the use case.
- Start with a test location. Validate behavior against test records before connecting important customer data.
- Separate reading from writing. Begin with searches and summaries. Add write operations only after the read-only workflow works reliably.
- Require approval for consequential actions. Sending messages, deleting data, changing appointments, and modifying important records deserve additional review.
- Verify actions directly. A natural-language confirmation is not a substitute for checking the final record or message in HighLevel.
- Protect sensitive information. Never paste credentials, access tokens, or unnecessary customer data into public chats or repositories.
- Review connected locations. Confirm which sub-accounts are authorized, particularly when managing multiple clients.
- Revoke access when no longer needed. Review connected applications and remove access that is no longer required.
MCP is a connection protocol, not a guarantee that an AI agent will always interpret instructions correctly. Safe operation depends on permissions, tool safeguards, client behavior, and the review process you build around the integration.
For technical integration work, consult the official HighLevel API documentation and the relevant authentication instructions.
GoHighLevel MCP for Claude Troubleshooting
Claude cannot connect to the LeadConnector server
Check that you entered the Claude-specific URL exactly as documented. Confirm that the client supports custom remote MCP connectors, complete the OAuth flow, and inspect any error shown by Claude. If you recently changed access permissions, reconnect using the current authorization flow.
The connector is connected, but Claude cannot see tools
Confirm that the connector is enabled in the conversation or client. Reopen or refresh the connection if needed. Check the authorized scopes and use the current HighLevel documentation to confirm the available tool interface. A connected status does not necessarily mean every possible CRM operation is available.
Claude says it cannot find a contact
Check the email, phone number, or other identifier; verify the selected location; and confirm the record is accessible to the connected user. Ask Claude to report whether it found an exact match instead of guessing between similar records.
Claude can read CRM records but cannot update them
Read and write operations may require different scopes. Check the requested action, the operation's requirements, and the permissions approved during authorization. Only add access that the use case genuinely requires.
Claude is using the wrong sub-account
Make the intended location explicit in your prompt and verify the selected location before any write operation. For multi-account connections, confirm that the correct locations were authorized. Avoid requests such as “update the latest lead” when the intended client account is unclear.
An operation appears successful, but the CRM did not change
Inspect the operation result and check the record directly in HighLevel. Verify the record identifier, selected location, required fields, and any validation error. Do not repeat an action blindly, because doing so may create duplicate records or messages.
OAuth authorization fails
Make sure you sign in to the intended HighLevel account and approve the requested access. If the connection was previously revoked or its access changed, reconnect through the documented OAuth flow. Never solve an authentication problem by pasting a secret into an untrusted prompt.
Should I create a Private Integration Token for Claude?
For the Claude-specific LeadConnector endpoint described in this guide, follow the official OAuth connection flow. Other HighLevel MCP setups may use a different authentication method, so do not mix instructions from the legacy or general MCP endpoint with the Anthropic-specific endpoint.
Does GoHighLevel MCP for Claude Cost Extra?
Do not assume that the MCP connection has a single universal price. Your total cost may depend on your HighLevel plan, Claude plan, and any additional services or automation tools you use.
Before buying a plan specifically for MCP, verify that your account can authorize the connection and access the operations you need. Also consider the cost of maintaining the workflow, reviewing results, and handling exceptions.
Check the current GoHighLevel pricing options and the relevant Claude plan details. Confirm any account-specific requirements before making a purchase.
Frequently Asked Questions
What is the official GoHighLevel MCP URL for Claude?
The Claude-specific LeadConnector MCP endpoint documented by HighLevel is https://services.leadconnectorhq.com/mcp/anthropic/v2. Always confirm the current endpoint in the official documentation before configuring your connector.
Can Claude.ai connect to GoHighLevel without coding?
Yes, the documented Claude.ai setup uses a custom connector and OAuth authorization. You generally do not need to write code for this web-interface setup, though available connector features depend on your Claude account and interface.
Can Claude create or update contacts?
Supported create and update operations may be available when the operation is included in the active MCP catalog and your connection has the necessary scopes. Test with a non-production record first and verify the result directly.
Can Claude send messages through HighLevel?
The MCP operation catalog may include supported conversation and messaging operations. Whether Claude can use a particular send action depends on available tools and authorization. Require human review of the recipient, message, and consent requirements before sending customer communications.
Can agencies use one Claude connection for multiple locations?
HighLevel documents multi-account support for agencies. The connection can work across selected authorized locations where this feature is supported, but each request still targets a specific location. Check the official multi-account guide for current configuration details.
What is the difference between Claude MCP and Claude Code MCP?
Claude.ai connects through its custom connector settings. Claude Code registers the server through the CLI and can use it in a development workflow. Both can connect to the Claude-specific LeadConnector MCP endpoint, but their setup steps differ.
Is MCP better than the HighLevel API?
Neither is universally better. MCP is useful when a compatible AI assistant needs to discover and use tools from natural-language requests. The API is often better for custom applications and precisely controlled programmatic integrations.
Can I use the same connection to build HighLevel apps?
The LeadConnector MCP server is designed for CRM operations. HighLevel also provides a separate Marketplace Developer MCP server for coding assistants working with app development. See the main GoHighLevel MCP server guide for the distinction.
Ready to Connect AI With Your CRM?
Claude MCP can make it easier to investigate CRM records and prepare actions through natural language. Start with one narrow task, use the smallest necessary permissions, and verify every important change before expanding the workflow.
Explore GoHighLevel Read Our GoHighLevel ReviewWe may earn a commission if you purchase through our affiliate link, at no additional cost to you. Verify current features and pricing before purchasing.