![]() |
VOOZH | about |
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 explains how to configure AlloyDB connectivity in Connect AI, register the CData MCP Server in Zed, and query live AlloyDB data from the Zed agent panel.
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.
The following connection properties are usually required in order to connect to AlloyDB.
You can also optionally set the following:
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.
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.
This authentication method must be enabled by setting the auth-method in the pg_hba.conf file to md5.
This authentication method must be enabled by setting the auth-method in the pg_hba.conf file to scram-sha-256.
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.
π Configuring a connection (Salesforce is shown)
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.
With the AlloyDB connection configured and a PAT generated, Zed can now connect to AlloyDB data through Connect AI.
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.
{
"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...
π Pasting the CData Connect AI MCP Server configurationZed 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.
With the MCP server registered and an LLM provider configured, the Zed agent is ready to query live AlloyDB data through Connect AI.
With the integration complete, use the Zed agent panel to explore and interact with live AlloyDB data through natural language prompts.
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.
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.
Learn more about CData Connect AI or sign up for free trial access:
Free Trial