![]() |
VOOZH | about |
Cursor is an AI-powered code editor that embeds conversational and agent-style assistance alongside your development workflow. By extending Cursor with MCP (Model Context Protocol) tools, you can give its AI agents secure access to external systems such as APIs and databases.
Integrating Cursor with CData Connect AI via the built-in MCP server allows the editor's AI to query, analyze, and act on live Elasticsearch data without copying data into the IDE. The result is a development experience where you can chat with your governed enterprise data directly from Cursor.
This article outlines how to configure Elasticsearch connectivity in Connect AI, generate the required access token, register Connect AI's MCP Server in Cursor, and then use the AI chat pane to explore live Elasticsearch data.
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 Cursor is made possible through CData Connect AI's Remote MCP Server. To interact with Elasticsearch data from Cursor, 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 Cursor. 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, Cursor can now connect to Elasticsearch data through Connect AI.
Next, configure Cursor to use Connect AI. Cursor reads MCP configuration from an mcp.json file in the user configuration directory and exposes the registered servers under the Tools & MCP settings. Once configured, Cursor's AI chat can call the tools exposed by CData Connect AI.
{
"mcpServers": {
"cdata-mcp": {
"url": "https://mcp.cloud.cdata.com/mcp",
"headers": {
"Authorization": "Basic your_base64_encoded_email_PAT"
}
}
}
}
π Configuring mcp.json with Connect AICursor is now fully integrated with the CData Connect AI MCP Server and can act on live Elasticsearch data directly from the editor.
To access hundreds of SaaS, Big Data, and NoSQL sources directly from your development tools, try CData Connect AI today!
Learn more about CData Connect AI or sign up for free trial access:
Free Trial