Build Agents in Relevance AI with Access to Live AlloyDB Data via CData Connect AI

Relevance AI is an AI automation and agent-building platform that enables organizations to create autonomous workflows powered by natural language reasoning. Users can visually design agents that interact with APIs, databases, and third-party systems to complete everyday business tasks or data operations.

By integrating Relevance AI with CData Connect AI through the built-in MCP (Model Context Protocol) Server, your agents can query, summarize, and act on live AlloyDB data in real time. This connection bridges Relevance AI intelligent workflow engine with the governed enterprise connectivity of CData Connect AI ensuring every query runs securely against authorized sources without manual data export.

This article outlines the steps to configure AlloyDB connectivity in Connect AI, register Connect AI in Relevance AI, and build an agent that interacts with live AlloyDB data.

Step 1: Configure AlloyDB Connectivity for Relevance AI

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

Step 2: Configure Connectivity in Relevance AI

The CData Connect AI MCP endpoint and authorization details are registered within Relevance AI so that agents can call live data from Connect AI.

1. Sign in to Relevance AI and create an account if you do not already have one
2. From the sidebar, navigate to Agents and then click on New Agent
👁 Creating a new agent in Relevance AI

3. Select Build from scratch and name the agent (eg; CData MCP Server)
👁 Building an agent from scratch

4. Inside the agent editor, select Advanced and then switch to the MCP Server tab
👁 Opening MCP Server settings

5. Click + Add Remote MCP Tools
6. In the dialog that appears, fill out the fields as follows:
• URL: https://mcp.cloud.cdata.com/mcp
• Label: Any custom label (eg; cdata_mcp_server)
• Authentication: Select Custom headers
• Add header key:value pair. Combine your email and PAT as email:PAT and encode that string in Base64 and then prefix with the word Basic
  • Key: Authorization
  • Value: Basic base64(email:PAT)
👁 Connecting to CData Connect AI MCP Server in Relevance AI

Click Connect to establish the connection. Relevance AI will verify your credentials and register the CData Connect AI MCP Server for use in agents.

Step 3: Build and Run a Relevance AI Agent with Live AlloyDB Data

1. Switch to the Run tab for your agent
2. Enter a task for example, "List the five most recent incidents from ServiceNow"
👁 Running the Relevance AI agent

3. The agent will query Connect AI via the MCP endpoint and display live results from AlloyDB data
👁 Example query result from Connect AI

With the connection complete, Relevance AI agents can now issue queries, retrieve records, and perform AI-driven tasks over live AlloyDB data through CData Connect AI MCP Server.

Get CData Connect AI

To access hundreds of SaaS, Big Data, and NoSQL sources directly from your cloud applications, try CData Connect AI today!