How to Access Live JSON Services 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 the CData MCP Server for JSON, 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 JSON 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 JSON installed on Windows

Step 1: Authenticate with JSON (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 JSON" or execute the MCP Server JAR file to open the configuration wizard.

java -jar "C:\Program Files\CData\CData MCP Server for JSON 2024\lib\cdata.mcp.json.jar"

Connecting to JSON

See the Getting Started chapter in the data provider documentation to authenticate to your data source: The data provider models JSON APIs as bidirectional database tables and JSON files as read-only views (local files, files stored on popular cloud services, and FTP servers). The major authentication schemes are supported, including HTTP Basic, Digest, NTLM, OAuth, and FTP. See the Getting Started chapter in the data provider documentation for authentication guides.

After setting the URI and providing any authentication values, set DataModel to more closely match the data representation to the structure of your data.

The DataModel property is the controlling property over how your data is represented into tables and toggles the following basic configurations.

• Document (default): Model a top-level, document view of your JSON data. The data provider returns nested elements as aggregates of data.
• FlattenedDocuments: Implicitly join nested documents and their parents into a single table.
• Relational: Return individual, related tables from hierarchical data. The tables contain a primary key and a foreign key that links to the parent document.

See the Modeling JSON Data chapter for more information on configuring the relational representation. You will also find the sample data used in the following examples. The data includes entries for people, the cars they own, and various maintenance services performed on those cars.

Configuring the CData MCP Server

Name your MCP Server (e.g. cdatajson), 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\json Provider\
 |-- cdatajson.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/"json Provider" ~/.config/CData/

Ensure the destination path matches exactly: ~/.config/CData/json 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_json/lib
sudo cp /mnt/c/Program\ Files/CData/CData\ MCP\ Server\ for\ JSON\ 2024/lib/cdata.mcp.json.jar /opt/cdata/mcp_json/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": {
    "cdatajson": {
      "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_json/lib/cdata.mcp.json.jar",
        "cdatajson"
      ],
      "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.

cdatajson_get_tables
cdatajson_get_columns people

If configured correctly, these commands will return a list of available JSON 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 JSON 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, 30-day trial or visit the CData Community to share insights, ask questions, and help shape the future of enterprise-ready AI.