Access Live PingOne Data in Roo Code via CData Connect AI

Roo Code is an open-source AI coding agent that runs inside VS Code with real file system access, terminal control, and multi-step workflows. It works across entire project workspaces through specialized modes like Code, Architect, and Orchestrator. Available as a VS Code Extension for local development, or as Cloud Agents that integrate with Slack and GitHub. Roo Code natively supports MCP, connecting external tools and data sources via STDIO or Streamable HTTP.

By default, Roo Code has no access to live enterprise data. CData Connect AI bridges this gap by exposing hundreds of data sources. Once connected, Roo can introspect live schemas, validate queries, and generate code directly inside VS Code, retrieved by real enterprise data.

Step 1: Configure PingOne connectivity for Roo Code

Connectivity to PingOne from Roo Code is made possible through CData Connect AI's Remote MCP Server. To interact with PingOne data from Roo Code, 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 Roo Code. 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. Copy the token when displayed and store it securely. It will not be shown again

With the PingOne connection configured and a PAT generated, Roo Code can now connect to PingOne data through Connect AI.

Step 2: Configure Connect AI in Roo Code

CData Connect AI can be integrated with Roo Code by registering the MCP Server directly in the Roo Code MCP configuration panel. Once registered, Roo Code agents can call live PingOne data through MCP tools without additional setup.

Method 1: Direct MCP configuration

Users can register the CData Connect AI MCP Server directly in the Roo Code MCP settings. Once registered, agents in any project can query live PingOne data through MCP tools without additional setup.

1. Open VS Code with the Roo Code extension installed
2. Click the Roo Code icon in the Activity Bar
3. Navigate to Settings, then choose MCP Servers in the Roo Code pane and turn on Enable MCP Servers, now click Edit Global MCP to open the MCP configuration file
4. In the mcp_settings.json file, add the following inside the mcpServers object, replacing base64encode with your Base64-encoded email:PAT

   {
       "mcpServers": {
           "cdata-mcp": {
               "type": "streamable-http",
               "url": "https://mcp.cloud.cdata.com/mcp",
               "headers": {
                   "Authorization": "Basic base64encode(USERNAME:PAT)"
               }
           }
       }
   }
           

   
5. Save the file to register the MCP server
6. Return to the MCP Servers panel 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, Roo Code agents can now query and act on live PingOne data through Connect AI in any project.

Query live PingOne data from Roo Code

With the MCP server configured, start a conversation in the Roo Code chat panel to interact with live PingOne data.

1. Open the Roo Code 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.
2. The agent calls the CData Connect AI MCP Server and returns live results from PingOne data

Method 2: Build an application with natural language

Users can direct Roo Code to build a full application that connects to the CData Connect AI MCP Server through a natural language prompt. The agent gathers the required endpoint and credentials interactively, then generates a working application wired to live PingOne data — all from the Roo Code chat panel inside VS Code.

1. Open the Roo Code panel in VS Code and select your preferred model from the dropdown
2. 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.
           

3. Roo Code 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)
4. Roo Code creates the project directory, initializes a Node.js project, installs the necessary packages, and stores credentials securely in a .env file

At this point, Roo Code 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 inside VS Code.

Get CData Connect AI

To access hundreds of SaaS, Big Data, and NoSQL sources directly from Roo Code, 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.