HighLevel MCP is now available as an official app in Muse, giving Muse access to approved HighLevel CRM capabilities through Model Context Protocol (MCP). The connection uses OAuth, allowing you to choose the CRM sub-account(s) you want to connect and review the permissions requested before granting access. Once authorized, Muse can access 600+ supported operations across 38 CRM domains through four unified MCP tools, based on the scopes you approve.
TABLE OF CONTENTS
- What is HighLevel MCP for Muse?
- Key Benefits of HighLevel MCP for Muse
- How OAuth Permissions Work with Muse
- Supported HighLevel Operations
- How To Set Up HighLevel MCP for Muse
- Frequently Asked Questions
- Related Articles
What is HighLevel MCP for Muse?
HighLevel MCP for Muse creates a secure connection between Muse and HighLevel so Muse can interact with supported CRM services using Model Context Protocol. MCP provides a standardized way for compatible AI clients to discover available capabilities, retrieve information, and perform approved actions without requiring users to build separate integrations for each CRM function. HighLevel's MCP Server supports CRM services such as Contacts, Conversations, Calendars, Opportunities, Payments, Locations, and Custom Fields.
With the Muse integration, authentication is completed using OAuth through a dedicated HighLevel MCP endpoint:
https://services.leadconnectorhq.com/mcp/muse/v2/
During authorization, you select the CRM sub-account(s) Muse can connect to and approve the requested scopes. These scopes determine which HighLevel data and functionality Muse is authorized to access.
Key Benefits of HighLevel MCP for Muse
Connecting HighLevel to Muse gives you a controlled way to make supported CRM capabilities available to Muse while retaining visibility into the permissions being requested. OAuth scopes help limit access to the specific HighLevel resources and actions authorized during setup.
OAuth-based connection: Authenticate through HighLevel without manually configuring credentials for the Muse connection.
Sub-account selection: Choose the CRM sub-account(s) you want to make available during authorization.
Granular access control: Approve OAuth scopes that determine the HighLevel resources and actions Muse can access.
Broad CRM coverage: Access 600+ supported operations across 38 CRM domains.
Unified MCP access: Supported operations are exposed through four unified MCP tools, simplifying how Muse interacts with HighLevel.
Permission visibility: HighLevel's OAuth experience displays requested scopes so users can review the permissions an external application is requesting before authorizing it.
How OAuth Permissions Work with Muse
OAuth allows an external application to request access to specific HighLevel resources without requiring you to share account credentials directly with that application. Reviewing requested scopes before authorization helps you understand which areas of HighLevel Muse will be able to use and what types of actions may be available.
When you connect HighLevel to Muse, the OAuth authorization flow presents the permissions, or OAuth scopes, being requested. HighLevel's OAuth consent experience is designed to show users the requested permissions and explain what those permissions allow before access is granted.
OAuth scopes should not be confused with HighLevel user permissions:
OAuth scopes control what the Muse connection is authorized to access.
User roles and permissions control what an individual HighLevel user can access within a sub-account.
Assigned data restrictions can further limit which records a HighLevel user can view or manage. HighLevel supports Admin and User roles as well as granular module permissions and assigned-data restrictions.
Always review the requested OAuth scopes before approving the connection.
Supported HighLevel Operations
MCP allows compatible AI clients to work with HighLevel services through a standardized connection instead of requiring a separate integration for every supported CRM function. The Muse integration provides access to 600+ supported operations across 38 CRM domains through four unified MCP tools, with actual access determined by the OAuth scopes you approve.
HighLevel's general MCP Server supports services including:
Contacts
Conversations
Calendars
Opportunities
Payments
Locations
Custom Fields
HighLevel's MCP documentation also explains that MCP-compatible clients can retrieve records, update data, send messages, search opportunities, access calendar information, and perform other supported actions when appropriate access is available.
The exact operations available to Muse depend on the permissions granted to the connection. Approving only the scopes you need helps keep access aligned with your intended use case.
How To Set Up HighLevel MCP for Muse
A successful setup requires completing HighLevel's OAuth authorization flow, selecting the correct CRM sub-account(s), and reviewing the scopes requested by Muse. Confirming these settings during setup helps ensure Muse receives the intended level of CRM access.
Open Muse and locate the option to connect an app or MCP service.
Select HighLevel as the app you want to connect.
When prompted for the HighLevel MCP connection, use the Muse-specific endpoint:
Start the HighLevel authorization process.
Sign in to HighLevel if prompted.
Review the HighLevel OAuth authorization screen.
HighLevel's OAuth consent experience displays the application's requested scopes so you can understand the permissions being requested before approving access.
Select the CRM sub-account(s) you want to connect to Muse.
Review the requested OAuth scopes and confirm that they match the access you want Muse to have.
Approve the authorization request.
Return to Muse and confirm that HighLevel shows as connected.
Muse can now use the HighLevel operations available through the scopes you approved.
Frequently Asked Questions
Q: Do I need a Private Integration Token to connect HighLevel to Muse?
The Muse connection described here uses a dedicated HighLevel MCP endpoint and an OAuth authorization flow. Follow the OAuth process presented through Muse rather than the generic token-based setup documented for other HighLevel MCP client configurations.
Q: What determines which HighLevel operations Muse can use?
The available operations depend on the OAuth scopes approved during authorization. Scopes define which HighLevel resources and actions an external application can access.
Q: Can Muse make changes to data in HighLevel?
HighLevel's MCP Server supports both retrieving information and performing supported actions, including updating data, when the required access is available. Whether a specific action is available through Muse depends on the approved scopes and supported operation.
Q: Why do I need to review OAuth scopes before connecting?
OAuth scopes identify the HighLevel resources and actions an external application is requesting. Reviewing them helps you understand the access you are granting before completing authorization.
Q: Why can't I see the HighLevel sub-account I want to connect?
First verify that the HighLevel user completing authorization has access to the expected sub-account. HighLevel user roles and permissions determine what a user can access within individual sub-accounts.
Q: Are OAuth scopes the same as HighLevel user permissions?
No. OAuth scopes control the permissions granted to an external application, while HighLevel user roles and permissions control what an individual user can access inside a sub-account.
Q: Can I revoke Muse's access later?
HighLevel recommends regularly reviewing connected applications and revoking access to applications that are no longer needed. Connected application access can be reviewed from Settings > Connected Apps in HighLevel.
Q: Does every Muse connection automatically receive all 600+ HighLevel operations?
No. The integration supports 600+ operations across 38 CRM domains, but the operations available to a connection are based on the scopes approved during authorization.
Related Articles
Was this article helpful?
That’s Great!
Thank you for your feedback
Sorry! We couldn't be helpful
Thank you for your feedback
Feedback sent
We appreciate your effort and will try to fix the article