How to Query Live PingOne Data in Perplexity MacOS Desktop

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

Model Context Protocol (MCP) is an emerging, open-source standard for connecting LLMs with external services and enterprise data sources. Using MCP Servers, AI clients such as Perplexity Desktop can securely interact with applications and data, performing actions, retrieving live information, and enabling natural language access to data.

In this article, we guide you through installing the CData MCP Server for PingOne, configuring the connection to PingOne, and interacting with your live PingOne data from Perplexity Desktop.

Step 1: Download and install the CData MCP Server for PingOne

1. To begin, download the CData MCP Server for PingOne
2. Find and double-click the installer to begin the installation
3. Drag the CData MCP Server app into the Applications folder

When the installation is complete, you are ready to configure your MCP Server by connecting to PingOne.

NOTE: Since you downloaded the application from the internet and not the Apple App Store, you may see a warning that the application was not opened because Apple could not verify its security. You may continue with the installation.

Installing a trusted, unverified App

CData's solutions are trusted across the globe by some of the largest software vendors in the world. That said, if you have any concerns about continuing, please consult with your IT and/or security team.

1. In the warning message that pops up, click "Done"
2. Open "System Settings" on your machine and navigate to the "Privacy & Security" page

3. Scroll down to the "Security" section and click "Open Anyway"
4. Authorize the installation (passkey or password)

Step 2: Configure the Connection to PingOne

1. After installation, you can open the CData MCP Server for PingOne from the Applications folder on your mac
2. Click the dropdown menu in MCP Configuration > Configuration Name and select "new configuration"
3. Name the configuration (e.g. "cdata_pingone") and click "OK"

4. Enter the appropriate connection properties in the configuration wizard.

   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.

   
5. Click "Connect" to authenticate with PingOne through OAuth.
6. Click "Save Configuration" to save the MCP server

With your MCP Server configured, you are ready to connect it to Perplexity Desktop.

Step 3: Connect the MCP Server to Perplexity Desktop

1. Download the Perplexity Desktop application for macOS and sign in with your Pro or Premium account
2. Open Settings > Connectors. If the Perplexity Helper App is not installed, you will be prompted to download it. Install the Helper App, then restart Perplexity Desktop
3. After restarting, return to Settings > Connectors and click Add Connector
4. Select the Simple tab and assign a name for the connector (e.g., "CData PingOne MCP"). In the Command box, enter the absolute path to your MCP Server executable.

   For example:

   	/Applications/CData MCP Server for PingOne.app/Contents/Payload/jre/Contents/Home/bin/java \
   	-jar /Applications/CData MCP Server for PingOne.app/Contents/Payload/lib/cdata.mcp.pingone.jar \
   	cdata_pingone
   

   
5. Click Save. Your MCP Server should now appear in the connector list with a "Running" status

Step 4: Query Your Live PingOne data in Perplexity Desktop

1. Open a new chat in Perplexity Desktop. Click the Sources toggle and enable your MCP Server
2. Start asking questions about your PingOne data. For example:

   "List all the tables available in my PingOne data connection."

   

Connect your AI to your PingOne data today!

CData MCP Servers make it simple to connect Perplexity and other LLM clients to real-time enterprise data. Download a free, 30-day trial and join the CData Community to share insights, ask questions, and help shape the future of enterprise-ready AI.