Integrate Cursor with Live HCL Domino 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 HCL Domino 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 HCL Domino 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 HCL Domino data.

Step 1: Configure HCL Domino connectivity for Cursor

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

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

2. Select HCL Domino from the Add Connection panel

3. Enter the necessary authentication properties to connect to HCL Domino.

   Connecting to Domino

   To connect to Domino data, set the following properties:

   • URL: The host name or IP of the server hosting the Domino database. Include the port of the server hosting the Domino database. For example: http://sampleserver:1234/
   • DatabaseScope: The name of a scope in the Domino Web UI. The driver exposes forms and views for the schema governed by the specified scope. In the Domino Admin UI, select the Scopes menu in the sidebar. Set this property to the name of an existing scope.

   Authenticating with Domino

   Domino supports authenticating via login credentials or an Entra ID (formerly Azure AD) OAuth application:

   Login Credentials

   To authenticate with login credentials, set the following properties:

   • AuthScheme: Set this to "OAuthPassword"
   • User: The username of the authenticating Domino user
   • Password: The password associated with the authenticating Domino user

   The driver uses the login credentials to automatically perform an OAuth token exchange.

   EntraID (formerly AzureAD)

   This authentication method uses Entra ID (formerly Azure AD) as an IdP to obtain a JWT token. You need to create a custom OAuth application in Entra ID (formerly Azure AD) and configure it as an IdP. To do so, follow the instructions in the Help documentation. Then set the following properties:

   • AuthScheme: Set this to "EntraID (formerly AzureAD)"
   • InitiateOAuth: Set this to GETANDREFRESH. You can use InitiateOAuth to avoid repeating the OAuth exchange and manually setting the OAuthAccessToken.
   • OAuthClientId: The Client ID obtained when setting up the custom OAuth application.
   • OAuthClientSecret: The Client secret obtained when setting up the custom OAuth application.
   • CallbackURL: The redirect URI defined when you registered your app. For example: https://localhost:33333
   • AzureTenant: The Microsoft Online tenant being used to access data. Supply either a value in the form companyname.microsoft.com or the tenant ID.

     The tenant ID is the same as the directory ID shown in the Azure Portal's Entra ID (formerly Azure AD) > Properties page.

   
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 HCL Domino connection configured and a PAT generated, Cursor can now connect to HCL Domino 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 HCL Domino data and list the high priority accounts"

Cursor is now fully integrated with the CData Connect AI MCP Server and can act on live HCL Domino 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!