The MCP Server is available for connecting Muse to supported CRM capabilities through Model Context Protocol (MCP). The connection uses OAuth, allowing you to review the requested permissions before granting access.


Once authorized, Muse can access 600+ supported operations across 38 CRM domains through four unified MCP tools, depending on the scopes you approve.

TABLE OF CONTENTS

What is MCP for Muse?


MCP for Muse creates a secure connection between Muse and 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 separate integrations for each CRM function.


The MCP Server supports services such as Contacts, Conversations, Calendars, Opportunities, Payments, Locations, and Custom Fields.


With the Muse integration, authentication uses OAuth through a dedicated MCP endpoint:


https://services.leadconnectorhq.com/mcp/muse/v2/


During authorization, you review and approve the requested OAuth scopes. These scopes determine which CRM data and functionality Muse can access.

Key Benefits of MCP for Muse


Connecting the MCP Server to Muse provides controlled access to supported CRM capabilities while maintaining visibility into the permissions being requested.


OAuth scopes help limit access to the specific resources and actions authorized during setup.

  • OAuth-Based Connection: Authenticate through the authorization process without manually configuring credentials for the Muse connection.

  • Granular Access Control: Approve OAuth scopes that determine which CRM resources and actions Muse can access.

  • Broad CRM Coverage: Access 600+ supported operations across 38 CRM domains.

  • Unified MCP Access: Access supported operations through four unified MCP tools, simplifying how Muse interacts with CRM services.

  • Permission Visibility: Review the requested OAuth scopes and understand the access being requested before authorizing the connection.

How OAuth Permissions Work with Muse


OAuth allows external applications to request access to specific CRM resources without requiring you to share your 

account credentials directly with those applications.


Reviewing the requested OAuth scopes helps you understand which resources Muse can access and what types of actions may be available.


When you connect MCP to Muse, the OAuth authorization process presents the permissions, or scopes, requested by the application.


The consent screen displays the requested scopes so you can review the permissions before granting access.


OAuth scopes and user permissions serve different purposes:

  • OAuth scopes control which resources and actions the Muse connection is authorized to access.

  • User roles and permissions control which features and information an individual user can access.

  • Assigned data restrictions can further limit which records a user can view or manage.


Admin and User roles, granular module permissions, and assigned data restrictions help control individual user access. Always review the requested OAuth scopes before approving the connection.

Supported MCP Operations


MCP allows compatible AI clients to work with supported CRM services through a standardized connection instead of requiring separate integrations for each function. The Muse integration provides access to 600+ supported operations across 38 CRM domains through four unified MCP tools.


The operations available to Muse depend on the OAuth scopes approved during authorization. The MCP Server supports services including:

  • Contacts

  • Conversations

  • Calendars

  • Opportunities

  • Payments

  • Locations

  • Custom Fields


Depending on the available tools and granted permissions, MCP-compatible clients can:

  • Retrieve contact and other supported records.

  • Create or update supported data.

  • Send supported messages.

  • Search opportunities.

  • Access calendar information.

  • Perform other authorized CRM actions.


The exact operations available to Muse depend on the permissions granted to the connection. Approve only the scopes required for your intended use case.

How To Set Up MCP for Muse


Connecting MCP to Muse requires completing the OAuth authorization process and reviewing the permissions requested by Muse. Use the following steps to configure the connection.


Step 1: Open Muse


Open Muse and locate the option to connect an application or MCP service.


Step 2: Select the MCP Integration


Locate and select the CRM integration you want to connect.


Step 3: Enter the MCP Endpoint


When prompted for the MCP connection endpoint, enter the Muse-specific URL:


https://services.leadconnectorhq.com/mcp/muse/v2/


Use this dedicated endpoint for the Muse integration.


Step 4: Start Authorization


Begin the OAuth authorization process. Sign in to your CRM account if prompted.


Step 5: Review the Authorization Request


Review the OAuth authorization screen. The consent experience displays the requested scopes so you can understand the permissions being requested before approving access.


Step 6: Review OAuth Scopes


Review the requested OAuth scopes and confirm that they match the access you want Muse to have. Only approve permissions required for your intended use case.


Step 7: Approve the Connection


Approve the authorization request to grant Muse the requested access.


Step 8: Confirm the Connection


Return to Muse and verify that the integration appears as connected. After successful authorization, Muse can use the supported MCP operations available through the scopes you approved.

Frequently Asked Questions


Do I need a Private Integration Token to connect MCP to Muse?

The Muse connection described in this article uses a dedicated MCP endpoint and OAuth authorization.

Follow the OAuth process presented through Muse rather than the generic token-based setup documented for other MCP client configurations.


Can Muse make changes to CRM data?

The MCP Server supports retrieving information and performing authorized actions, including updating supported data. Whether a specific action is available through Muse depends on the approved scopes and supported operation.


Why do I need to review OAuth scopes before connecting?

OAuth scopes identify the resources and actions that an external application requests permission to access. Reviewing them helps you understand which permissions you are granting before completing authorization.


Why can't I access the CRM information I expect through Muse?

Verify that the user completing authorization has the appropriate permissions to access the required CRM information. Also confirm that the approved OAuth scopes allow the requested operations. User roles, permissions, and assigned data restrictions can affect access to specific resources and records.


Are OAuth scopes the same as user permissions?

No. OAuth scopes control the permissions granted to an external application. User roles and permissions control which features and information an individual user can access. These are separate access controls.


Does every Muse connection automatically receive all 600+ operations?

No. The integration supports 600+ operations across 38 CRM domains, but the operations available to a connection depend on the scopes approved during authorization.