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

Use the CData Connect AI Remote MCP Server to enable Muse to securely interact with live XML 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 XML 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 XML 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 XML data from Muse.

Step 1: Configure XML connectivity for Meta Muse

Connectivity to XML from Muse is made possible through Connect AI's Remote MCP Server. To interact with XML data from Muse, start by creating and configuring a XML 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 XML from the Add Connection panel
  4. Selecting data source
  5. Enter the necessary authentication properties to connect to XML.

    Connecting to Local or Cloud-Stored (Box, Google Drive, Amazon S3, SharePoint) XML Files

    CData Drivers let you work with XML files stored locally and stored in cloud storage services like Box, Amazon S3, Google Drive, or SharePoint, right where they are.

    Setting connection properties for local files

    Set the URI property to local folder path.

    Setting connection properties for files stored in Amazon S3

    To connect to XML file(s) within Amazon S3, set the URI property to the URI of the Bucket and Folder where the intended XML files exist. In addition, at least set these properties:

    • AWSAccessKey: AWS Access Key (username)
    • AWSSecretKey: AWS Secret Key

    Setting connection properties for files stored in Box

    To connect to XML file(s) within Box, set the URI property to the URI of the folder that includes the intended XML file(s). Use the OAuth authentication method to connect to Box.

    Dropbox

    To connect to XML file(s) within Dropbox, set the URI proprerty to the URI of the folder that includes the intended XML file(s). Use the OAuth authentication method to connect to Dropbox. Either User Account or Service Account can be used to authenticate.

    SharePoint Online (SOAP)

    To connect to XML file(s) within SharePoint with SOAP Schema, set the URI proprerty to the URI of the document library that includes the intended XML file. Set User, Password, and StorageBaseURL.

    SharePoint Online REST

    To connect to XML file(s) within SharePoint with REST Schema, set the URI proprerty to the URI of the document library that includes the intended XML file. StorageBaseURL is optional. If not set, the driver will use the root drive. OAuth is used to authenticate.

    Google Drive

    To connect to XML file(s) within Google Drive, set the URI property to the URI of the folder that includes the intended XML file(s). Use the OAuth authentication method to connect and set InitiateOAuth to GETANDREFRESH.

    The DataModel property is the controlling property over how your data is represented into tables and toggles the following basic configurations.

    • Document (default): Model a top-level, document view of your XML data. The data provider returns nested elements as aggregates of data.
    • FlattenedDocuments: Implicitly join nested documents and their parents into a single table.
    • Relational: Return individual, related tables from hierarchical data. The tables contain a primary key and a foreign key that links to the parent document.

    See the Modeling XML Data chapter for more information on configuring the relational representation. You will also find the sample data used in the following examples. The data includes entries for people, the cars they own, and various maintenance services performed on those cars.

    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 XML connection configured and a PAT generated, Muse can now connect to XML 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 XML data from Meta Muse

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

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