Query Live AlloyDB 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 AlloyDB data. This enables developers to query schemas, retrieve records, and explore AlloyDB data without leaving the editor or writing custom integration code.

This article walks through configuring AlloyDB connectivity in Connect AI, registering the CData MCP Server in Zed, and querying live AlloyDB data from the Zed agent panel.

Step 1: Configure AlloyDB connectivity for Zed

Connectivity to AlloyDB from Zed is made possible through CData Connect AI's Remote MCP Server. To interact with AlloyDB data from Zed, start by creating and configuring a AlloyDB connection in CData Connect AI.

1. Log into Connect AI, click Sources, and then click Add Connection

2. Select AlloyDB from the Add Connection panel

3. Enter the necessary authentication properties to connect to AlloyDB.

   The following connection properties are usually required in order to connect to AlloyDB.

   • Server: The host name or IP of the server hosting the AlloyDB database.
   • User: The user which will be used to authenticate with the AlloyDB server.
   • Password: The password which will be used to authenticate with the AlloyDB server.

   You can also optionally set the following:

   • Database: The database to connect to when connecting to the AlloyDB Server. If this is not set, the user's default database will be used.
   • Port: The port of the server hosting the AlloyDB database. This property is set to 5432 by default.

   Authenticating with Standard Authentication

   Standard authentication (using the user/password combination supplied earlier) is the default form of authentication.

   No further action is required to leverage Standard Authentication to connect.

   Authenticating with pg_hba.conf Auth Schemes

   There are additional methods of authentication available which must be enabled in the pg_hba.conf file on the AlloyDB server.

   Find instructions about authentication setup on the AlloyDB Server here.

   Authenticating with MD5 Authentication

   This authentication method must be enabled by setting the auth-method in the pg_hba.conf file to md5.

   Authenticating with SASL Authentication

   This authentication method must be enabled by setting the auth-method in the pg_hba.conf file to scram-sha-256.

   Authenticating with Kerberos

   The authentication with Kerberos is initiated by AlloyDB Server when the ∏ is trying to connect to it. You should set up Kerberos on the AlloyDB Server to activate this authentication method. Once you have Kerberos authentication set up on the AlloyDB Server, see the Kerberos section of the help documentation for details on how to authenticate with Kerberos.

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 AlloyDB connection configured and a PAT generated, Zed can now connect to AlloyDB 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 AlloyDB data through Connect AI.

Step 3: Query live AlloyDB data from the Zed agent

With the integration complete, use the Zed agent panel to explore and interact with live AlloyDB 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 AlloyDB
   • Query the top 5 records from a table in AlloyDB data
3. The agent calls the CData Connect AI MCP Server and returns live results from AlloyDB data

At this point, your Zed agent communicates with the CData Connect AI MCP Server and retrieves live AlloyDB data through remote MCP tools directly from the editor.

Get CData Connect AI

To access 300+ SaaS, Big Data, and NoSQL sources directly from your cloud applications, try CData Connect AI today! Download 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.