![]() |
VOOZH | about |
Antigravity is an AI-native development environment designed around autonomous and semi-autonomous agents. It allows developers to run agent-driven workflows directly inside the editor, combining planning, execution, and tool usage in a single interface.
By integrating Antigravity with CData Connect AI through the built-in MCP (Model Context Protocol) Server, agents gain governed, real-time access to live AlloyDB data. This enables Antigravity agents to explore schemas, query data, and perform actions without manual data movement or custom API wiring.
This article explains how to configure AlloyDB connectivity in Connect AI, generate the required access token, register CData Connect AI in Antigravity, and validate the integration by querying live AlloyDB data from an agent-driven workflow.
Connectivity to AlloyDB from Antigravity is made possible through CData Connect AI's Remote MCP Server. To interact with AlloyDB data from Antigravity, 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 Antigravity. 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, Antigravity can now connect to AlloyDB data through CData Connect AI.
Next, register Connect AI in Antigravity. Antigravity reads MCP server definitions from a raw configuration file, allowing agents to dynamically discover and invoke the sources exposed by Connect AI.
{
"mcpServers": {
"cdata-mcp": {
"serverUrl": "https://mcp.cloud.cdata.com/mcp",
"headers": {
"Authorization": "Basic your_base64_encoded_email_PAT",
"Content-Type": "application/json"
}
}
}
}
Note: Antigravity will use Basic authentication with Connect AI. Combine your Connect AI user email and the PAT you created earlier and base64 encode the value. For example, given username and PAT like [email protected]:ABC123...XYZ789, the value for the Authorization header is something like: Basic dXNlckBteWRvbWFpbjphSzkvbVB4Mi9Rcjd2TjQvTHc4Qi96WTZqQzMvRnQ1SGcxL0RzMFVlL01iWHdKdg==
π Editing the Config fileWith the MCP server registered, Antigravity agents can now interact with your live data sources exposed by Connect AI to explore schemas and run queries.
At this point, your Antigravity agent communicates with the CData Connect AI MCP Server and retrieves live AlloyDB data through remote MCP tools.
To access hundreds of SaaS, Big Data, and NoSQL sources directly from your cloud applications, try CData Connect AI today!
Learn more about CData Connect AI or sign up for free trial access:
Free Trial