Integrate OpenCode with Live AlloyDB Data via CData Connect AI

OpenCode is an open source AI coding agent that connects to a wide range of LLM providers. It supports the model context protocol (MCP), allowing you to configure local or remote MCP servers in its configuration files to add external tools and data sources and give the agent access to live data.

By integrating OpenCode with CData Connect AI through the built-in MCP Server, OpenCode 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, generate the required personal access token, install OpenCode, add the Connect AI MCP Server in the project configuration file, configure an LLM provider, and verify the integration by querying live AlloyDB data from OpenCode.

Step 1: Configure AlloyDB connectivity for OpenCode

Connectivity to AlloyDB from OpenCode is made possible through Connect AI's Remote MCP Server. To interact with AlloyDB data from OpenCode, 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

Add a Personal Access Token

A Personal Access Token (PAT) is used to authenticate the connection to Connect AI from OpenCode. 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

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, OpenCode can now connect to AlloyDB data through Connect AI.

Step 2: Install OpenCode and configure the Connect AI MCP Server

Next, install OpenCode, add the Connect AI Remote MCP Server in your project configuration file, and configure an LLM provider so the agent can discover and call live data tools through Connect AI.

1. Download and install OpenCode by following the official installation guide
2. Create a new folder for your project, or open an existing project directory
3. In the root of that directory, create a file named opencode.json and paste the following configuration:

   {
     "$schema": "https://opencode.ai/config.json",
     "mcp": {
       "cdata-connect-ai": {
         "type": "remote",
         "url": "https://mcp.cloud.cdata.com/mcp",
         "enabled": true,
         "oauth": false,
         "headers": {
           "Authorization": "Basic your_base64_encoded_email_PAT"
         },
         "timeout": 30000
       }
     }
   }
   		

   Note: OpenCode will use Basic authentication with Connect AI. Combine your Connect AI user email and the PAT you created earlier in the format email:PAT, base64 encode the combined string, and prefix it with Basic. For example, given [email protected]:ABC123...XYZ789, the Authorization header value becomes something like: Basic dXNlckBkb21haW4uY29tOkFCQzEyMy4uLlhZWjc4OQ==

4. Open the project directory in OpenCode. Select the project from the project dropdown, or click Add project to point OpenCode at the folder that contains opencode.json
5. Configure an LLM provider so the agent can interpret prompts and call MCP tools. Open the model selector (Ctrl + '), choose a provider such as OpenAI, Anthropic, or Google, and enter your API key

With the MCP server added in opencode.json and an LLM provider configured, OpenCode is ready to query live AlloyDB data through Connect AI.

Step 3: Query live AlloyDB data from OpenCode

With the integration complete, use OpenCode to interact with live AlloyDB data through natural language prompts handled by the configured LLM.

1. In a new session, type a prompt in the chat input, for example:
   • Use the cdata-connect-ai tools to list all available catalogs
   • Show the available schemas and tables for AlloyDB
   • Query the top 5 records from a table in AlloyDB
2. OpenCode calls the Connect AI MCP Server and returns live results from AlloyDB data

At this point, OpenCode communicates with the Connect AI MCP Server and retrieves live AlloyDB data through remote MCP tools directly from your AI coding agent.

Get 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.