![]() |
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 Databricks data. This enables agents to query, analyze, and visualize Databricks 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 Databricks connectivity in Connect AI, register the CData MCP Server in Emergent, and interact with live Databricks data from Emergent.
Accessing and integrating live data from Databricks has never been easier with CData. Customers rely on CData connectivity to:
While many customers are using CData's solutions to migrate data from different systems into their Databricks data lakehouse, several customers use our live connectivity solutions to federate connectivity between their databases and Databricks. These customers are using SQL Server Linked Servers or Polybase to get live access to Databricks from within their existing RDBMs.
Read more about common Databricks use-cases and how CData's solutions help solve data problems in our blog: What is Databricks Used For? 6 Use Cases.
Connectivity to Databricks from Emergent is made possible through CData Connect AI's Remote MCP Server. To interact with Databricks data from Emergent, start by creating and configuring a Databricks connection in CData Connect AI.
To connect to a Databricks cluster, set the properties as described below.
Note: The needed values can be found in your Databricks instance by navigating to Clusters, and selecting the desired cluster, and selecting the JDBC/ODBC tab under Advanced Options.
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 Databricks connection configured and a PAT generated, Emergent can now connect to Databricks 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 Databricks 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 Databricks data through Connect AI in any project.
With the MCP server configured, start a conversation in the Emergent agent panel to interact with live Databricks 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 Databricks 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 Databricks 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