Integrate Cline with Live SingleStore Data via CData Connect AI

Cline is an autonomous AI coding agent that runs inside modern IDEs such as VS Code and Cursor. It enables developers to build agent-driven workflows that can reason through tasks, execute actions, and interact with external systems directly from the editor using a structured execution model.

By integrating Cline with CData Connect AI through the built-in MCP (Model Context Protocol) Server, the agent gains the ability to query, analyze, and act on live SingleStore data in real time. This integration bridges Cline's in-IDE agent framework with the governed enterprise connectivity of CData Connect AI, ensuring all data access runs securely against authorized sources without manual data movement.

This article outlines the steps to configure SingleStore connectivity in Connect AI, generate the required personal access token, register the Connect AI MCP Server in Cline, and verify that the agent can successfully interact with live SingleStore data from within the IDE.

Step 1: Configure SingleStore connectivity for Cline

Connectivity to SingleStore from Cline is made possible through CData Connect AI's Remote MCP Server. To interact with SingleStore data from Cline, 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 Cline. 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, Cline can now connect to SingleStore data through the CData Connect Ai.

Step 2: Install and set up Cline

Cline is distributed as an IDE extension and can be installed in environments such as VS Code or Cursor. In this example, Cursor is used, but the steps are identical for supported IDEs.

1. Open Cursor and install the Cline extension from the Extensions Marketplace
2. Complete the initial Cline setup flow, including model selection and permission prompts
3. After setup is complete, the Cline agent panel opens automatically inside the IDE

Step 3: Add the Connect AI Remote MCP Server

Once Cline is running, add the CData Connect AI Remote MCP Server so the agent can access live SingleStore data through Connect AI.

1. In the Cline panel, click MCP Servers
2. Open Remote Servers and click Edit Configuration
3. This opens a JSON configuration file. Paste the configuration below

   {
     "mcpServers": {
       "mcp": {
         "url": "https://mcp.cloud.cdata.com/mcp",
         "type": "streamableHttp",
         "headers": {
           "Authorization": "Basic your_email:your_PAT"
         },
         "disabled": false,
         "autoApprove": []
       }
     }
   }
   

   Note: Cline will use Basic authentication with Connect AI. Combine your Connect AI user email and the PAT you created earlier. For example, [email protected]:ABC123...XYZ789 and add the value for the Authorization header like, Basic [email protected]:ABC123...XYZ789.

   
4. Save the file and return to the MCP Servers screen to confirm the server is listed and enabled

Step 4: Query live data from Cline

With the MCP server registered, Cline can now interact with live data sources exposed by Connect AI.

1. Click the icon in the Cline panel to start a New Task/Chat
2. At the bottom of the chat window, confirm that the configured MCP server is selected
3. Start interacting with the agent by entering prompts such as:
   • List connections
   • Show schemas for a catalog
   • Query recent records from SingleStore data
   

Cline is now fully configured to access and query live SingleStore data through the CData Connect AI Remote MCP Server, enabling real-time, data-driven workflows directly from your IDE.

Get CData Connect AI

To access 300+ SaaS, Big Data, and NoSQL sources through secure, AI-ready interfaces, try CData Connect AI today.