How to Access Live Anaplan 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 MCP Server for Anaplan, 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 MCP Server 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 MCP Server for Anaplan on WSL (Windows Subsystem for Linux) and connect to it from the Cline extension in Visual Studio Code on Windows.
Background
MCP Server 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 MCP Server for Anaplan installed on Windows
Step 1: Authenticate with Anaplan (on Windows)
Before running 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 "CData MCP Server for Anaplan" or execute the JAR file to open the configuration wizard.
java -jar "C:\Program Files\CData\CData MCP Server for Anaplan 20XX\lib\cdata.mcp.anaplan.jar"
Connecting to Anaplan
Authenticating to Anaplan
The driver supports authenticating with Basic, Certificate, or OAuth. In every case, set Region to the region where your Anaplan account data is hosted (e.g., US1, which is the default).
Using Basic Authentication
Set AuthScheme to Basic, then supply your Anaplan User and Password. If your workspace uses single sign-on (SSO), you must be assigned as an Exception User to use Basic authentication.
Using Certificate Authentication
Set AuthScheme to Certificate, then supply the Certificate, CertificateType, and PrivateKey properties (and the matching CertificatePassword / PrivateKeyPassword if either is encrypted). The certificate must be a CA-issued X.509 certificate registered with your Anaplan tenant administrator.
Using OAuth Authentication
Register a custom OAuth application in Anaplan, then set the following properties:
- OAuthClientId: The client Id assigned when you registered your custom OAuth application.
- OAuthClientSecret: The client secret assigned when you registered your custom OAuth application.
- CallbackURL: The redirect URI defined when you registered your application.
- InitiateOAuth: Set to GETANDREFRESH to have the driver manage the OAuth token exchange and refresh automatically.
See the Getting Started chapter of the help documentation for a guide to creating a custom OAuth app and using OAuth.
Configuring MCP Server
Name your configuration (e.g. cdataanaplan), 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\anaplan Provider\ |-- cdataanaplan.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/"anaplan Provider" ~/.config/CData/
Ensure the destination path matches exactly: ~/.config/CData/anaplan Provider/.
Step 3: Install 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_anaplan/lib sudo cp /mnt/c/Program\ Files/CData/CData\ Code\ Assist\ MCP\ for\ Anaplan\ 20XX/lib/cdata.mcp.anaplan.jar /opt/cdata/mcp_anaplan/lib/
Step 4: Configure Cline
Now, configure the Cline extension to launch MCP Server inside WSL using the wsl command.
Create or update cline_mcp_settings.json with the following content:
{
"mcpServers": {
"cdataanaplan": {
"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_anaplan/lib/cdata.mcp.anaplan.jar",
"cdataanaplan"
],
"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.
cdataanaplan_get_tables cdataanaplan_get_columns Sales
If configured correctly, these commands will return a list of available Anaplan 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 Anaplan Lead."
- "Write a Python function to pull Opportunities closed this quarter."
Build with MCP Server. Deploy with CData Drivers.
Download MCP Server for free and give your AI tools schema-aware access to live Anaplan data during development. When you're ready to move to production, CData Anaplan 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.