How to Connect to Live SingleStore Data from Gemini CLI (via CData Connect AI)

Gemini CLI is a command-line interface tool that provides direct access to Google's Gemini AI models for code generation, text analysis, and conversational AI capabilities. When combined with CData Connect AI Remote MCP, you can leverage Gemini CLI to interact with your SingleStore data in real-time through natural language queries. This article outlines the process of connecting to SingleStore using Connect AI Remote MCP and configuring Gemini CLI to interact with your SingleStore data.

CData Connect AI offers a dedicated cloud-to-cloud interface for connecting to SingleStore data. The CData Connect AI Remote MCP Server enables secure communication between Gemini CLI and SingleStore. This allows you to ask questions and take actions on your SingleStore data using natural language through Gemini CLI, all without the need for data replication to a natively supported database. With its inherent optimized data processing capabilities, CData Connect AI efficiently channels all supported SQL operations, including filters and JOINs, directly to SingleStore. This leverages server-side processing to swiftly deliver the requested SingleStore data.

In this article, we show how to configure Gemini CLI to conversationally explore (or Vibe Query) your data using natural language. With Connect AI you can query and interact with live SingleStore data, plus hundreds of other sources.

Step 1: Configure SingleStore Connectivity for Gemini CLI

Connectivity to SingleStore from Gemini CLI is made possible through CData Connect AI Remote MCP. To interact with SingleStore data from Gemini CLI, we 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 in the Add SingleStore Connection page and update the User-based permissions.

Add a Personal Access Token

A Personal Access Token (PAT) is used to authenticate the connection to Connect AI from Gemini CLI. It is best practice to create a separate PAT for each service to maintain granularity of access.

1. Click on the Gear icon () at the top right of the Connect AI app to open the settings page.
2. On the Settings page, go to the Access Tokens section and click Create PAT.
3. Give the PAT a name and click Create.
4. The personal access token is only visible at creation, so be sure to copy it and store it securely for future use.

With the connection configured and a PAT generated, we are ready to connect to SingleStore data from Gemini CLI.

Step 2: Configure Gemini CLI for CData Connect AI

Follow these steps to configure Gemini CLI to connect to CData Connect AI:

1. Ensure Gemini CLI is installed on your system. If not, install it using npm:

   npm install -g @google-gemini/cli

2. Locate your Gemini CLI settings file. If the file doesn't exist, create it:
   • Linux/Unix/Mac: ~/.gemini/settings.json
   • Windows: %USERPROFILE%\.gemini\settings.json
3. Add the CData Connect AI Remote MCP Server to the mcpServers object in your settings file. Replace YOUR_EMAIL and YOUR_PAT with your Connect AI email address and the PAT created previously:

   {
     "mcpServers": {
       "cdata-connect-cloud": {
         "httpUrl": "https://mcp.cloud.cdata.com/mcp",
         "headers": {
           "Authorization": "Basic YOUR_EMAIL:YOUR_PAT"
         }
       }
     }
   }    

   For example, if your email is [email protected] and your PAT is Uu90pt5vEO..., the Authorization header would be:

   "Authorization": "Basic [email protected]:Uu90pt5vEO..."

4. Save the settings file. Gemini CLI will now use the CData Connect AI MCP Server for data operations.

Step 3: Query Live SingleStore Data with Natural Language

With Gemini CLI configured and connected to CData Connect AI, you can now interact with your SingleStore data using natural language queries. The MCP integration allows you to ask questions and receive responses from the SingleStore data source in real-time.

Start using Gemini CLI to explore your data:

1. Open your terminal and start a Gemini CLI session:

   gemini

2. You can now use natural language to query your SingleStore data. For example:
   • "Show me all customers from the last 30 days"
   • "What are my top performing products?"
   • "Analyze sales trends for Q4"
   • "List all active projects with their current status"
3. Gemini CLI will automatically translate your natural language queries into appropriate SQL queries and execute them against your SingleStore data through the CData Connect AI MCP Server.

The combination of Gemini CLI's natural language processing capabilities and CData Connect AI's robust data connectivity enables you to explore and analyze your SingleStore data without writing complex SQL queries or needing deep technical knowledge of the underlying data structure.

Get CData Connect AI

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