Query Live SingleStore Data in Perplexity Desktop via CData Connect AI

Perplexity is an AI-powered research and answer engine that combines web search, structured data, and connected tools through a unified conversational interface. With Perplexity Desktop for macOS, you can bring external data sources directly into your workflow using MCP, enabling fast, context-aware insights powered by live data.

Integrating Perplexity Desktop with CData Connect AI via its built-in MCP connector allows the AI to query, explore, and reason over live SingleStore data without copying data out of its source system. The result is a research experience where you can ask questions about your governed enterprise data directly from Perplexity Desktop.

This article outlines how to configure SingleStore connectivity in Connect AI, generate the required access token, register Connect AI's MCP Server in Perplexity Desktop, and then use the chat interface to explore live SingleStore data.

Step 1: Configure SingleStore connectivity for Perplexity Desktop

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

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

2. Select SingleStore from the Add Connection panel

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

   The following connection properties are required in order to connect to data.

   • Server: The host name or IP of the server hosting the SingleStore database.
   • Port: The port of the server hosting the SingleStore database.
   • Database (Optional): The default database to connect to when connecting to the SingleStore Server. If this is not set, tables from all databases will be returned.

   Connect Using Standard Authentication

   To authenticate using standard authentication, set the following:

   • User: The user which will be used to authenticate with the SingleStore server.
   • Password: The password which will be used to authenticate with the SingleStore server.

   Connect Using Integrated Security

   As an alternative to providing the standard username and password, you can set IntegratedSecurity to True to authenticate trusted users to the server via Windows Authentication.

   Connect Using SSL Authentication

   You can leverage SSL authentication to connect to SingleStore data via a secure session. Configure the following connection properties to connect to data:

   • SSLClientCert: Set this to the name of the certificate store for the client certificate. Used in the case of 2-way SSL, where truststore and keystore are kept on both the client and server machines.
   • SSLClientCertPassword: If a client certificate store is password-protected, set this value to the store's password.
   • SSLClientCertSubject: The subject of the TLS/SSL client certificate. Used to locate the certificate in the store.
   • SSLClientCertType: The certificate type of the client store.
   • SSLServerCert: The certificate to be accepted from the server.

   Connect Using SSH Authentication

   Using SSH, you can securely login to a remote machine. To access SingleStore data via SSH, configure the following connection properties:

   • SSHClientCert: Set this to the name of the certificate store for the client certificate.
   • SSHClientCertPassword: If a client certificate store is password-protected, set this value to the store's password.
   • SSHClientCertSubject: The subject of the TLS/SSL client certificate. Used to locate the certificate in the store.
   • SSHClientCertType: The certificate type of the client store.
   • SSHPassword: The password that you use to authenticate with the SSH server.
   • SSHPort: The port used for SSH operations.
   • SSHServer: The SSH authentication server you are trying to authenticate against.
   • SSHServerFingerPrint: The SSH Server fingerprint used for verification of the host you are connecting to.
   • SSHUser: Set this to the username that you use to authenticate with the SSH server.
   
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 Perplexity Desktop. 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. The personal access token is only visible at creation, so be sure to copy it and store it securely for future use

Create an OAuth App in CData Connect AI

Perplexity Desktop uses OAuth 2.0 to authenticate users against the CData Connect AI MCP Server. This requires creating an OAuth App in your CData Connect AI account.

1. Click the Gear icon () in the top-right corner of Connect AI to open Settings
2. Navigate to OAuth Apps and click + Create App. The Create OAuth App dialog appears
3. Fill in the following fields:
   • Name: Enter a descriptive name (e.g., PerplexityOAuth)
   • Authentication Flow: Select User-based (Authorization Code)
   • Callback URL: Enter the callback URL provided by Perplexity Desktop when adding the connector
   
4. Click Confirm. CData Connect AI generates a Client ID and Client Secret
5. Copy both values and store them securely. You will need them in Step 2

With the SingleStore connection configured and an OAuth App created, Perplexity Desktop can now connect to SingleStore data through Connect AI.

Step 2: Configure Connect AI in Perplexity Desktop

Next, register the CData Connect AI MCP Server as a custom remote connector in Perplexity Desktop. This feature requires a Perplexity Pro, Max, or Enterprise account and the macOS desktop app. Once configured, Perplexity's AI can call the tools exposed by CData Connect AI to access live SingleStore data.

1. Download the Perplexity Desktop application for macOS and sign in with your Pro, Max, or Enterprise account
2. Click Customize in the left sidebar and open the Connectors tab. Click + Custom connector in the top-right corner to open the Add custom connector dialog
3. Enter a Name for the connector (e.g., CData Connect AI) and, optionally, a Description. In the MCP server URL field, enter the CData Connect AI MCP endpoint: https://mcp.cloud.cdata.com/mcp
4. Expand Advanced and configure the following:
   • Authentication: Select OAuth, then enter the Client ID and Client Secret from the OAuth App created in Step 1
   • Transport: Select Streamable HTTP
   • Network access: Select Public
   Check the box acknowledging that custom connectors can introduce risks, then click Add
5. The new connector appears in the Connectors list. Click + on the connector to connect it. When redirected to CData Connect AI, sign in and click Allow to grant Perplexity access

Step 3: Query your live SingleStore data from Perplexity Desktop

1. Click New Session and make sure the CData Connect AI connector is enabled for the session. The active connector appears above the prompt box
2. Start asking questions about your SingleStore data. For example:

   "Which data sources do you have access to via Connect AI?"

   
3. Try additional queries such as:
   • "List all the tables available in my SingleStore data connection."
   • "Show the available schemas in SingleStore."
   • "Retrieve the top 10 records from the Account table."
   • "Summarize the high-priority open opportunities in SingleStore."

Perplexity Desktop is now fully integrated with the CData Connect AI MCP Server and can reason over live SingleStore data directly from the chat interface.

Get CData Connect AI

To access hundreds of SaaS, Big Data, and NoSQL sources directly from your AI tools, try CData Connect AI today!