![]() |
VOOZH | about |
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 Elasticsearch data. This enables agents to query, analyze, and visualize Elasticsearch 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 Elasticsearch connectivity in Connect AI, register the CData MCP Server in Emergent, and interact with live Elasticsearch data from Emergent.
Accessing and integrating live data from Elasticsearch has never been easier with CData. Customers rely on CData connectivity to:
Users frequently integrate Elasticsearch data with analytics tools such as Crystal Reports, Power BI, and Excel, and leverage our tools to enable a single, federated access layer to all of their data sources, including Elasticsearch.
For more information on CData's Elasticsearch solutions, check out our Knowledge Base article: CData Elasticsearch Driver Features & Differentiators.
Connectivity to Elasticsearch from Emergent is made possible through CData Connect AI's Remote MCP Server. To interact with Elasticsearch data from Emergent, start by creating and configuring a Elasticsearch connection in CData Connect AI.
Set the Server and Port connection properties to connect. To authenticate, set the User and Password properties, PKI (public key infrastructure) properties, or both. To use PKI, set the SSLClientCert, SSLClientCertType, SSLClientCertSubject, and SSLClientCertPassword properties.
The data provider uses X-Pack Security for TLS/SSL and authentication. To connect over TLS/SSL, prefix the Server value with 'https://'. Note: TLS/SSL and client authentication must be enabled on X-Pack to use PKI.
Once the data provider is connected, X-Pack will then perform user authentication and grant role permissions based on the realms you have configured.
π Configuring a connection (Salesforce is shown)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.
With the Elasticsearch connection configured and a PAT generated, Emergent can now connect to Elasticsearch data through Connect AI.
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.
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 Elasticsearch data through MCP tools without additional setup.
{
"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 EmergentWith the CData MCP Server registered and enabled, Emergent agents can now query and act on live Elasticsearch data through Connect AI in any project.
With the MCP server configured, start a conversation in the Emergent agent panel to interact with live Elasticsearch data.
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 Elasticsearch data.
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.
At this point, Emergent has built an application that communicates with the CData Connect AI MCP Server and retrieves live Elasticsearch data, all from a single natural language prompt.
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.
Learn more about CData Connect AI or sign up for free trial access:
Free Trial