Home/HighLevel/Features/Getting Started with HighLevel/How to connect HighLevel MCP to Muse and configure access

Agency, Settings and Integrations

How to connect HighLevel MCP to Muse and configure access

In short

HighLevel MCP for Muse creates a secure OAuth link that lets Muse use approved HighLevel functions. After selecting subaccounts and approving scopes, Muse can retrieve and modify records across contacts, calendars, opportunities and other domains without separate integrations.

AreaGetting Started with HighLevel · Foundational Setup
Used forDigital marketing agency, Health care clinic, Real estate brokerage
Setup steps11 steps in 1 task
Last updatedNovember 17, 2026

01Who this is for

  • Founders who run multiple subaccounts benefit from granting Muse limited access without sharing full credentials.
  • Marketing teams can let Muse automate contact outreach while controlling which data fields are exposed.
  • Operations managers can enable Muse to schedule appointments and track opportunities using the same platform data.

02HighLevel MCP for Muse, explained

HighLevel MCP for Muse is an app that connects the Muse platform to HighLevel through an OAuth flow. The connection lets Muse discover and call supported services such as contacts, conversations, calendars, opportunities, payments, locations and custom fields.

When the user authorizes the link, Muse receives a token that permits up to 600+ operations across 38 domains. The exact actions Muse can perform depend on the OAuth scopes approved during setup. All interactions are routed through four unified MCP tools, simplifying calls from Muse to HighLevel.

03How businesses use HighLevel MCP for Muse

  • Digital marketing agency. The agency connects Muse to the client’s HighLevel subaccount, selects only the contacts and campaigns scopes, and then uses Muse to draft and send personalized messages based on platform data.
  • Health care clinic. The clinic authorizes Muse with calendar and appointment scopes, allowing Muse to view available slots and schedule patient visits directly from the AI interface.
  • Real estate brokerage. The brokerage links Muse to its HighLevel opportunities domain, approves the necessary scopes, and lets Muse pull property lead information and update deal stages within the platform.

04The numbers and rules that matter

  • OAuth endpoint: Https://services.leadconnectorhq.com/MCP/muse/v2/.
  • 600+ supported operations.
  • 38 CRM domains.

05Before you start

  • Be logged into a HighLevel user account that has access to the desired subaccount.
  • Have Muse open and ready to initiate an app connection.

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

Connect HighLevel MCP to Muse

  1. Open Muse and find the option to add an app or MCP service.
  2. Choose HighLevel from the list of available apps.
  3. Enter the Muse specific endpoint https://services.leadconnectorhq.com/mcp/muse/v2/ when asked for the MCP connection.
  4. Begin the HighLevel authorization flow.
  5. Log in to HighLevel if the system prompts for credentials.
  6. Examine the HighLevel OAuth consent screen that appears.
  7. Pick the subaccount or subaccounts that Muse should access.
  8. Check the listed OAuth scopes and verify they match the needed access.
  9. Always review the requested OAuth scopes before approving the connection.
  10. Confirm the authorization to grant the requested permissions.
  11. Return to Muse and verify that HighLevel appears as a connected service.

07Settings that matter

  • OAuth scopes. Define which HighLevel resources and actions Muse is permitted to use after the connection is authorized.
  • Sub, account(s) selection. Specifies which HighLevel subaccounts Muse can interact with once the OAuth flow completes.

08Things to know before you rely on it

  • Only the operations covered by the approved OAuth scopes are available to Muse; the full set of 600+ actions is not granted automatically.
  • OAuth scopes control external app access and are separate from HighLevel user roles and permissions.

09If something goes wrong

  • The desired HighLevel subaccount does not appear during selection.. Confirm that the HighLevel user completing the OAuth flow has access to that subaccount according to their role and data restrictions.
  • Need to remove Muse’s access after it has been granted.. Navigate to Settings > Connected Apps in HighLevel and revoke the Muse application entry.

10How it connects to the rest of HighLevel

Michael's take

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

You need a way for AI driven tools like Muse to talk to your HighLevel account without handing out passwords or building dozens of separate integrations. The OAuth link that HighLevel MCP for Muse provides solves that by giving Muse only the permissions you approve, keeping your data safe while unlocking many actions.

The first setting I would lock down is the scope selection. Approve only the exact resources Muse needs. Contacts, calendars, or payments. So you keep tight control over what the AI can see or change. After that, run a quick test in Muse to confirm the connection shows as active and that the expected operations work.

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

Common questions

Common questions about HighLevel MCP for Muse.

Do I need a private integration token to connect HighLevel to Muse?

No. The Muse connection uses a dedicated HighLevel MCP endpoint and follows the OAuth flow presented within Muse.

What determines which HighLevel operations Muse can perform?

The set of operations available to Muse depends on the OAuth scopes you approve during the authorization step.

Can Muse update data in HighLevel?

Yes, when the approved scopes include write permissions, Muse can perform supported actions such as updating records.

Why should I review OAuth scopes before connecting?

Reviewing scopes lets you see exactly which HighLevel resources and actions Muse is requesting, ensuring you grant only the access you intend.

How can I revoke Muse’s access later?

You can revoke access from the Connected Apps section in HighLevel settings, removing Muse’s permission to the platform.

Are OAuth scopes the same as HighLevel user permissions?

No. OAuth scopes govern what an external app like Muse can do, while user permissions control what an individual HighLevel user can access inside a subaccount.

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.