VOOZH about

URL: https://www.cdata.com/kb/tech/domino-cloud-emergent.rst

⇱ Access Live HCL Domino Data in Emergent via CData Connect AI

Access Live HCL Domino Data in Emergent via CData Connect AI

👁 Yazhini G
Yazhini G
Technical Marketing Engineer
Leverage the CData Connect AI Remote MCP Server to enable Emergent agents to securely access and build applications with live HCL Domino data through MCP integration.

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 HCL Domino data. This enables agents to query, analyze, and visualize HCL Domino 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 HCL Domino connectivity in Connect AI, register the CData MCP Server in Emergent, and interact with live HCL Domino data from Emergent.

Step 1: Configure HCL Domino connectivity for Emergent

Connectivity to HCL Domino from Emergent is made possible through CData Connect AI's Remote MCP Server. To interact with HCL Domino data from Emergent, 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. 👁 Adding a connection in Connect AI
  2. Select HCL Domino from the Add Connection panel
    3. 👁 Selecting data source
  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.

    👁 Configuring a connection (Salesforce is shown)
  4. Click Save & Test
  5. Navigate to the Permissions tab and update user-based permissions
    6. 👁 Updating permissions

Add a Personal Access Token

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.

  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. 👁 Creating a new PAT
  4. Copy the token when displayed and store it securely. It will not be shown again

With the HCL Domino connection configured and a PAT generated, Emergent can now connect to HCL Domino data through Connect AI.

Step 2: Configure Connect AI in Emergent

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.

Method 1: Direct MCP Configuration (Pro/Enterprise)

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 HCL Domino data through MCP tools without additional setup.

  1. Sign in to Emergent and create an account if you do not already have one
  2. Click to start a new project. Enter a Project Name and click Create Project 👁 Creating a new project in Emergent
  3. In the project chat window, select your preferred model from the dropdown (e.g., Claude 4.5 Sonnet)
  4. Click the Advanced Controls icon and then click Select MCP Tools to open the MCP configuration panel 👁 Opening Advanced Controls in Emergent
  5. In the Select MCPs to use dialog, click + New MCP Server to add a custom MCP server 👁 Adding a new MCP server in Emergent
  6. In the Configure New MCP dialog, fill in the following:
    • MCP Name: cdata-mcp
    • Description: (optional) A brief description of the server
    • JSON Configuration: Paste the following, replacing base64-encode-email-pat with your Base64-encoded email:PAT string:
    {
 "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 Emergent
  7. Click Verify and Save to register the MCP server
  8. Return to Select MCP Tools and confirm that cdata-mcp is listed and its toggle is enabled. If it is not enabled, toggle it on

With the CData MCP Server registered and enabled, Emergent agents can now query and act on live HCL Domino data through Connect AI in any project.

Query live HCL Domino data from Emergent

With the MCP server configured, start a conversation in the Emergent agent panel to interact with live HCL Domino data.

  1. Return to the project chat and enter a prompt to explore your data, for example:
    • List all available catalogs in my cdata-mcp connection.
    • Show the schemas and tables available for HCL Domino.
    • Query the top 5 records from HCL Domino data.
  2. The agent calls the CData Connect AI MCP Server and returns live results from HCL Domino data

Method 2: Build an application with natural language (Free)

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 HCL Domino data.

  1. Sign in to Emergent and open the chat window
  2. Enter a prompt that describes the application you want to build. For example: 
    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.
  3. Emergent will prompt you to provide the MCP endpoint URL and authentication credentials. Supply the following values:
    • MCP Endpoint URL: https://mcp.cloud.cdata.com/mcp
    • Authorization: Basic base64(email:PAT)
  4. The Emergent agent generates a full-stack application that connects to HCL Domino data through Connect AI and renders live results in the App Preview panel. 👁 Emergent agent returning live data from CData Connect AI

At this point, Emergent has built an application that communicates with the CData Connect AI MCP Server and retrieves live HCL Domino data, all from a single natural language prompt.

Get CData Connect AI

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.