Access Live PingOne Data in Emergent via CData Connect AI
Emergent is an AI-powered development platform that lets users describe what they want to build and have an autonomous agent generate full-stack web applications in real time. Agents can connect to external tools and data sources through MCP to retrieve live data and power their outputs.
By integrating Emergent with CData Connect AI through the built-in MCP (Model Context Protocol) Server, Emergent agents gain governed, real-time access to live PingOne data. This enables agents to query, analyze, and visualize PingOne data: either by calling MCP tools directly during a session, or by generating a full application wired to live data, all without manual data exports or custom integration code.
This article outlines the steps to configure PingOne connectivity in Connect AI, register the CData MCP Server in Emergent, and interact with live PingOne data from Emergent.
Step 1: Configure PingOne connectivity for Emergent
Connectivity to PingOne from Emergent is made possible through CData Connect AI's Remote MCP Server. To interact with PingOne data from Emergent, start by creating and configuring a PingOne connection in CData Connect AI.
- Log into Connect AI, click Sources, and then click Add Connection
- Select PingOne from the Add Connection panel
-
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:
- From the home page of your PingOne organization, move to the navigation sidebar and click Environments.
- 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.
- In the environment's home page navigation sidebar, click Applications.
- Find your OAuth or Worker application details in the list.
-
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:
- The driver obtains an access token from PingOne and uses it to request data.
- 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.
- Click Save & Test
- 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 Emergent. It is best practice to create a separate PAT for each integration to maintain granular access control.
- Click the gear icon () at the top right of the Connect AI app to open Settings
- On the Settings page, go to the Access Tokens section and click Create PAT
- Give the PAT a descriptive name and click Create
- Copy the token when displayed and store it securely. It will not be shown again
With the PingOne connection configured and a PAT generated, Emergent can now connect to PingOne data through Connect AI.
Step 2: Configure Connect AI in Emergent
CData Connect AI can be integrated with Emergent in two ways depending on your account tier. Pro and Enterprise users can register the MCP Server directly in the Emergent UI, while free-tier users can describe the integration in natural language and have Emergent's agent build a connected application automatically.
Method 1: Direct MCP Configuration (Pro/Enterprise)
Pro and Enterprise users can register the CData Connect AI MCP Server directly in the Emergent UI. Once registered, agents in any project can call live PingOne data through MCP tools without additional setup.
- Sign in to Emergent and create an account if you do not already have one
-
Click to start a new project. Enter a Project Name and click Create Project
- In the project chat window, select your preferred model from the dropdown (e.g., Claude 4.5 Sonnet)
-
Click the Advanced Controls icon and then click Select MCP Tools to open the MCP configuration panel
-
In the Select MCPs to use dialog, click + New MCP Server to add a custom MCP server
-
In the Configure New MCP dialog, fill in the following:
- MCP Name: cdata-mcp
- Description: (optional) A brief description of the server
- JSON Configuration: Paste the following, replacing base64-encode-email-pat with your Base64-encoded email:PAT string:
{ "mcpServers": { "cdata-mcp": { "args": [ "-y", "mcp-client", "connect", "https://mcp.cloud.cdata.com/mcp" ], "command": "npx", "env": { "MCP_HEADERS": "{\"Authorization\":\"Basic base64-encode-email-pat\"}" } } } }Note: Combine your Connect AI email and PAT in the format email:PAT, then Base64 encode the combined string. For example, given [email protected]:ABC123...XYZ, the value becomes something like: dXNlckBteWRvbWFpbjphSzkvbVB4Mi9Rcjd2TjQ...
- Click Verify and Save to register the MCP server
- Return to Select MCP Tools and confirm that cdata-mcp is listed and its toggle is enabled. If it is not enabled, toggle it on
With the CData MCP Server registered and enabled, Emergent agents can now query and act on live PingOne data through Connect AI in any project.
Query live PingOne data from Emergent
With the MCP server configured, start a conversation in the Emergent agent panel to interact with live PingOne data.
-
Return to the project chat and enter a prompt to explore your data, for example:
- List all available catalogs in my cdata-mcp connection.
- Show the schemas and tables available for PingOne.
- Query the top 5 records from PingOne data.
- The agent calls the CData Connect AI MCP Server and returns live results from PingOne data
Method 2: Build an application with natural language (Free)
Free-tier users can direct Emergent to build a full-stack application that connects to the CData Connect AI MCP Server through a natural language prompt. The agent will gather the required endpoint and credentials interactively, then generate a working application wired to live PingOne data.
- Sign in to Emergent and open the chat window
-
Enter a prompt that describes the application you want to build. For example:
I would like to build a small application that connects to a remote MCP HTTPS server. I already have the MCP endpoint URL and the required credentials. The application should: - Establish a connection to the remote MCP server - Authenticate using the provided credentials - Retrieve and list all available catalogs from the MCP Please make sure the credentials are stored securely in a .env file and not hardcoded in the application. -
Emergent will prompt you to provide the MCP endpoint URL and authentication credentials. Supply the following values:
- MCP Endpoint URL: https://mcp.cloud.cdata.com/mcp
- Authorization: Basic base64(email:PAT)
-
The Emergent agent generates a full-stack application that connects to PingOne data through Connect AI and renders live results in the App Preview panel.
At this point, Emergent has built an application that communicates with the CData Connect AI MCP Server and retrieves live PingOne data, all from a single natural language prompt.
Get CData Connect AI
To access hundreds of SaaS, Big Data, and NoSQL sources directly from your cloud applications, try CData Connect AI today! Sign up for a free 14-day trial of CData Connect AI, and as always, our world-class Support Team is available to assist you with any questions you may have.