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

Use the CData Connect AI Remote MCP Server to enable Muse to securely interact with live AlloyDB data.

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 AlloyDB 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 AlloyDB 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 AlloyDB data from Muse.

Step 1: Configure AlloyDB connectivity for Meta Muse

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

  1. Log into Connect AI, click Sources, and then click Add Connection
  2. Adding a connection in Connect AI
  3. Select AlloyDB from the Add Connection panel
  4. Selecting data source
  5. Enter the necessary authentication properties to connect to AlloyDB.

    The following connection properties are usually required in order to connect to AlloyDB.

    • Server: The host name or IP of the server hosting the AlloyDB database.
    • User: The user which will be used to authenticate with the AlloyDB server.
    • Password: The password which will be used to authenticate with the AlloyDB server.

    You can also optionally set the following:

    • Database: The database to connect to when connecting to the AlloyDB Server. If this is not set, the user's default database will be used.
    • Port: The port of the server hosting the AlloyDB database. This property is set to 5432 by default.

    Authenticating with Standard Authentication

    Standard authentication (using the user/password combination supplied earlier) is the default form of authentication.

    No further action is required to leverage Standard Authentication to connect.

    Authenticating with pg_hba.conf Auth Schemes

    There are additional methods of authentication available which must be enabled in the pg_hba.conf file on the AlloyDB server.

    Find instructions about authentication setup on the AlloyDB Server here.

    Authenticating with MD5 Authentication

    This authentication method must be enabled by setting the auth-method in the pg_hba.conf file to md5.

    Authenticating with SASL Authentication

    This authentication method must be enabled by setting the auth-method in the pg_hba.conf file to scram-sha-256.

    Authenticating with Kerberos

    The authentication with Kerberos is initiated by AlloyDB Server when the ∏ is trying to connect to it. You should set up Kerberos on the AlloyDB Server to activate this authentication method. Once you have Kerberos authentication set up on the AlloyDB Server, see the Kerberos section of the help documentation for details on how to authenticate with Kerberos. Configuring a connection (Salesforce is shown)

  6. Click Save & Test
  7. Navigate to the Permissions tab and update user-based permissions
  8. Updating 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. Creating a new PAT
  5. Copy the token when displayed and store it securely. It will not be shown again

With the AlloyDB connection configured and a PAT generated, Muse can now connect to AlloyDB 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 Click Continue

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

Step 3: Interact with live AlloyDB data from Meta Muse

With the integration complete, interact with live AlloyDB 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 AlloyDB
    • Fetch the top 5 records from AlloyDB
  2. Approve the tool call in the Sentinel dialog when prompted
  3. Muse calls the Connect AI MCP Server and returns live results from AlloyDB data Querying live data from Muse

At this point, Muse communicates with the Connect AI MCP Server and retrieves live AlloyDB 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.

Ready to get started?

Learn more about CData Connect AI or sign up for free trial access:

Free Trial