Integrating Gumloop with Azure Data Lake Storage Data via CData Connect AI

Gumloop is a visual automation platform designed to create AI-powered workflows by combining triggers, AI nodes, APIs, and data connectors. By integrating Gumloop with CData Connect AI through the built-in MCP (Model Context Protocol) Server, workflows can seamlessly access and interact with live Azure Data Lake Storage data.

The platform provides a low-code environment, making it easier to orchestrate complex processes without heavy development effort. Its flexibility allows integration across multiple business applications, enabling end-to-end automation with live data.

This article outlines the steps required to configure Azure Data Lake Storage connectivity in Connect AI, register the MCP server in Gumloop, and build a workflow that queries Azure Data Lake Storage data.

Step 1: Configure Azure Data Lake Storage Connectivity for Gumloop

Connectivity to Azure Data Lake Storage from Gumloop is made possible through CData Connect AI's Remote MCP Server. To interact with Azure Data Lake Storage data from Gumloop, we start by creating and configuring a Azure Data Lake Storage connection in CData Connect AI.

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

2. Select "Azure Data Lake Storage" from the Add Connection panel

3. Enter the necessary authentication properties to connect to Azure Data Lake Storage.

   Authenticating to a Gen 1 DataLakeStore Account

   Gen 1 uses OAuth 2.0 in Entra ID (formerly Azure AD) for authentication.

   For this, an Active Directory web application is required. You can create one as follows:

   1. Sign in to your Azure Account through the .
   2. Select "Entra ID" (formerly Azure AD).
   3. Select "App registrations".
   4. Select "New application registration".
   5. Provide a name and URL for the application. Select Web app for the type of application you want to create.
   6. Select "Required permissions" and change the required permissions for this app. At a minimum, "Azure Data Lake" and "Windows Azure Service Management API" are required.
   7. Select "Key" and generate a new key. Add a description, a duration, and take note of the generated key. You won't be able to see it again.

   To authenticate against a Gen 1 DataLakeStore account, the following properties are required:

   • Schema: Set this to ADLSGen1.
   • Account: Set this to the name of the account.
   • OAuthClientId: Set this to the application Id of the app you created.
   • OAuthClientSecret: Set this to the key generated for the app you created.
   • TenantId: Set this to the tenant Id. See the property for more information on how to acquire this.
   • Directory: Set this to the path which will be used to store the replicated file. If not specified, the root directory will be used.

   Authenticating to a Gen 2 DataLakeStore Account

   To authenticate against a Gen 2 DataLakeStore account, the following properties are required:

   • Schema: Set this to ADLSGen2.
   • Account: Set this to the name of the account.
   • FileSystem: Set this to the file system which will be used for this account.
   • AccessKey: Set this to the access key which will be used to authenticate the calls to the API. See the property for more information on how to acquire this.
   • Directory: Set this to the path which will be used to store the replicated file. If not specified, the root directory will be used.
   
4. Click Save & Test
5. Navigate to the Permissions tab in the Add Azure Data Lake Storage Connection page and update the User-based permissions.

Add a Personal Access Token

A Personal Access Token (PAT) is used to authenticate the connection to Connect AI from Gumloop. It is best practice to create a separate PAT for each service to maintain granularity of access.

1. Click on the Gear icon () at the top right of the Connect AI app to open the settings page.
2. On the Settings page, go to the Access Tokens section and click Create PAT.
3. Give the PAT a 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 Azure Data Lake Storage connection configured and a PAT generated, Gumloop is prepared to connect to Azure Data Lake Storage data through the CData MCP server.

Step 2: Connect to the MCP server in Gumloop

The MCP server endpoint and authentication values from Connect AI must be added to Gumloop credentials.

1. Sign in to Gumloop and create an account
2. Visit the Gumloop Credentials page to configure MCP server
3. Click on Add Credentials and search and select MCP Server

4. Provide the following details:
   • URL: https://mcp.cloud.cdata.com/mcp
   • Label: A descriptive name such as Azure Data Lake Storage-mcp-server
   • Access Token / API Key: leave blank
   • Additional Header: Authorization: Basic YOUR EMAIL:YOUR PAT
   
   • Save the credentials
   

The MCP server is now available to build workflows in Gumloop.

Step 3: Build a workflow and explore live Azure Data Lake Storage data with Gumloop

1. Visit Gumloop Personal workspace and click on the Create Flow

2. Select the icon or press Ctrl + B to add a node or a subflow

3. Search for Ask AI and select it

4. Click Show More Options and enable the Connect MCP Server? option

5. From the MCP Servers dropdown, choose the saved MCP credential
6. Add a Prompt and Choose an AI Model according to your requirements

7. After configuring the required details, Click Run to run the pipeline

With the workflow run completed, Gumloop demonstrates successful retrieval of Azure Data Lake Storage data through the CData Connect AI MCP server, with the MCP Client node providing the ability to ask questions, retrieve records, and perform actions on the data.

Get CData Connect AI

To get live data access to 300+ SaaS, Big Data, and NoSQL sources directly from your cloud applications, try CData Connect AI today!