Access Live AlloyDB Data in Emergent via CData Connect AI

Emergent is an AI-powered development platform that lets users describe what they want to build and have an autonomous agent generate full-stack web applications in real time. Agents can connect to external tools and data sources through MCP to retrieve live data and power their outputs.

By integrating Emergent with CData Connect AI through the built-in MCP (Model Context Protocol) Server, Emergent agents gain governed, real-time access to live AlloyDB data. This enables agents to query, analyze, and visualize AlloyDB data: either by calling MCP tools directly during a session, or by generating a full application wired to live data, all without manual data exports or custom integration code.

This article outlines the steps to configure AlloyDB connectivity in Connect AI, register the CData MCP Server in Emergent, and interact with live AlloyDB data from Emergent.

Step 1: Configure AlloyDB connectivity for Emergent

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

Step 2: Configure Connect AI in Emergent

CData Connect AI can be integrated with Emergent in two ways depending on your account tier. Pro and Enterprise users can register the MCP Server directly in the Emergent UI, while free-tier users can describe the integration in natural language and have Emergent's agent build a connected application automatically.

Method 1: Direct MCP Configuration (Pro/Enterprise)

Pro and Enterprise users can register the CData Connect AI MCP Server directly in the Emergent UI. Once registered, agents in any project can call live AlloyDB data through MCP tools without additional setup.

1. Sign in to Emergent and create an account if you do not already have one
2. Click to start a new project. Enter a Project Name and click Create Project 👁 Creating a new project in Emergent
   
3. In the project chat window, select your preferred model from the dropdown (e.g., Claude 4.5 Sonnet)
4. Click the Advanced Controls icon and then click Select MCP Tools to open the MCP configuration panel 👁 Opening Advanced Controls in Emergent
   
5. In the Select MCPs to use dialog, click + New MCP Server to add a custom MCP server 👁 Adding a new MCP server in Emergent
   
6. In the Configure New MCP dialog, fill in the following:
   • MCP Name: cdata-mcp
   • Description: (optional) A brief description of the server
   • JSON Configuration: Paste the following, replacing base64-encode-email-pat with your Base64-encoded email:PAT string:

   {
    "mcpServers": {
    "cdata-mcp": {
    "args": [
    "-y",
    "mcp-client",
    "connect",
    "https://mcp.cloud.cdata.com/mcp"
    ],
    "command": "npx",
    "env": {
    "MCP_HEADERS": "{\"Authorization\":\"Basic base64-encode-email-pat\"}"
    }
    }
    }
   }
    

   Note: Combine your Connect AI email and PAT in the format email:PAT, then Base64 encode the combined string. For example, given [email protected]:ABC123...XYZ, the value becomes something like: dXNlckBteWRvbWFpbjphSzkvbVB4Mi9Rcjd2TjQ...

   👁 Configuring the CData MCP Server in Emergent
   
7. Click Verify and Save to register the MCP server
8. Return to Select MCP Tools and confirm that cdata-mcp is listed and its toggle is enabled. If it is not enabled, toggle it on

With the CData MCP Server registered and enabled, Emergent agents can now query and act on live AlloyDB data through Connect AI in any project.

Query live AlloyDB data from Emergent

With the MCP server configured, start a conversation in the Emergent agent panel to interact with live AlloyDB data.

1. Return to the project chat and enter a prompt to explore your data, for example:
   • List all available catalogs in my cdata-mcp connection.
   • Show the schemas and tables available for AlloyDB.
   • Query the top 5 records from AlloyDB data.
2. The agent calls the CData Connect AI MCP Server and returns live results from AlloyDB data

Method 2: Build an application with natural language (Free)

Free-tier users can direct Emergent to build a full-stack application that connects to the CData Connect AI MCP Server through a natural language prompt. The agent will gather the required endpoint and credentials interactively, then generate a working application wired to live AlloyDB data.

1. Sign in to Emergent and open the chat window
2. Enter a prompt that describes the application you want to build. For example:

   I would like to build a small application that connects to a remote MCP HTTPS server.
   I already have the MCP endpoint URL and the required credentials.
   The application should:
    - Establish a connection to the remote MCP server
    - Authenticate using the provided credentials
    - Retrieve and list all available catalogs from the MCP
   
   Please make sure the credentials are stored securely in a .env file
   and not hardcoded in the application.
    

3. Emergent will prompt you to provide the MCP endpoint URL and authentication credentials. Supply the following values:
   • MCP Endpoint URL: https://mcp.cloud.cdata.com/mcp
   • Authorization: Basic base64(email:PAT)
4. The Emergent agent generates a full-stack application that connects to AlloyDB data through Connect AI and renders live results in the App Preview panel. 👁 Emergent agent returning live data from CData Connect AI
   

At this point, Emergent has built an application that communicates with the CData Connect AI MCP Server and retrieves live AlloyDB data, all from a single natural language prompt.

Get CData Connect AI

To access hundreds of SaaS, Big Data, and NoSQL sources directly from your cloud applications, try CData Connect AI today! Sign up for a free 14-day trial of CData Connect AI, and as always, our world-class Support Team is available to assist you with any questions you may have.