Integrate Cursor with Live SingleStore Data via CData Connect AI

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 CData MCP Server allows the editor's AI to query, analyze, and act on live SingleStore 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 SingleStore connectivity in Connect AI, generate the required access token, register the CData MCP Server in Cursor, and then use the AI chat pane to explore live SingleStore data.

Step 1: Configure SingleStore connectivity for Cursor

Connectivity to SingleStore from Cursor is made possible through CData Connect AI's Remote MCP Server. To interact with SingleStore data from Cursor, start by creating and configuring a SingleStore connection in CData Connect AI.

1. Log into Connect AI, click Sources, and then click Add Connection

2. Select SingleStore from the Add Connection panel

3. Enter the necessary authentication properties to connect to SingleStore.

   The following connection properties are required in order to connect to data.

   • Server: The host name or IP of the server hosting the SingleStore database.
   • Port: The port of the server hosting the SingleStore database.
   • Database (Optional): The default database to connect to when connecting to the SingleStore Server. If this is not set, tables from all databases will be returned.

   Connect Using Standard Authentication

   To authenticate using standard authentication, set the following:

   • User: The user which will be used to authenticate with the SingleStore server.
   • Password: The password which will be used to authenticate with the SingleStore server.

   Connect Using Integrated Security

   As an alternative to providing the standard username and password, you can set IntegratedSecurity to True to authenticate trusted users to the server via Windows Authentication.

   Connect Using SSL Authentication

   You can leverage SSL authentication to connect to SingleStore data via a secure session. Configure the following connection properties to connect to data:

   • SSLClientCert: Set this to the name of the certificate store for the client certificate. Used in the case of 2-way SSL, where truststore and keystore are kept on both the client and server machines.
   • SSLClientCertPassword: If a client certificate store is password-protected, set this value to the store's password.
   • SSLClientCertSubject: The subject of the TLS/SSL client certificate. Used to locate the certificate in the store.
   • SSLClientCertType: The certificate type of the client store.
   • SSLServerCert: The certificate to be accepted from the server.

   Connect Using SSH Authentication

   Using SSH, you can securely login to a remote machine. To access SingleStore data via SSH, configure the following connection properties:

   • SSHClientCert: Set this to the name of the certificate store for the client certificate.
   • SSHClientCertPassword: If a client certificate store is password-protected, set this value to the store's password.
   • SSHClientCertSubject: The subject of the TLS/SSL client certificate. Used to locate the certificate in the store.
   • SSHClientCertType: The certificate type of the client store.
   • SSHPassword: The password that you use to authenticate with the SSH server.
   • SSHPort: The port used for SSH operations.
   • SSHServer: The SSH authentication server you are trying to authenticate against.
   • SSHServerFingerPrint: The SSH Server fingerprint used for verification of the host you are connecting to.
   • SSHUser: Set this to the username that you use to authenticate with the SSH server.
   
4. Click Save & Test
5. Navigate to the Permissions tab and update user-based permissions

Add a Personal Access Token

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.

1. Click the gear icon () at the top right of the Connect AI app to open Settings
2. On the Settings page, go to the Access Tokens section and click Create PAT
3. Give the PAT a descriptive name and click Create

4. The personal access token is only visible at creation, so be sure to copy it and store it securely for future use

With the SingleStore connection configured and a PAT generated, Cursor can now connect to SingleStore data through the CData MCP Server.

Step 2: Configure the CData MCP Server in Cursor

Next, configure Cursor to use the CData MCP Server. 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.

1. Download the Cursor desktop application and complete the sign-up flow for your account
2. From the top menu, click Settings to open the settings panel
3. In the left navigation, open the Tools & MCP tab and click Add Custom MCP
4. Cursor opens an mcp.json file in the editor
5. Add the following configuration. Make sure to base64-encode your email:PAT before inserting into the header:

   {
     "mcpServers": {
       "cdata-mcp": {
         "url": "https://mcp.cloud.cdata.com/mcp",
         "headers": {
           "Authorization": "Basic your_base64_encoded_email_PAT"
         }
       }
     }
   }
   		

   
6. Save the file
7. Return to Settings and then select Tools & MCP. You can now see cdata-mcp enabled with an active indicator

Step 3: Chat with CData Connect AI from Cursor

1. From the top bar, click Toggle AI Pane to open the chat window
2. Test the connection by entering "List connections"
3. You can also run queries like "Query SingleStore data and list the high priority accounts"

Cursor is now fully integrated with the CData Connect AI MCP Server and can act on live SingleStore data directly from the editor.

Get CData Connect AI

To access 300+ SaaS, Big Data, and NoSQL sources directly from your development tools, try CData Connect AI today!