How to Access Live PingOne Data in Visual Studio Code via Cline

Cline is an autonomous coding agent right in your IDE, capable of creating/editing files, running commands, using the browser, and more with your permission every step of the way. When paired with CData Code Assist MCP for PingOne, you get live access to CRM data within your IDE, enabling you to build, test, and validate data-driven features using real-time schema and records without ever leaving your development environment.

CData Code Assist MCP provides schema-aware context to AI tools — whether you're using it for AI-assisted code generation in IDEs like Cursor and Cline, or for querying live data through chat interfaces like Claude Desktop.

This article outlines how to run CData Code Assist MCP for PingOne on WSL (Windows Subsystem for Linux) and connect to it from the Cline extension in Visual Studio Code on Windows.

Background

Code Assist MCP is typically designed for clients like Claude Desktop. However, when attempting to use it via the Cline extension in Windows VS Code, the following error occurred:

MCP error -32000: Connection closed

This issue is suspected to be caused by I/O handling problems in the stdio transport implementation on the Windows version of the Cline extension.

• Related GitHub Issue: https://github.com/cline/cline/issues/3464
• Additionally, environment variables such as PATH may not be inherited correctly when launching processes like Java or Node.

Prerequisites

• Visual Studio Code installed on Windows
• Cline extension installed and configured in VS Code
• Windows Subsystem for Linux (WSL) installed with a working Linux distribution (e.g., Ubuntu)
• Java 21+ JRE installed in WSL
• CData Code Assist MCP for PingOne installed on Windows

Step 1: Authenticate with PingOne (on Windows)

Before running Code Assist MCP in WSL, you must complete authentication flow in a Windows environment. This ensures all necessary credentials are generated and stored properly. Find and run "CData Code Assist MCP for PingOne" or execute the JAR file to open the configuration wizard.

java -jar "C:\Program Files\CData\CData Code Assist MCP for PingOne 20XX\lib\cdata.mcp.pingone.jar"

Connecting to PingOne

To connect to PingOne, configure these properties:

• : The region where the data for your PingOne organization is being hosted.
• : The type of authentication to use when connecting to PingOne.
• Either (required when using the default PingOne domain) or , configured as described below.

Configuring 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 to the value of the Environment ID field.

Configuring 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 to OAuth.

Desktop Applications

Get and Refresh the OAuth Access Token

After setting the following, you are ready to connect:

• : GETANDREFRESH. To avoid the need to repeat the OAuth exchange and manually setting the each time you connect, use .
• : The Client ID you obtained when you created your custom OAuth application.
• : The Client Secret you obtained when you created your custom OAuth application.
• : 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 , 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 Code Assist MCP

Name your configuration (e.g. cdatapingone), enter the required connection properties, and click "Connect."

👁 The Code Assist MCP configuration wizard (Google Sheets is shown).

Upon successful connection, the following directory and files will be created:

C:\Users\<username>\AppData\Roaming\CData\pingone Provider\
 |-- cdatapingone.mcp
 |-- (other supporting config files)

Step 2: Copy the Code Assist MCP Configuration into WSL

Next, copy the entire configuration folder from Windows into your WSL environment.

mkdir -p ~/.config/CData/
cp -r /mnt/c/Users/<username>/AppData/Roaming/CData/"pingone Provider" ~/.config/CData/

Ensure the destination path matches exactly: ~/.config/CData/pingone Provider/.

Step 3: Install Code Assist MCP on WSL

Install Java and place the Code Assist MCP JAR in the desired location within WSL:

sudo apt update
sudo apt install openjdk-21-jre-headless
sudo mkdir -p /opt/cdata/mcp_pingone/lib
sudo cp /mnt/c/Program\ Files/CData/CData\ Code\ Assist\ MCP\ for\ PingOne\ 20XX/lib/cdata.mcp.pingone.jar /opt/cdata/mcp_pingone/lib/

Step 4: Configure Cline

Now, configure the Cline extension to launch Code Assist MCP inside WSL using the wsl command.

Create or update cline_mcp_settings.json with the following content:

{
 "mcpServers": {
 "cdatapingone": {
 "autoApprove": ["*"],
 "disabled": false,
 "timeout": 60,
 "type": "stdio",
 "command": "wsl",
 "args": [
 "-d",
 "Ubuntu", // Replace with your installed WSL distro name
 "--",
 "/usr/bin/java",
 "-jar",
 "/opt/cdata/mcp_pingone/lib/cdata.mcp.pingone.jar",
 "cdatapingone"
 ],
 "env": {
 "JAVA_TOOL_OPTIONS": "-Xmx2g"
 }
 }
 }
}

Note: Replace Ubuntu with your actual WSL distribution name (e.g., Ubuntu-22.04). Run wsl -l in PowerShell or CMD to confirm.

Step 5: Interact with Live Data in Cline

From within Visual Studio Code, you can now run MCP commands through the Cline extension.

cdatapingone_get_tables
cdatapingone_get_columns [CData].[Administrators].Users

If configured correctly, these commands will return a list of available PingOne objects and metadata, allowing you to interact with your CRM schema in real time.

Try natural language prompts like:

• "Generate a React form to create a new PingOne Lead."
• "Write a Python function to pull Opportunities closed this quarter."

Build with Code Assist MCP. Deploy with CData Drivers.

Download Code Assist MCP for free and give your AI tools schema-aware access to live PingOne data during development. When you're ready to move to production, CData PingOne Drivers deliver the same SQL-based access with enterprise-grade performance, security, and reliability.

Visit the CData Community to share insights, ask questions, and explore what's possible with MCP-powered AI workflows.