Build AlloyDB-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 AlloyDB, configuring the connection to AlloyDB, connecting the Code Assist MCP add-on to GitHub Copilot, and querying live AlloyDB 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 AlloyDB has been installed

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

1. To begin, download the CData Code Assist MCP for AlloyDB 👁 Downloading the CData Code Assist MCP add-on installer
   
2. Find and double-click the installer to begin the installation
3. Run the installer and follow the prompts to complete the installation 👁 Completing the CData Code Assist MCP add-on installation
   

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

Step 2: Configure the connection to AlloyDB

1. After installation, open the CData Code Assist MCP for AlloyDB configuration wizard 👁 The CData Code Assist MCP add-on configuration wizard
   

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

   👁 Opening the CData Code Assist MCP add-on configuration wizard (Google Sheets is shown).
   
2. In MCP Configuration > Configuration Name, either select an existing configuration or choose to create a new one 👁 Creating a new configuration
   
3. Name the configuration (e.g. "cdata_alloydb") and click OK 👁 Naming the configuration
   

4. Enter the appropriate connection properties in the configuration wizard

   The following connection properties are usually required in order to connect to AlloyDB.

   • Server: The host name or IP of the server hosting the AlloyDB database.
   • User: The user which will be used to authenticate with the AlloyDB server.
   • Password: The password which will be used to authenticate with the AlloyDB server.

   You can also optionally set the following:

   • Database: The database to connect to when connecting to the AlloyDB Server. If this is not set, the user's default database will be used.
   • Port: The port of the server hosting the AlloyDB database. This property is set to 5432 by default.

   Authenticating with Standard Authentication

   Standard authentication (using the user/password combination supplied earlier) is the default form of authentication.

   No further action is required to leverage Standard Authentication to connect.

   Authenticating with pg_hba.conf Auth Schemes

   There are additional methods of authentication available which must be enabled in the pg_hba.conf file on the AlloyDB server.

   Find instructions about authentication setup on the AlloyDB Server here.

   Authenticating with MD5 Authentication

   This authentication method must be enabled by setting the auth-method in the pg_hba.conf file to md5.

   Authenticating with SASL Authentication

   This authentication method must be enabled by setting the auth-method in the pg_hba.conf file to scram-sha-256.

   Authenticating with Kerberos

   The authentication with Kerberos is initiated by AlloyDB Server when the ∏ is trying to connect to it. You should set up Kerberos on the AlloyDB Server to activate this authentication method. Once you have Kerberos authentication set up on the AlloyDB Server, see the Kerberos section of the help documentation for details on how to authenticate with Kerberos. 👁 Configuring the Code Assist MCP add-on connection
   

5. Click Connect to authenticate with AlloyDB
6. Click Save & Test to finalize the connection 👁 Saving and testing the Code Assist MCP add-on configuration
   

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:
2. Add the JSON code shown below and save the file

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

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_alloydb").

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

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

Step 4: Query live AlloyDB 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 👁 Enabling the CData Code Assist MCP add-on in GitHub Copilot
   
2. Ask questions about your AlloyDB data using natural language. For example:

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

   👁 Querying live data from GitHub Copilot
   
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 AlloyDB and can use the MCP tools to explore schemas and execute live queries against AlloyDB.

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 AlloyDB data during development. When you're ready to move to production, CData AlloyDB 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.