Integrate Theia IDE with Live PingOne Data via CData Connect AI
Theia IDE is an open-source, cloud and desktop IDE platform that provides a flexible, extensible development environment with built-in AI capabilities. Its AI features support multiple LLM providers and MCP (Model Context Protocol) tool integrations, allowing developers to interact with live external data sources directly from chat-based agents inside the IDE.
By integrating Theia IDE with CData Connect AI through the built-in MCP server, Theia's AI agents gain governed, real-time access to live PingOne data. This enables developers to list catalogs, explore schemas, and query records from PingOne data without leaving the editor or writing custom integration code.
This article explains how to configure PingOne connectivity in Connect AI, generate the required personal access token, register the CData Connect AI MCP Server in Theia IDE, enable AI features with an LLM provider, and verify the integration by querying live PingOne data from the Theia AI Chat.
Step 1: Configure PingOne connectivity for Theia IDE
Connectivity to PingOne from Theia IDE is made possible through Connect AI's Remote MCP Server. To interact with PingOne data from Theia IDE, start by creating and configuring a PingOne connection in 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 Theia IDE. 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, Theia IDE can now connect to PingOne data through Connect AI.
Step 2: Configure Connect AI MCP in Theia IDE
Next, register the CData Connect AI Remote MCP Server in Theia IDE so that the built-in AI agents can discover and call live data tools through Connect AI.
- Download and install the Theia IDE
- Open Theia IDE and navigate to Settings (or press Ctrl + ,) to open the Settings view
-
In the Settings panel, expand AI Features and select MCP
-
Click Edit in settings.json to open the configuration file and paste the following JSON:
{ "ai-features.mcp.mcpServers": { "cdata": { "serverUrl": "https://mcp.cloud.cdata.com/mcp", "serverAuthToken": "Basic your_base64_encoded_email_PAT", "serverAuthTokenHeader": "Authorization" } } }Note: Theia IDE will use Basic authentication with Connect AI. Combine your Connect AI user email and the PAT you created earlier in the format email:PAT, base64 encode the combined string, and prefix it with Basic. For example, given [email protected]:ABC123...XYZ789, the serverAuthToken value becomes something like: Basic dXNlckBkb21haW4uY29tOkFCQzEyMy4uLlhZWjc4OQ==
- Save the settings.json file
Enable AI and configure an LLM provider
Theia IDE requires AI features to be enabled and at least one LLM provider configured to power the agent's reasoning.
- Return to Settings and under AI Features, select AI Enablement
-
Check the Enable AI box to activate Theia's AI capabilities
- Under AI Features, choose your preferred LLM provider (e.g., Anthropic, OpenAI, Google, Hugging Face) and enter your API key
With the MCP server registered and an LLM provider configured, Theia's AI agents are ready to query live PingOne data through Connect AI.
Step 3: Query live PingOne data from the Theia AI Chat
With the integration complete, use the Theia AI Chat panel to interact with live PingOne data.
- Open the AI Chat panel from the right sidebar of the Theia IDE
- At the bottom of the chat, click the Toggle Capabilities Configuration icon (or press Ctrl + Shift + .) to open the capabilities panel
-
Under Generic Capabilities, expand MCP and check the cdata server (and any specific tools you want to expose) to make the Connect AI tools available to the agent
-
Type @AppTester in the chat input followed by your prompt, for example:
- List all catalogs in my cdata mcp
- Show the available schemas and tables for PingOne
- Query the top 5 records from a table in PingOne data
-
The agent calls the Connect AI MCP Server and returns live results from PingOne data
At this point, your Theia IDE communicates with the Connect AI MCP Server and retrieves live PingOne data through remote MCP directly from the editor.
Get CData Connect AI
To access hundreds of SaaS, Big Data, and NoSQL sources directly from your cloud applications, try CData Connect AI today! Start a free 14-day trial of CData Connect AI today, and as always, our world-class Support Team is available to assist you with any questions you may have.