Interact with Live HubDB Data in Meta Muse via CData Connect AI

Muse is Meta's personal AI agent for iOS, Android, and the web, built on the Muse Spark models. It connects to remote model context protocol (MCP) servers, so you can point Muse at a governed data source and let it discover and call live data tools.

Connect Muse to CData Connect AI through its Remote MCP Server, and Muse gains governed, real-time access to live HubDB data. You can explore data, fetch records, and interact with objects using natural language prompts, with every request running against authorized sources.

This article shows you how to configure HubDB connectivity in Connect AI, generate a personal access token, create a custom connector to the Connect AI Remote MCP Server in Muse, and interact with live HubDB data from Muse.

Step 1: Configure HubDB connectivity for Meta Muse

Connectivity to HubDB from Muse is made possible through Connect AI's Remote MCP Server. To interact with HubDB data from Muse, start by creating and configuring a HubDB connection in Connect AI.

1. Log into Connect AI, click Sources, and then click Add Connection

2. Select HubDB from the Add Connection panel

3. Enter the necessary authentication properties to connect to HubDB.

   There are two authentication methods available for connecting to HubDB data source: OAuth Authentication with a public HubSpot application and authentication with a Private application token.

   Using a Custom OAuth App

   AuthScheme must be set to "OAuth" in all OAuth flows. Be sure to review the Help documentation for the required connection properties for you specific authentication needs (desktop applications, web applications, and headless machines).

   Follow the steps below to register an application and obtain the OAuth client credentials:

   1. Log into your HubSpot app developer account.
      • Note that it must be an app developer account. Standard HubSpot accounts cannot create public apps.
   2. On the developer account home page, click the Apps tab.
   3. Click Create app.
   4. On the App info tab, enter and optionally modify values that are displayed to users when they connect. These values include the public application name, application logo, and a description of the application.
   5. On the Auth tab, supply a callback URL in the "Redirect URLs" box.
      • If you're creating a desktop application, set this to a locally accessible URL like http://localhost:33333.
      • If you are creating a Web application, set this to a trusted URL where you want users to be redirected to when they authorize your application.
   6. Click Create App. HubSpot then generates the application, along with its associated credentials.
   7. On the Auth tab, note the Client ID and Client secret. You will use these later to configure the driver.

   8. Under Scopes, select any scopes you need for your application's intended functionality.

      A minimum of the following scopes is required to access tables:

      • hubdb
      • oauth
      • crm.objects.owners.read
   9. Click Save changes.
   10. Install the application into a production portal with access to the features that are required by the integration.
       • Under "Install URL (OAuth)", click Copy full URL to copy the installation URL for your application.
       • Navigate to the copied link in your browser. Select a standard account in which to install the application.
       • Click Connect app. You can close the resulting tab.

   Using a Private App

   To connect using a HubSpot private application token, set the AuthScheme property to "PrivateApp."

   You can generate a private application token by following the steps below:

   1. In your HubDB account, click the settings icon (the gear) in the main navigation bar.
   2. In the left sidebar menu, navigate to Integrations > Private Apps.
   3. Click Create private app.
   4. On the Basic Info tab, configure the details of your application (name, logo, and description).
   5. On the Scopes tab, select Read or Write for each scope you want your private application to be able to access.
   6. A minimum of hubdb and crm.objects.owners.read is required to access tables.
   7. After you are done configuring your application, click Create app in the top right.
   8. Review the info about your application's access token, click Continue creating, and then Show token.
   9. Click Copy to copy the private application token.

   To connect, set PrivateAppToken to the private application token you retrieved.

   
4. Click Save & Test
5. Navigate to the Permissions tab and update user-based permissions

Add a Personal Access Token

A Personal Access Token (PAT) is used to authenticate the connection to Connect AI from Muse. It is best practice to create a separate PAT for each integration to maintain granular access control.

1. Click the gear icon () at the top right of the Connect AI app to open Settings
2. On the Settings page, go to the Access Tokens section and click Create PAT
3. Give the PAT a descriptive name and click Create

4. Copy the token when displayed and store it securely. It will not be shown again

With the HubDB connection configured and a PAT generated, Muse can now connect to HubDB data through Connect AI.

Step 2: Create a custom connector to the Connect AI MCP Server in Meta Muse

Muse has no manual "add MCP server" form. Instead, you ask Muse in plain language to build a custom connector that points at the Connect AI Remote MCP Server, a hosted, public HTTPS endpoint that speaks streamable HTTP. Muse builds the connector on its secure VM using the official MCP SDK, then discovers and calls the available Connect AI data tools.

1. Open Muse on iOS, Android, or the web and start a new chat
2. Ask Muse to build a custom connector to the Connect AI Remote MCP Server, giving it the server URL and noting that the endpoint is a hosted MCP server over streamable HTTP, for example:
   Create a custom connector to CData Connect AI. It is a hosted MCP server over streamable HTTP at https://mcp.cloud.cdata.com/mcp and it requires an Authorization header.
3. When Muse prompts for credentials, it opens a secure entry flow, separate from the chat, that saves the value in its Secure Credentials Store. Enter the Authorization header value in the format Basic your_base64_encoded_email_PAT

   Note: For the Authorization value, base64 encode email:PAT and prefix it with Basic. Enter it only in Muse's secure credential prompt, never in the chat.

4. Muse connects to the Connect AI MCP Server and lists the available data tools. Review the custom connector confirmation, then click Continue. When Muse offers to save the integration as a skill, choose yes so the connector is available in every future chat

With the custom connector saved, the Connect AI tools are available to Muse in any chat.

Step 3: Interact with live HubDB data from Meta Muse

With the integration complete, interact with live HubDB data directly from Muse through natural language prompts.

1. In a Muse chat, type a prompt that uses the Connect AI connector, for example:
   • Use the CData Connect AI connector to list all available connections
   • Show the available objects and fields for HubDB
   • Fetch the top 5 records from HubDB
2. Approve the tool call in the Sentinel dialog when prompted
3. Muse calls the Connect AI MCP Server and returns live results from HubDB data

At this point, Muse communicates with the Connect AI MCP Server and retrieves live HubDB data through remote MCP tools directly from your chats.

Get started with CData Connect AI

With CData Connect AI, interact with hundreds of SaaS, big data, and NoSQL sources directly from your AI agents, models, and cloud applications. To explore more download a free 14-day trial today. Our Support Team is available to help with any questions you have.