Integrate Cline with Live AlloyDB Data via CData Connect AI

Cline is an autonomous AI coding agent that runs inside modern IDEs such as VS Code and Cursor. It enables developers to build agent-driven workflows that can reason through tasks, execute actions, and interact with external systems directly from the editor using a structured execution model.

By integrating Cline with CData Connect AI through the built-in MCP (Model Context Protocol) Server, the agent gains the ability to query, analyze, and act on live AlloyDB data in real time. This integration bridges Cline's in-IDE agent framework with the governed enterprise connectivity of CData Connect AI, ensuring all data access runs securely against authorized sources without manual data movement.

This article outlines the steps to configure AlloyDB connectivity in Connect AI, generate the required personal access token, register the Connect AI MCP Server in Cline, and verify that the agent can successfully interact with live AlloyDB data from within the IDE.

Step 1: Configure AlloyDB connectivity for Cline

Connectivity to AlloyDB from Cline is made possible through CData Connect AI's Remote MCP Server. To interact with AlloyDB data from Cline, start by creating and configuring a AlloyDB connection in CData Connect AI.

1. Log into Connect AI, click Sources, and then click Add Connection
👁 Adding a connection in Connect AI

2. Select AlloyDB from the Add Connection panel
👁 Selecting data source

3. Enter the necessary authentication properties to connect 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. 👁 Configuring a connection (Salesforce is shown)
   

4. Click Save & Test
5. Navigate to the Permissions tab and update user-based permissions
👁 Updating permissions

Add a Personal Access Token

A Personal Access Token (PAT) is used to authenticate the connection to Connect AI from Cline. It is best practice to create a separate PAT for each integration to maintain granular access control.

1. Click the gear icon () at the top right of the Connect AI app to open Settings
2. On the Settings page, go to the Access Tokens section and click Create PAT
3. Give the PAT a descriptive name and click Create
👁 Creating a new PAT

4. Copy the token when displayed and store it securely. It will not be shown again

With the AlloyDB connection configured and a PAT generated, Cline can now connect to AlloyDB data through the CData Connect Ai.

Step 2: Install and set up Cline

Cline is distributed as an IDE extension and can be installed in environments such as VS Code or Cursor. In this example, Cursor is used, but the steps are identical for supported IDEs.

1. Open Cursor and install the Cline extension from the Extensions Marketplace 👁 Installing the Cline extension in Cursor
   
2. Complete the initial Cline setup flow, including model selection and permission prompts
3. After setup is complete, the Cline agent panel opens automatically inside the IDE

Step 3: Add the Connect AI Remote MCP Server

Once Cline is running, add the CData Connect AI Remote MCP Server so the agent can access live AlloyDB data through Connect AI.

1. In the Cline panel, click MCP Servers 👁 Opening MCP Servers in Cline
   
2. Open Remote Servers and click Edit Configuration 👁 Editing remote MCP server configuration
   
3. This opens a JSON configuration file. Paste the configuration below

   {
    "mcpServers": {
    "mcp": {
    "url": "https://mcp.cloud.cdata.com/mcp",
    "type": "streamableHttp",
    "headers": {
    "Authorization": "Basic your_email:your_PAT"
    },
    "disabled": false,
    "autoApprove": []
    }
    }
   }
   

   Note: Cline will use Basic authentication with Connect AI. Combine your Connect AI user email and the PAT you created earlier. For example, [email protected]:ABC123...XYZ789 and add the value for the Authorization header like, Basic [email protected]:ABC123...XYZ789.

   👁 Configuring MCP server
   
4. Save the file and return to the MCP Servers screen to confirm the server is listed and enabled 👁 Configured MCP server listed in Cline
   

Step 4: Query live data from Cline

With the MCP server registered, Cline can now interact with live data sources exposed by Connect AI.

1. Click the icon in the Cline panel to start a New Task/Chat 👁 Starting a new chat in Cline
   
2. At the bottom of the chat window, confirm that the configured MCP server is selected 👁 Selecting the configured MCP server
   
3. Start interacting with the agent by entering prompts such as:
   • List connections
   • Show schemas for a catalog
   • Query recent records from AlloyDB data
   👁 Sample output from querying through the MCP server
   

Cline is now fully configured to access and query live AlloyDB data through the CData Connect AI Remote MCP Server, enabling real-time, data-driven workflows directly from your IDE.

Get CData Connect AI

To access hundreds of SaaS, Big Data, and NoSQL sources through secure, AI-ready interfaces, try CData Connect AI today.