![]() |
VOOZH | about |
ElevenLabs is a leading AI audio platform that enables developers to build conversational voice agents capable of natural, human-like interactions. The ElevenLabs Conversational AI platform allows you to create voice-powered assistants that can reason through tasks, respond dynamically, and interact with external systems in real time.
By integrating ElevenLabs with CData Connect AI through the MCP (Model Context Protocol), your voice agents gain the ability to query, analyze, and act on live AlloyDB data during conversations. This integration bridges ElevenLabs' conversational AI framework with the governed enterprise connectivity of CData Connect AI, ensuring all data access runs securely against authorized sources without manual data movement.
This article outlines the steps to configure AlloyDB connectivity in Connect AI, generate the required authentication credentials, register the Connect AI MCP Server in ElevenLabs, and verify that your voice agent can successfully interact with live AlloyDB data during conversations.
Connectivity to AlloyDB from ElevenLabs is made possible through CData Connect AI's Remote MCP Server. To interact with AlloyDB data from your voice agents, 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)
A Personal Access Token (PAT) is used to authenticate the connection to Connect AI from ElevenLabs. 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, ElevenLabs can now connect to AlloyDB data through Connect AI.
ElevenLabs supports connecting to external MCP servers that use SSE (Server-Sent Events) or HTTP streamable transport. The CData Connect AI Remote MCP Server is compatible with this integration.
With the MCP server registered, you can now add it to your ElevenLabs voice agents to enable real-time data access during conversations.
Your ElevenLabs voice agent can now access and query live AlloyDB data through the CData Connect AI MCP Server during conversations.
Your ElevenLabs voice agent is now fully configured to access and query live AlloyDB data through the CData Connect AI Remote MCP Server, enabling real-time, data-driven voice interactions for your users.
To access hundreds of SaaS, Big Data, and NoSQL sources through secure, AI-ready interfaces, try CData Connect AI today.
Learn more about CData Connect AI or sign up for free trial access:
Free Trial