Build SingleStore-Powered Applications in GitHub Copilot with CData Code Assist MCP

GitHub Copilot is an AI-powered coding assistant that integrates directly into Visual Studio Code and other IDEs. With support for MCP, GitHub Copilot can connect to local tools and enterprise data sources, enabling natural language interaction with live systems during development.

Model Context Protocol (MCP) is an open standard for connecting LLM clients to external services through structured tool interfaces. MCP servers expose capabilities such as schema discovery and live querying, allowing AI agents to retrieve and reason over real-time data safely and consistently.

In this article, we guide you through installing the CData Code Assist MCP for SingleStore, configuring the connection to SingleStore, connecting the Code Assist MCP add-on to GitHub Copilot, and querying live SingleStore data from within Visual Studio Code.

Prerequisites

• Visual Studio Code is installed on your machine
• GitHub Copilot Chat extension is enabled in Visual Studio Code
• CData Code Assist MCP for SingleStore has been installed

Step 1: Download and install the CData Code Assist MCP for SingleStore

1. To begin, download the CData Code Assist MCP for SingleStore
2. Find and double-click the installer to begin the installation
3. Run the installer and follow the prompts to complete the installation

When the installation is complete, you are ready to configure your Code Assist MCP add-on by connecting to SingleStore.

Step 2: Configure the connection to SingleStore

1. After installation, open the CData Code Assist MCP for SingleStore configuration wizard

   NOTE: If the wizard does not open automatically, search for "CData Code Assist MCP for SingleStore" in the Windows search bar and open the application.

   
2. In MCP Configuration > Configuration Name, either select an existing configuration or choose to create a new one
3. Name the configuration (e.g. "cdata_singlestore") and click OK

4. Enter the appropriate connection properties in the configuration wizard

   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.
   
5. Click Connect to authenticate with SingleStore
6. Click Save & Test to finalize the connection

This process creates a .mcp configuration file that GitHub Copilot will reference when launching the Code Assist MCP add-on. Now with your Code Assist MCP add-on configured, you are ready to connect it to GitHub Copilot.

Step 3: Connect the Code Assist MCP add-on to GitHub Copilot

1. Download and install Visual Studio Code and enable the GitHub Copilot Chat extension

Option 1: Manually add the MCP configuration

1. Open or create the mcp.json file:
   • For global configuration: %%APPDATA%%/Roaming/Code/User/mcp.json
   • For project-specific configuration: /.vscode/mcp.json
2. Add the JSON code shown below and save the file

{
  "servers": {
    "cdata_singlestore": {
      "command": "C:\Program Files\CData\CData Code Assist MCP for SingleStore\jre\bin\java.exe",
      "args": [
        "-Dfile.encoding=UTF-8",
        "-jar",
        "C:\Program Files\CData\CData Code Assist MCP for SingleStore\lib\cdata.mcp.singlestore.jar",
        "cdata_singlestore"
      ]
    }
  }
}

NOTE: The command value should point to your Java 17+ java.exe executable, and the JAR path should point to the installed CData Code Assist MCP add-on .jar file. The final argument must match the MCP configuration name you saved in the CData configuration wizard (e.g. "cdata_singlestore").

Option 2: Copy the MCP configuration from the CData Code Assist MCP for SingleStore UI

1. After saving and testing your connection in the configuration wizard, click Next
2. Select Github Copilot from the AI MCP Tool dropdown
3. Follow the MCP Client Instructions to create the required configuration file
4. Copy the displayed JSON code and paste it into your configuration file

Step 4: Query live SingleStore data in GitHub Copilot

1. Launch Visual Studio Code and open the GitHub Copilot Chat interface. Select the tool icon to enable the configured Code Assist MCP add-on
2. Ask questions about your SingleStore data using natural language. For example:

   "List all tables available in my SingleStore data data connection."

   
3. Start building with natural language prompts:

   For my project, data from the Orders is very important. Pull data from the most important columns like ShipName and ShipCity.
   

GitHub Copilot is now fully integrated with CData Code Assist MCP for SingleStore and can use the MCP tools to explore schemas and execute live queries against SingleStore.

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.