Integrate Dify with Live AlloyDB Data via CData Connect AI

Anusha M B
Anusha M B
Technical Marketing Engineer
Use the CData Connect AI Remote MCP Server to enable Dify agents and workflows to securely access and query live AlloyDB data.

Dify is an open source platform for building production-ready agentic workflows, chatbots, and other LLM applications. It includes built-in, two-way support for the model context protocol (MCP), allowing you to register remote MCP servers as tools in the platform to add external data sources and give your agents access to live data.

By integrating Dify with CData Connect AI through the built-in MCP Server, Dify 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, register the Connect AI MCP Server as a tool in Dify, add it to an agent application, and verify the integration by querying live AlloyDB data from Dify.

Step 1: Configure AlloyDB connectivity for Dify

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

  1. Log into Connect AI, click Sources, and then click Add Connection
  2. Adding a connection in Connect AI
  3. Select AlloyDB from the Add Connection panel
  4. Selecting data source
  5. 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)

  6. Click Save & Test
  7. Navigate to the Permissions tab and update user-based permissions
  8. Updating permissions

Add a Personal Access Token

A Personal Access Token (PAT) is used to authenticate the connection to Connect AI from Dify. 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. Creating a new PAT
  5. Copy the token when displayed and store it securely. It will not be shown again

With the AlloyDB connection configured and a PAT generated, Dify can now connect to AlloyDB data through Connect AI.

Step 2: Register the Connect AI MCP Server in Dify

Next, register the Connect AI Remote MCP Server as a tool in Dify so your agents and workflows can discover and call live data tools through Connect AI.

  1. Log into Dify, or open your self-hosted Dify instance (version 1.6.0 or later, which includes built-in MCP support)
  2. Navigate to the Integrations page, select Tools and click MCP tab
  3. Navigate to MCP
  4. Click Add MCP Server (HTTP) and enter the following details:
    • Server URL: https://mcp.cloud.cdata.com/mcp
    • Name Icon: Give a descriptive name, for example, CData Connect AI
    • Server Identifier: A unique identifier, for example, cdata-connect-ai
    • Headers: Add an Authorization header with the value Basic your_base64_encoded_email_PAT

    Note: Dify 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.

  5. Click Add & Authorize. Dify connects to the Connect AI MCP Server and lists the available tools Adding the Connect AI MCP Server in Dify

With the MCP server registered, the Connect AI tools are available to any agent application or workflow in your Dify workspace.

Step 3: Query live AlloyDB data from Dify

With the integration complete, build an agent application in Dify and interact with live AlloyDB data through natural language prompts.

  1. From the Dify Studio page, click Create from Blank and select Agent as the application type Viewing the Connect AI MCP tools in Dify
  2. In the agent configuration, click Add under the Tools section and select the Connect AI MCP tools registered in Step 2 Adding the Connect AI MCP tools to a Dify agent
  3. Select an LLM provider and model for the agent so it can interpret prompts and call MCP tools
  4. In the preview panel, 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
  5. The Dify agent calls the Connect AI MCP Server and returns live results from AlloyDB data Querying live data from a Dify agent

At this point, Dify communicates with the Connect AI MCP Server and retrieves live AlloyDB data through remote MCP tools directly from your agentic workflows.

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.

Ready to get started?

Learn more about CData Connect AI or sign up for free trial access:

Free Trial