Integrate Cline with Live PingOne Data via CData Connect AI

Yazhini G
Yazhini G
Technical Marketing Engineer
Leverage the CData Connect AI Remote MCP Server to enable Cline to securely access and query live PingOne data from within your IDE.

Cline is an autonomous AI coding agent that runs inside modern IDEs such as VS Code and Cursor. It enables developers to build agent-driven workflows that can reason through tasks, execute actions, and interact with external systems directly from the editor using a structured execution model.

By integrating Cline with CData Connect AI through the built-in MCP (Model Context Protocol) Server, the agent gains the ability to query, analyze, and act on live PingOne data in real time. This integration bridges Cline's in-IDE agent framework with the governed enterprise connectivity of CData Connect AI, ensuring all data access runs securely against authorized sources without manual data movement.

This article outlines the steps to configure PingOne connectivity in Connect AI, generate the required personal access token, register the Connect AI MCP Server in Cline, and verify that the agent can successfully interact with live PingOne data from within the IDE.

Step 1: Configure PingOne connectivity for Cline

Connectivity to PingOne from Cline is made possible through CData Connect AI's Remote MCP Server. To interact with PingOne data from Cline, 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. Adding a connection in Connect AI
  3. Select PingOne from the Add Connection panel
  4. Selecting data source
  5. 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.

    Configuring a connection (Salesforce is shown)
  6. Click Save & Test
  7. Navigate to the Permissions tab and update user-based permissions
  8. Updating permissions

Add a Personal Access Token

A Personal Access Token (PAT) is used to authenticate the connection to Connect AI from Cline. 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. Creating a new PAT
  5. Copy the token when displayed and store it securely. It will not be shown again

With the PingOne connection configured and a PAT generated, Cline can now connect to PingOne data through the CData Connect Ai.

Step 2: Install and set up Cline

Cline is distributed as an IDE extension and can be installed in environments such as VS Code or Cursor. In this example, Cursor is used, but the steps are identical for supported IDEs.

  1. Open Cursor and install the Cline extension from the Extensions Marketplace Installing the Cline extension in Cursor
  2. Complete the initial Cline setup flow, including model selection and permission prompts
  3. After setup is complete, the Cline agent panel opens automatically inside the IDE

Step 3: Add the Connect AI Remote MCP Server

Once Cline is running, add the CData Connect AI Remote MCP Server so the agent can access live PingOne data through Connect AI.

  1. In the Cline panel, click MCP Servers Opening MCP Servers in Cline
  2. Open Remote Servers and click Edit Configuration Editing remote MCP server configuration
  3. This opens a JSON configuration file. Paste the configuration below
    {
      "mcpServers": {
        "mcp": {
          "url": "https://mcp.cloud.cdata.com/mcp",
          "type": "streamableHttp",
          "headers": {
            "Authorization": "Basic your_email:your_PAT"
          },
          "disabled": false,
          "autoApprove": []
        }
      }
    }
    

    Note: Cline will use Basic authentication with Connect AI. Combine your Connect AI user email and the PAT you created earlier. For example, [email protected]:ABC123...XYZ789 and add the value for the Authorization header like, Basic [email protected]:ABC123...XYZ789.

    Configuring MCP server
  4. Save the file and return to the MCP Servers screen to confirm the server is listed and enabled Configured MCP server listed in Cline

Step 4: Query live data from Cline

With the MCP server registered, Cline can now interact with live data sources exposed by Connect AI.

  1. Click the icon in the Cline panel to start a New Task/Chat Starting a new chat in Cline
  2. At the bottom of the chat window, confirm that the configured MCP server is selected Selecting the configured MCP server
  3. Start interacting with the agent by entering prompts such as:
    • List connections
    • Show schemas for a catalog
    • Query recent records from PingOne data
    Sample output from querying through the MCP server

Cline is now fully configured to access and query live PingOne data through the CData Connect AI Remote MCP Server, enabling real-time, data-driven workflows directly from your IDE.

Get CData Connect AI

To access hundreds of SaaS, Big Data, and NoSQL sources through secure, AI-ready interfaces, try CData Connect AI today.

Ready to get started?

Learn more about CData Connect AI or sign up for free trial access:

Free Trial