Query Live PingOne 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 PingOne 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 PingOne 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 PingOne data.

Step 1: Configure PingOne connectivity for Perplexity Desktop

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

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

2. Select PingOne from the Add Connection panel

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

   To connect to PingOne, configure these properties:

   • Region: The region where the data for your PingOne organization is being hosted.
   • AuthScheme: The type of authentication to use when connecting to PingOne.
   • Either WorkerAppEnvironmentId (required when using the default PingOne domain) or AuthorizationServerURL, configured as described below.

   Configuring WorkerAppEnvironmentId

   WorkerAppEnvironmentId is the ID of the PingOne environment in which your Worker application resides. This parameter is used only when the environment is using the default PingOne domain (auth.pingone). It is configured after you have created the custom OAuth application you will use to authenticate to PingOne, as described in Creating a Custom OAuth Application in the Help documentation.

   First, find the value for this property:

   1. From the home page of your PingOne organization, move to the navigation sidebar and click Environments.
   2. Find the environment in which you have created your custom OAuth/Worker application (usually Administrators), and click Manage Environment. The environment's home page displays.
   3. In the environment's home page navigation sidebar, click Applications.
   4. Find your OAuth or Worker application details in the list.
   5. Copy the value in the Environment ID field. It should look similar to:
      

      WorkerAppEnvironmentId='11e96fc7-aa4d-4a60-8196-9acf91424eca'

   Now set WorkerAppEnvironmentId to the value of the Environment ID field.

   Configuring AuthorizationServerURL

   AuthorizationServerURL is the base URL of the PingOne authorization server for the environment where your application is located. This property is only used when you have set up a custom domain for the environment, as described in the PingOne platform API documentation. See Custom Domains.

   Authenticating to PingOne with OAuth

   PingOne supports both OAuth and OAuthClient authentication. In addition to performing the configuration steps described above, there are two more steps to complete to support OAuth or OAuthCliet authentication:

   • Create and configure a custom OAuth application, as described in Creating a Custom OAuth Application in the Help documentation.
   • To ensure that the driver can access the entities in Data Model, confirm that you have configured the correct roles for the admin user/worker application you will be using, as described in Administrator Roles in the Help documentation.
   • Set the appropriate properties for the authscheme and authflow of your choice, as described in the following subsections.

   OAuth (Authorization Code grant)

   Set AuthScheme to OAuth.

   Desktop Applications

   Get and Refresh the OAuth Access Token

   After setting the following, you are ready to connect:

   • InitiateOAuth: GETANDREFRESH. To avoid the need to repeat the OAuth exchange and manually setting the OAuthAccessToken each time you connect, use InitiateOAuth.
   • OAuthClientId: The Client ID you obtained when you created your custom OAuth application.
   • OAuthClientSecret: The Client Secret you obtained when you created your custom OAuth application.
   • CallbackURL: The redirect URI you defined when you registered your custom OAuth application. For example: https://localhost:3333

   When you connect, the driver opens PingOne's OAuth endpoint in your default browser. Log in and grant permissions to the application. The driver then completes the OAuth process:

   1. The driver obtains an access token from PingOne and uses it to request data.
   2. The OAuth values are saved in the location specified in OAuthSettingsLocation, to be persisted across connections.

   The driver refreshes the access token automatically when it expires.

   For other OAuth methods, including Web Applications, Headless Machines, or Client Credentials Grant, refer to the Help documentation.

   
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 PingOne connection configured and an OAuth App created, Perplexity Desktop can now connect to PingOne 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 PingOne 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 PingOne 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 PingOne 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 PingOne data connection."
   • "Show the available schemas in PingOne."
   • "Retrieve the top 10 records from the Account table."
   • "Summarize the high-priority open opportunities in PingOne."

Perplexity Desktop is now fully integrated with the CData Connect AI MCP Server and can reason over live PingOne 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!