How to Query Live PingOne Data in Claude Desktop

Model Context Protocol (MCP) is an emerging, open-source standard for connecting LLMs with external services and data sources. Through MCP Servers, AI clients can perform actions like opening Jira tickets, posting Slack messages, committing GitHub branches and more. With CData MCP Servers, these capabilities expand exponentially.

In this article, we guide the reader through installing the CData MCP Server for PingOne, configuring the connection to PingOne, and asking questions of the data in Claude Desktop.

Prerequisites

You need to download Claude Desktop (download) and create an account before continuing.

Overview

Here's a quick overview of the steps:

1. Download and install the CData MCP Server for PingOne
2. Configure the connection to PingOne
3. Ask questions about the data in Claude Desktop

Step 1: Download and install the CData MCP Server

1. To begin, navigate to https://www.cdata.com/solutions/mcp/connectors and download the CData MCP Server for PingOne.
2. Find and double-click the installer to begin the installation.
3. Follow the prompts to complete the installation.

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

Step 2: Configure the connection to PingOne

1. After installation, the CData MCP Server configuration wizard should open automatically.

   NOTE: If the wizard does not open automatically, search for "CData MCP Server" in the Windows search bar and double-click the application.

2. Click the dropdown menu in MCP Configuration > Configuration Name and select ""
3. Name the configuration (e.g. "cdatapingone") and click "OK."

   NOTE: This name is used as the name for the MCP server and as the prefix for all of the MCP Server's tools.

   

4. Connecting 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.

   Enter the appropriate connection properties in the configuration wizard.

   
5. Click "Connect" to authenticate with PingOne through OAuth.

   NOTE: The configuration wizard should open your browser and ask you to sign into Google. If your browser does not open, close the configuration wizard and re-open the application using "Run as Administrator" (see below).

   
6. Finally, click "Save Configuration" to save the MCP server.

   NOTE: This saves the configuration details to a separate file and updates the Claude Desktop configuration file (claude_desktop_config.json) to start the CData MCP Server when the Claude Desktop client starts.

With the CData MCP Server configured, you are ready to start asking questions of your live data from Claude.

Step 3: Ask AI for answers from live PingOne data

Now that we have installed the CData MCP Server and configured a connection, we are ready to start with PingOne data in Claude Desktop.

1. Open Claude Desktop. It may take a moment for the MCP Servers to start, but you will see the list of servers and tools available in the Claude interface (look for the settings icon below the prompt bar).

   You can individually enable and disable specific tools by clicking on the server name.

2. Now that you have connected, you can ask Claude questions about the PingOne data. For example: "Can you give me a quantitative analysis about my closed-won opportunities by industry?"

   NOTE: Claude may need to explore the PingOne data to make sense of it before it can begin answering questions of the data. The tabular model presented by CData alongside the database tools available simplify the data exploration and analysis for an LLM.

   

Connect your AI to your data today!

CData MCP Servers make it easier than ever for LLMs to work with live enterprise data. To explore the technology hands-on, download a free MCP Server or visit the CData Community to share insights, ask questions, and help shape the future of enterprise-ready AI.