![]() |
VOOZH | about |
Flowise AI is an open-source, no-code tool for building AI workflows and custom agents visually. Its drag-and-drop interface allows you to integrate large language models (LLMs) with APIs, databases, and external systems effortlessly.
CData Connect AI enables real-time connectivity to hundreds of enterprise data sources. Through its Model Context Protocol (MCP) server, CData Connect AI bridges Flowise agents with live AlloyDB securely and efficiently, no data replication required. By combining Flowise AI's intuitive agent builder with CData's MCP integration, users can create agents capable of fetching, analyzing, and acting upon live AlloyDB data directly within Flowise AI workflows.
This guide shows you how to connect Flowise AI to CData Connect AI MCP, set up credentials, and enable your agents to query live AlloyDB data in real time.
Connectivity to AlloyDB from Flowise AI is made possible through CData Connect AI's Remote MCP Server. To interact with AlloyDB data from Flowise AI, we start by creating and configuring a AlloyDB connection in CData Connect AI.
The following connection properties are usually required in order to connect to AlloyDB.
You can also optionally set the following:
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.
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.
This authentication method must be enabled by setting the auth-method in the pg_hba.conf file to md5.
This authentication method must be enabled by setting the auth-method in the pg_hba.conf file to scram-sha-256.
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)
Once the connection is established, AlloyDB data is now accessible in CData Connect AI and ready to be used with MCP enabled tools.
A Personal Access Token (PAT) is used to authenticate the connection to Connect AI from Flowise AI. It is best practice to create a separate PAT for each integration to maintain granular access control.
With the AlloyDB connection configured and a PAT generated, Flowise AI can now connect to AlloyDB data through Connect AI.
Log in to Flowise AI workspace to set up the integration.
Double-click on the Agent node and fill in the details:
{
"url": "https://mcp.cloud.cdata.com/mcp",
"headers": {
"Authorization": "Basic {{$vars.PAT}}"
}
}
π Configuring custom MCP tool in FlowiseClick the refresh icon to load available MCP actions. Once actions are listed, now Flowise agent is successfully connected to CData Connect AI MCP.
With the workflow run completed, Flowise demonstrates successful retrieval of Salesforce data through the CData Connect AI MCP server, with the MCP Client node providing the ability to ask questions, retrieve records, and perform actions on the data.
To access hundreds of SaaS, Big Data, and NoSQL sources directly from your cloud applications, try CData Connect AI today!
Learn more about CData Connect AI or sign up for free trial access:
Free Trial