Integrate Open WebUI with Live SingleStore Data via CData Connect AI
Open WebUI is an open-source, self-hosted AI chat platform that brings together hosted LLM APIs and locally served models under a single, customizable interface. It supports the Model Context Protocol (MCP) through its tool server framework, allowing you to configure external tools and data sources so that chats can reach beyond the model's training data and interact with live systems.
By integrating Open WebUI with CData Connect AI through the built-in MCP Server, Open WebUI gains governed, real-time access to live SingleStore data. This enables users to list catalogs, explore schemas, and query records from SingleStore data using natural language prompts, with all data access running securely against authorized sources.
This article explains how to configure SingleStore connectivity in Connect AI, generate the required personal access token, install Open WebUI, register the Connect AI MCP Server, configure an LLM provider, and verify the integration by querying live SingleStore data from the Open WebUI chat interface.
Step 1: Configure SingleStore connectivity for Open WebUI
Connectivity to SingleStore from Open WebUI is made possible through Connect AI's Remote MCP Server. To interact with SingleStore data from Open WebUI, start by creating and configuring a SingleStore connection in Connect AI.
- Log into Connect AI, click Sources, and then click Add Connection
- Select SingleStore from the Add Connection panel
-
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.
- Click Save & Test
- 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 Open WebUI. It is best practice to create a separate PAT for each integration to maintain granular access control.
- Click the gear icon () at the top right of the Connect AI app to open Settings
- On the Settings page, go to the Access Tokens section and click Create PAT
- Give the PAT a descriptive name and click Create
- Copy the token when displayed and store it securely. It will not be shown again
With the SingleStore connection configured and a PAT generated, Open WebUI can now connect to SingleStore data through Connect AI.
Step 2: Install Open WebUI and configure Connect AI MCP
Next, install Open WebUI locally and configure the Connect AI Remote MCP Server as a tool server so that the chat interface can discover and call live data tools through Connect AI.
- Install Open WebUI by following the official Quick Start guide
- Once the installation is complete, start Open WebUI and open it in your browser to access the chat interface
-
Click your profile icon in the top right and select Admin Panel
-
In the top navigation bar of the Admin Panel, click Settings
-
Select Integrations from the left menu, then click the icon next to Manage Tool Servers to add a new connection
-
In the Add Connection panel, configure the server with the following values:
- Type: MCP Streamable HTTP
- Name: CData MCP, or any name of your choice
- ID: cdata-mcp
- URL: https://mcp.cloud.cdata.com/mcp
- Auth: None
-
Expand the Advanced section and paste the following JSON into the Headers field:
{ "Authorization": "Basic your_base64_encoded_email_PAT", "Content-Type": "application/json" }Note: Open WebUI will use Basic authentication with Connect AI. Combine your Connect AI user email and the PAT you created earlier in the format email:PAT, base64 encode the combined string, and prefix it with Basic. For example, given [email protected]:ABC123...XYZ789, the Authorization header value becomes something like: Basic dXNlckBkb21haW4uY29tOkFCQzEyMy4uLlhZWjc4OQ==
- Click Save to register the tool server
Enable the MCP server and configure an LLM provider
Open WebUI requires at least one LLM provider to power the chat. Enable the MCP server from the chat input and configure an API key for your preferred provider so the model can interpret prompts and call MCP tools through Connect AI.
-
Return to the chat interface, click the Integrations icon at the bottom of the chat input, select Tools, and toggle CData MCP on to expose the tools to the chat
- At the top of the chat, click the model selector and choose your preferred LLM provider and model. Add your provider API key when prompted so the model can be used in the chat
With the MCP server and an LLM provider configured, Open WebUI is ready to query live SingleStore data through Connect AI.
Step 3: Query live SingleStore data from Open WebUI
With the integration complete, use the Open WebUI chat input to interact with live SingleStore data through natural language prompts handled by the configured LLM.
-
With the CData MCP server enabled and a model selected, type a prompt in the chat input, for example:
- List all catalogs in my cdata mcp
- Show the available schemas and tables for SingleStore
- Query the top 5 records from a table in SingleStore data
-
Open WebUI calls the Connect AI MCP Server and returns live results from SingleStore data
At this point, your Open WebUI instance communicates with the Connect AI MCP Server and retrieves live SingleStore data through remote MCP tools directly from the chat interface.
Get CData Connect AI
To acess hundreds of SaaS, Big Data, and NoSQL sources directly from your cloud applications, try CData Connect AI today! Download a free 14-day trial of CData Connect AI today, and as always, our world-class Support Team is available to assist you with any questions you may have.