Query Live PingOne Data in Zed Editor via CData Connect AI

Zed is a high-performance, open-source code editor built for speed and collaboration. Its built-in AI agent panel supports LLM-powered interactions and MCP (Model Context Protocol) tool integrations, enabling developers to access live external data sources directly within the editor.

By integrating Zed with CData Connect AI through the built-in MCP (Model Context Protocol) Server, the Zed AI agent gains governed, real-time access to live PingOne data. This enables developers to query schemas, retrieve records, and explore PingOne data without leaving the editor or writing custom integration code.

This article explains how to configure PingOne connectivity in Connect AI, register the CData MCP Server in Zed, and query live PingOne data from the Zed agent panel.

Step 1: Configure PingOne connectivity for Zed

Connectivity to PingOne from Zed is made possible through CData Connect AI's Remote MCP Server. To interact with PingOne data from Zed, 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 Zed. 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, Zed can now connect to PingOne data through Connect AI.

Step 2: Configure Connect AI in Zed

Now, let's register the CData Connect AI MCP endpoint in Zed so that the built-in AI agent can discover and call live data tools.

1. Download and install Zed
2. Open the agent panel by pressing Ctrl + Shift + /, or by clicking the sparkle icon at the bottom right of the editor
3. In the agent panel, click the ... (toggle agent menu) and select Add Custom Server from the dropdown
4. Select the Configure Remote option to configure CData's MCP
5. An Add MCP Server dialog opens displaying a remote server configuration template. Replace the placeholder content with the following JSON:

   {
       "cdata": {
           "url": "https://mcp.cloud.cdata.com/mcp",
           "headers": {
               "Authorization": "Basic your_base64_encoded_email_PAT"
           }
       }
   }
           

   Note: Combine your Connect AI email and PAT in the format email:PAT, Base64 encode the combined string, and prefix it with Basic. For example, given [email protected]:ABC123...XYZ, the header value becomes something like: Basic dXNlckBteWRvbWFpbjphSzkvbVB4Mi9Rcjd2TjQ...

   
6. Click Add Server or press Ctrl + Enter to register the MCP server

Configure an LLM provider

Zed requires at least one LLM provider to power the agent's reasoning. Configure a provider so the agent can interpret queries and call MCP tools through Connect AI.

1. Click the ... (toggle agent menu) and select Settings
2. Under LLM Providers, expand your preferred provider (e.g., Anthropic, OpenAI, Google AI) and enter your API key
3. Under Model Context Protocol (MCP) Servers, confirm that cdata appears with a green dot and the toggle is enabled

With the MCP server registered and an LLM provider configured, the Zed agent is ready to query live PingOne data through Connect AI.

Step 3: Query live PingOne data from the Zed agent

With the integration complete, use the Zed agent panel to explore and interact with live PingOne data through natural language prompts.

1. Open the agent panel using Ctrl + Shift + / and start a new thread
2. Enter a prompt to interact with your data, for example:
   • List all catalogs in my cdata connection
   • Show the available schemas and tables for PingOne
   • Query the top 5 records from a table in PingOne data
3. The agent calls the CData Connect AI MCP Server and returns live results from PingOne data

At this point, your Zed agent communicates with the CData Connect AI MCP Server and retrieves live PingOne data through remote MCP tools 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.