How to Query Live AlloyDB Data in Claude Desktop

Model Context Protocol (MCP) is an emerging, open-source standard for connecting LLMs with external services and data sources. Through MCP Servers, AI clients can perform actions like opening Jira tickets, posting Slack messages, committing GitHub branches and more. With CData Code Assist MCP, these capabilities expand exponentially.

CData Code Assist MCP provides schema-aware context to AI tools — whether you're using it for AI-assisted code generation in IDEs like Cursor, or for querying live data through chat interfaces like Claude Desktop.

In this article, we guide the reader through installing CData Code Assist MCP for AlloyDB, configuring the connection to AlloyDB, and asking questions of the data in Claude Desktop.

Prerequisites

You need to download Claude Desktop (download) and create an account before continuing.

Overview

Here's a quick overview of the steps:

1. Download and install the CData Code Assist MCP for AlloyDB
2. Configure the connection to AlloyDB
3. Ask questions about the data in Claude Desktop

Step 1: Download and install CData Code Assist MCP

1. To begin, navigate to https://www.cdata.com/solutions/codeassist/ and download the CData Code Assist MCP for AlloyDB. 👁 Downloading the CData Code Assist MCP installer
   
2. Find and double-click the installer to begin the installation. 👁 Running the installer for CData Code Assist MCP (Google Sheets is shown.)
   
3. Follow the prompts to complete the installation. 👁 Completing the CData Code Assist MCP installation (Google Sheets is shown).
   

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

Step 2: Configure the connection to AlloyDB

1. After installation, the Code Assist MCP configuration wizard should open automatically. 👁 The Code Assist MCP configuration wizard.
   

   NOTE: If the wizard does not open automatically, search for "CData Code Assist MCP" in the Windows search bar and double-click the application. 👁 Opening the Code Assist MCP configuration wizard (Google Sheets is shown).
   

2. Click the dropdown menu in MCP Configuration > Configuration Name and select "
3. Name the configuration (e.g. "cdataalloydb") and click "OK."

   NOTE: This name is used as the name for the MCP server and as the prefix for all of the MCP Server's tools.

   👁 Naming the configuration.
   

4. Connecting to AlloyDB

   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.

   Enter the appropriate connection properties in the configuration wizard.

   👁 Configuring the Server to connect with a specific Spreadsheet.
   
5. Click "Connect" to authenticate with AlloyDB.
6. Finally, click "Save Configuration" to save the configuration. 👁 Saving the Code Assist MCP configuration.
   

   NOTE: This saves the configuration details to a separate file and updates the Claude Desktop configuration file (claude_desktop_config.json) to start Code Assist MCP when the Claude Desktop client starts.

With Code Assist MCP configured, you are ready to start asking questions of your live data from Claude.

Step 3: Ask AI for answers from live AlloyDB data

Now that we have installed Code Assist MCP and configured a connection, we are ready to start with AlloyDB data in Claude Desktop.

1. Open Claude Desktop. It may take a moment for Code Assist MCP to start, but you will see the list of servers and tools available in the Claude interface (look for the settings icon below the prompt bar). 👁 The MCP servers menu showing available connections in Claude Desktop
   

   You can individually enable and disable specific tools by clicking on the server name. 👁 The expanded tool list for Code Assist MCP in Claude Desktop
   

2. Now that you have connected, you can ask Claude questions about the AlloyDB data. For example: "Can you give me a quantitative analysis about my closed-won opportunities by industry?"

   NOTE: Claude may need to explore the AlloyDB data to make sense of it before it can begin answering questions of the data. The tabular model presented by CData alongside the database tools available simplify the data exploration and analysis for an LLM.

   👁 Claude Desktop displaying a quantitative analysis of live data
   

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.