Integrating Claude Code with PingOne Data via CData Connect AI

Claude Code is an AI-powered development environment that brings intelligent code generation, automation, and interactive reasoning directly into your workflow. By integrating it with CData Connect AI, you can enable Claude Code to securely access, query, and interact with live enterprise data, such as PingOne, through a standardized MCP tool interface.

CData Connect AI is a managed MCP platform that exposes your enterprise data sources through the Model Context Protocol (MCP). This allows Claude Code to work with catalogs, schemas, tables, metadata, and SQL-enabled data access from hundreds of data sources, without requiring ETL pipelines or custom integration code.

This article explains how to register the CData Connect AI MCP endpoint in Claude Code, configure your PingOne or other data source connection, and begin issuing real-time data queries directly from the coding environment. We explore how Claude Code uses the built-in MCP tools, such as getCatalogs, getSchemas, getTables, and queryData to help you write, debug, and automate development workflows powered by live PingOne data securely and interactively.

Prerequisites

• An account in CData Connect AI
• A Claude Code account.
• Visual Studio Code installed on your system.

Step 1: Configure PingOne connectivity for Claude Code

For Claude Code to access PingOne, create a connection to PingOne in CData Connect AI. This connection is then exposed to Claude Code using the remote MCP server.

1. Log in to Connect AI click Sources, and then click + Add Connection
2. From the available data sources, choose PingOne
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. Once authenticated, open the Permissions tab in the PingOne connection and configure user-based permissions as required

Generate a Personal Access Token (PAT)

Claude Code authenticates to Connect AI using an account email and a Personal Access Token (PAT). Creating separate PATs for each integration is recommended to maintain access control granularity.

1. In Connect AI, select the Gear icon in the top-right to open Settings
2. Under Access Tokens, select Create PAT
3. Provide a descriptive name for the token and select Create
4. Copy the token and store it securely. The PAT will only be visible during creation

With the PingOne connection configured and a PAT generated, Claude Code is prepared to connect to PingOne data through the CData MCP server.

Step 2: Install Claude Code

Claude Code is distributed as an npm package. You can install it globally.

To install Claude Code on your system, open PowerShell, Terminal, or CMD as an Administrator and run:

npm install -g @anthropic-ai/claude-code

Verify the installation using the following command:

npm list -g @anthropic-ai/claude-code

Expected output should be:

C:\Users\User\AppData\Roaming
pm
`-- @anthropic-ai/[email protected]

Step 3: Authenticate Claude Code with Claude.ai

Link your local Claude Code environment with your Claude.ai account to enable secure access. In the terminal, run:

claude login

Claude Code outputs a URL, like:

Please visit https://claude.ai/login?code=

Follow these steps:

1. Click the URL or paste it into your browser.
2. Log in to Claude.ai.
3. Claude.ai displays a verification code.
4. Return to your terminal and enter/paste the provided verification code when prompted.

Once verified, you'll need to authenticate with Claude Code using an authentication code. Once done, your terminal should display:

You're all set up for Claude Code.

Claude Code is now linked to your Claude.ai account.

Step 4: Create a Claude Code project

To set up a workspace where Claude Code can store MCP configuration files, start by creating a new directory:

mkdir ClaudeCode
cd ClaudeCode

Now, open it in Visual Studio Code:

code .

Step 5: Launch Claude Code and register the CData Connect AI MCP server

Before Claude Code can interact with PingOne, you must register your CData Connect AI MCP endpoint. Claude Code uses this remote MCP server to securely access metadata, schemas, tables, and live query results.

Now register the CData Connect AI MCP server by running the following command in your Claude Code project directory:

claude mcp add connectmcp https://mcp.cloud.cdata.com/mcp \
  --transport http \
  --header "Authorization: Basic base64encoded(EMAIL:PAT)" \
  --header "Content-Type: application/json"

Once added, verify that Claude recognizes your MCP server:

claude mcp list

If successful, you should see:

connectmcp: https://mcp.cloud.cdata.com/mcp (HTTP) - ✓ OK

Start the Claude Code assistant and verify that it detects your MCP server. To run, use the given command:

claude

Once Claude Code loads, you should see:

Loaded MCP Server: connectmcp

This confirms that Claude Code is now connected to your CData Connect AI instance.

Step 6: Explore PingOne metadata

You can now use Claude Code's natural-language interface to list catalogs, schemas, and tables in PingOne. Ask Claude:

List all PingOne catalogs using getCatalogs.

Claude automatically calls the appropriate MCP tool when you issue a request.

Try additional queries such as:

• "Show the available schemas."
• "List all tables in the PingOne connection."
• "Retrieve the top 10 records from the Account table."

Claude Code uses the following MCP tools to interact with PingOne in real time:

• getCatalogs
• getSchemas
• getTables
• queryData

These tools allow Claude Code to retrieve metadata and query live PingOne data.

Step 7: Generate code and automation workflows

Use real PingOne metadata to build working scripts directly inside your IDE.

Example prompt:

Write a Python script that queries Salesforce Contacts where LastName starts with 'A' using the MCP queryData tool.

Claude Code writes accurate code because it has:

• direct access to PingOne schemas
• live query testing
• metadata introspection

All delivered through CData Connect AI.

Step 8: Build data-driven development workflows

Use Claude Code to generate, refine, and automate code that works with your PingOne data using CData Connect AI.

With the CData Connect AI integration in place, Claude Code can help you build development workflows that rely on your PingOne data. Although Claude Code does not include built-in real-time data connectivity, your configured MCP connection through CData Connect AI provides it with access to the metadata and query results for your request.

You can use Claude Code to automate tasks such as:

• generating scripts for data exploration
• creating integration test scaffolding
• validating queries against your PingOne schema
• producing code for data extraction or transformation workflows

In this setup, Claude Code acts as an intelligent coding assistant that uses live PingOne data from CData Connect AI to help you write and refine data-driven logic.

Optional: Manage MCP integrations

Add, remove, or inspect MCP servers in your project.

List MCP servers using the following command:

claude mcp list

To remove one, use:

claude mcp remove connectmcp

Modify the config by editing:

.claude/mcp.json

Get CData Connect AI

To get live data access to hundreds of SaaS, Big Data, and NoSQL sources directly from your cloud applications, try CData Connect AI today!