Model Context Protocol (MCP) finally gives AI models a way to access the business data needed to make them really useful at work. CData MCP Servers have the depth and performance to make sure AI has access to all of the answers.
Try them now for free →How to Access Live SQL Server Data in Visual Studio Code via Cline
Run the CData MCP Server for SQL Server on Windows Subsytem for Linux (WSL) and connect to live SQL Server data from the Cline extension in Visual Studio Code.
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 the CData MCP Server for SQL Server, 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.
This article outlines how to run the CData MCP Server for SQL Server on WSL (Windows Subsystem for Linux) and connect to it from the Cline extension in Visual Studio Code on Windows.
Background
CData MCP Servers are typically designed for clients like Claude Desktop. However, when attempting to use the server 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 MCP Server for SQL Server installed on Windows
Step 1: Authenticate with SQL Server (on Windows)
Before running the MCP Server in WSL, you must complete authentication flow in a Windows environment. This ensures all necessary credentials are generated and stored properly. Find and run the "CData MCP Server for SQL Server" or execute the MCP Server JAR file to open the configuration wizard.
java -jar "C:\Program Files\CData\CData MCP Server for SQL Server 2024\lib\cdata.mcp.sql.jar"
Connecting to SQL Server
Connecting to Microsoft SQL Server
Connect to Microsoft SQL Server using the following properties:
- Server: The name of the server running SQL Server.
- User: The username provided for authentication with SQL Server.
- Password: The password associated with the authenticating user.
- Database: The name of the SQL Server database.
Connecting to Azure SQL Server and Azure Data Warehouse
You can authenticate to Azure SQL Server or Azure Data Warehouse by setting the following connection properties:
- Server: The server running Azure. You can find this by logging into the Azure portal and navigating to "SQL databases" (or "SQL data warehouses") -> "Select your database" -> "Overview" -> "Server name."
- User: The name of the user authenticating to Azure.
- Password: The password associated with the authenticating user.
- Database: The name of the database, as seen in the Azure portal on the SQL databases (or SQL warehouses) page.
Configuring the CData MCP Server
Name your MCP Server (e.g. cdatasql), enter the required connection properties, and click "Connect."
Upon successful connection, the following directory and files will be created:
C:\Users\<username>\AppData\Roaming\CData\sql Provider\ |-- cdatasql.mcp |-- (other supporting config files)
Step 2: Copy the MCP Server 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/"sql Provider" ~/.config/CData/
Ensure the destination path matches exactly: ~/.config/CData/sql Provider/.
Step 3: Install the MCP Server on WSL
Install Java and place the MCP Server JAR in the desired location within WSL:
sudo apt update sudo apt install openjdk-21-jre-headless sudo mkdir -p /opt/cdata/mcp_sql/lib sudo cp /mnt/c/Program\ Files/CData/CData\ MCP\ Server\ for\ SQL Server\ 2024/lib/cdata.mcp.sql.jar /opt/cdata/mcp_sql/lib/
Step 4: Configure Cline
Now, configure the Cline extension to launch the MCP Server inside WSL using the wsl command.
Create or update cline_mcp_settings.json with the following content:
{
"mcpServers": {
"cdatasql": {
"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_sql/lib/cdata.mcp.sql.jar",
"cdatasql"
],
"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.
cdatasql_get_tables cdatasql_get_columns Orders
If configured correctly, these commands will return a list of available SQL Server 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 SQL Server Lead."
- "Write a Python function to pull Opportunities closed this quarter."
Connect your AI to your data today!
CData MCP Servers make it easier than ever for LLMs to work with live enterprise data. To explore the technology hands-on, download a free MCP Server or visit the CData Community to share insights, ask questions, and help shape the future of enterprise-ready AI.