How to Access Live SingleStore Data in Visual Studio Code via Cline

Cline is an autonomous coding agent right in your IDE, capable of creating/editing files, running commands, using the browser, and more with your permission every step of the way. When paired with CData Code Assist MCP for SingleStore, you get live access to CRM data within your IDE, enabling you to build, test, and validate data-driven features using real-time schema and records without ever leaving your development environment.

CData Code Assist MCP provides schema-aware context to AI tools — whether you're using it for AI-assisted code generation in IDEs like Cursor and Cline, or for querying live data through chat interfaces like Claude Desktop.

This article outlines how to run CData Code Assist MCP for SingleStore on WSL (Windows Subsystem for Linux) and connect to it from the Cline extension in Visual Studio Code on Windows.

Background

Code Assist MCP is typically designed for clients like Claude Desktop. However, when attempting to use it via the Cline extension in Windows VS Code, the following error occurred:

MCP error -32000: Connection closed

This issue is suspected to be caused by I/O handling problems in the stdio transport implementation on the Windows version of the Cline extension.

• Related GitHub Issue: https://github.com/cline/cline/issues/3464
• Additionally, environment variables such as PATH may not be inherited correctly when launching processes like Java or Node.

Prerequisites

• Visual Studio Code installed on Windows
• Cline extension installed and configured in VS Code
• Windows Subsystem for Linux (WSL) installed with a working Linux distribution (e.g., Ubuntu)
• Java 21+ JRE installed in WSL
• CData Code Assist MCP for SingleStore installed on Windows

Step 1: Authenticate with SingleStore (on Windows)

Before running Code Assist MCP in WSL, you must complete authentication flow in a Windows environment. This ensures all necessary credentials are generated and stored properly. Find and run "CData Code Assist MCP for SingleStore" or execute the JAR file to open the configuration wizard.

java -jar "C:\Program Files\CData\CData Code Assist MCP for SingleStore 20XX\lib\cdata.mcp.singlestore.jar"

Connecting 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.

Configuring Code Assist MCP

Name your configuration (e.g. cdatasinglestore), enter the required connection properties, and click "Connect."

👁 The Code Assist MCP configuration wizard (Google Sheets is shown).

Upon successful connection, the following directory and files will be created:

C:\Users\<username>\AppData\Roaming\CData\singlestore Provider\
 |-- cdatasinglestore.mcp
 |-- (other supporting config files)

Step 2: Copy the Code Assist MCP Configuration into WSL

Next, copy the entire configuration folder from Windows into your WSL environment.

mkdir -p ~/.config/CData/
cp -r /mnt/c/Users/<username>/AppData/Roaming/CData/"singlestore Provider" ~/.config/CData/

Ensure the destination path matches exactly: ~/.config/CData/singlestore Provider/.

Step 3: Install Code Assist MCP on WSL

Install Java and place the Code Assist MCP JAR in the desired location within WSL:

sudo apt update
sudo apt install openjdk-21-jre-headless
sudo mkdir -p /opt/cdata/mcp_singlestore/lib
sudo cp /mnt/c/Program\ Files/CData/CData\ Code\ Assist\ MCP\ for\ SingleStore\ 20XX/lib/cdata.mcp.singlestore.jar /opt/cdata/mcp_singlestore/lib/

Step 4: Configure Cline

Now, configure the Cline extension to launch Code Assist MCP inside WSL using the wsl command.

Create or update cline_mcp_settings.json with the following content:

{
 "mcpServers": {
 "cdatasinglestore": {
 "autoApprove": ["*"],
 "disabled": false,
 "timeout": 60,
 "type": "stdio",
 "command": "wsl",
 "args": [
 "-d",
 "Ubuntu", // Replace with your installed WSL distro name
 "--",
 "/usr/bin/java",
 "-jar",
 "/opt/cdata/mcp_singlestore/lib/cdata.mcp.singlestore.jar",
 "cdatasinglestore"
 ],
 "env": {
 "JAVA_TOOL_OPTIONS": "-Xmx2g"
 }
 }
 }
}

Note: Replace Ubuntu with your actual WSL distribution name (e.g., Ubuntu-22.04). Run wsl -l in PowerShell or CMD to confirm.

Step 5: Interact with Live Data in Cline

From within Visual Studio Code, you can now run MCP commands through the Cline extension.

cdatasinglestore_get_tables
cdatasinglestore_get_columns Orders

If configured correctly, these commands will return a list of available SingleStore objects and metadata, allowing you to interact with your CRM schema in real time.

Try natural language prompts like:

• "Generate a React form to create a new SingleStore Lead."
• "Write a Python function to pull Opportunities closed this quarter."

Build with Code Assist MCP. Deploy with CData Drivers.

Download Code Assist MCP for free and give your AI tools schema-aware access to live SingleStore data during development. When you're ready to move to production, CData SingleStore Drivers deliver the same SQL-based access with enterprise-grade performance, security, and reliability.

Visit the CData Community to share insights, ask questions, and explore what's possible with MCP-powered AI workflows.