Integrate Google's Antigravity Agent with Live SingleStore Data via CData Connect AI

Yazhini G
Yazhini G
Technical Marketing Engineer
Leverage the CData Connect AI Remote MCP Server to enable Antigravity agents to securely access and act on live SingleStore data using the Model Context Protocol.

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 SingleStore data. This enables Antigravity agents to explore schemas, query data, and perform actions without manual data movement or custom API wiring.

This article walks through configuring SingleStore connectivity in Connect AI, generating required access token, registering the CData MCP Server in Antigravity, and validating the integration by querying live SingleStore data from an agent-driven workflow.

Step 1: Configure SingleStore connectivity for Antigravity

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

  1. Log into Connect AI, click Sources, and then click Add Connection
  2. Select SingleStore from the Add Connection panel
  3. Enter the necessary authentication properties to connect to SingleStore.

    The following connection properties are required in order to connect to data.

    • Server: The host name or IP of the server hosting the SingleStore database.
    • Port: The port of the server hosting the SingleStore database.
    • Database (Optional): The default database to connect to when connecting to the SingleStore Server. If this is not set, tables from all databases will be returned.

    Connect Using Standard Authentication

    To authenticate using standard authentication, set the following:

    • User: The user which will be used to authenticate with the SingleStore server.
    • Password: The password which will be used to authenticate with the SingleStore server.

    Connect Using Integrated Security

    As an alternative to providing the standard username and password, you can set IntegratedSecurity to True to authenticate trusted users to the server via Windows Authentication.

    Connect Using SSL Authentication

    You can leverage SSL authentication to connect to SingleStore data via a secure session. Configure the following connection properties to connect to data:

    • SSLClientCert: Set this to the name of the certificate store for the client certificate. Used in the case of 2-way SSL, where truststore and keystore are kept on both the client and server machines.
    • SSLClientCertPassword: If a client certificate store is password-protected, set this value to the store's password.
    • SSLClientCertSubject: The subject of the TLS/SSL client certificate. Used to locate the certificate in the store.
    • SSLClientCertType: The certificate type of the client store.
    • SSLServerCert: The certificate to be accepted from the server.

    Connect Using SSH Authentication

    Using SSH, you can securely login to a remote machine. To access SingleStore data via SSH, configure the following connection properties:

    • SSHClientCert: Set this to the name of the certificate store for the client certificate.
    • SSHClientCertPassword: If a client certificate store is password-protected, set this value to the store's password.
    • SSHClientCertSubject: The subject of the TLS/SSL client certificate. Used to locate the certificate in the store.
    • SSHClientCertType: The certificate type of the client store.
    • SSHPassword: The password that you use to authenticate with the SSH server.
    • SSHPort: The port used for SSH operations.
    • SSHServer: The SSH authentication server you are trying to authenticate against.
    • SSHServerFingerPrint: The SSH Server fingerprint used for verification of the host you are connecting to.
    • SSHUser: Set this to the username that you use to authenticate with the SSH server.
  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 Antigravity. 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 SingleStore connection configured and a PAT generated, Antigravity can now connect to SingleStore data through the CData MCP Server.

Step 2: Configure the CData MCP Server in Antigravity

Next, register the CData MCP Server 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.

  1. Download the Antigravity desktop application and sign in using your Google account
  2. During the initial setup flow, select Agent-driven development when prompted. This mode enables autonomous agents with tool execution capabilities
  3. Once you have completed the Antigravity setup and the IDE is open, you can access the built-in agent interface to manage MCP servers. From the top menu, click Toggle Agent or press Ctrl + Alt + B to open the agent panel
  4. Once the agent panel opens, click the "..." and select MCP Servers from the dropdown
  5. Select Manage MCP Servers from the MCP Store, and click View raw config to open the MCP configuration file
  6. Paste the following json into the file:
    {
        "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==

  7. Save the configuration file
  8. Return to the Manage MCP Servers view and click Refresh to load the new MCP server

Step 3: Query live SingleStore data from Antigravity agent

With the MCP server registered, Antigravity agents can now interact with your live data sources exposed by Connect AI to explore schemas and run queries.

  1. Open the agent panel again using Toggle Agent
  2. Start a new conversation in the agent chat
  3. Start interacting with the agent by entering prompts such as:
    • List all catalogs in my cdata-mcp connection.
    • Show schemas and tables available for SingleStore.
    • Query the top 3 records from a table in SingleStore data.

At this point, your Antigravity agent communicates with the CData Connect AI MCP Server and retrieves live SingleStore data through remote MCP tools.

Get CData Connect AI

To access 300+ SaaS, Big Data, and NoSQL sources directly from your cloud applications, try CData Connect AI today!

Ready to get started?

Learn more about CData Connect AI or sign up for free trial access:

Free Trial