Integrate Devin with Live AlloyDB Data Using CData Connect AI

Devin is an AI software engineer from Cognition that plans, writes, and tests code in autonomous sessions. It supports the model context protocol (MCP) through its built-in MCP marketplace, allowing you to install remote MCP servers and give Devin access to external tools and live data sources.

By integrating Devin with CData Connect AI through the built-in MCP Server, Devin gains governed, real-time access to live AlloyDB data. You can list catalogs, explore schemas, and query records from AlloyDB data using natural language prompts, with all data access running securely against authorized sources.

This article explains how to configure AlloyDB connectivity in Connect AI, install the CData Connect AI MCP Server from the Devin MCP marketplace, and verify the integration by querying live AlloyDB data from a Devin session.

Step 1: Configure AlloyDB connectivity for Devin

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

1. Log into Connect AI, click Sources, and then click Add Connection

2. Select AlloyDB from the Add Connection panel

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.

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

With the AlloyDB connection configured, Devin can now connect to AlloyDB data through Connect AI.

Step 2: Install the Connect AI MCP Server in Devin

Next, install the CData Connect AI MCP Server from the Devin MCP servers list so your sessions can discover and call live data tools through Connect AI.

Note: Installing MCP servers in Devin requires the Manage MCP Servers permission. If you don't have this permission, use the Suggest option or contact your organization admin.

1. Log into Devin and navigate to Settings and Connections, then select the MCP servers tab
2. Search for CData Connect AI in the marketplace and select the verified listing

3. Click Install and enable. When prompted, complete the OAuth flow to authenticate with your Connect AI account
4. Once installed, confirm the Enable in sessions toggle is on and click Test tools. Devin validates the connection and lists the available Connect AI tools, such as getCatalogs, getSchemas, getTables, and queryData

With the MCP server installed and enabled, the Connect AI tools are available to every Devin session in your workspace.

Step 3: Query live AlloyDB data from Devin

With the integration complete, start a Devin session and interact with live AlloyDB data through natural language prompts.

1. From the Devin home page, start a new session
2. In the session prompt, ask Devin to work with your Connect AI data, for example:
   • Can you list the connections in CData Connect AI
   • Show the available schemas and tables for AlloyDB
   • Query the top 5 records from a table in AlloyDB
3. Devin calls the Connect AI MCP Server and returns live results from AlloyDB data directly in the session. You can follow the tool calls, inputs, and outputs in the Progress panel

At this point, Devin communicates with the Connect AI MCP Server and retrieves live AlloyDB data through remote MCP tools directly from your sessions, whether you're exploring data, building features against it, or automating engineering tasks.

Get started with CData Connect AI

To access hundreds of SaaS, big data, and NoSQL sources directly from your cloud applications, try CData Connect AI today. Download a free 14-day trial of CData Connect AI, and our Support Team is available to help with any questions you have.