Integrate Theia IDE with Live SingleStore Data via CData Connect AI

Theia IDE is an open-source, cloud and desktop IDE platform that provides a flexible, extensible development environment with built-in AI capabilities. Its AI features support multiple LLM providers and MCP (Model Context Protocol) tool integrations, allowing developers to interact with live external data sources directly from chat-based agents inside the IDE.

By integrating Theia IDE with CData Connect AI through the built-in MCP server, Theia's AI agents gain governed, real-time access to live SingleStore data. This enables developers to list catalogs, explore schemas, and query records from SingleStore data without leaving the editor or writing custom integration code.

This article explains how to configure SingleStore connectivity in Connect AI, generate the required personal access token, register the CData Connect AI MCP Server in Theia IDE, enable AI features with an LLM provider, and verify the integration by querying live SingleStore data from the Theia AI Chat.

Step 1: Configure SingleStore connectivity for Theia IDE

Connectivity to SingleStore from Theia IDE is made possible through Connect AI's Remote MCP Server. To interact with SingleStore data from Theia IDE, start by creating and configuring a SingleStore connection in 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 Theia IDE. 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. Copy the token when displayed and store it securely. It will not be shown again

With the SingleStore connection configured and a PAT generated, Theia IDE can now connect to SingleStore data through Connect AI.

Step 2: Configure Connect AI MCP in Theia IDE

Next, register the CData Connect AI Remote MCP Server in Theia IDE so that the built-in AI agents can discover and call live data tools through Connect AI.

1. Download and install the Theia IDE
2. Open Theia IDE and navigate to Settings (or press Ctrl + ,) to open the Settings view
3. In the Settings panel, expand AI Features and select MCP
4. Click Edit in settings.json to open the configuration file and paste the following JSON:

   {
       "ai-features.mcp.mcpServers": {
           "cdata": {
               "serverUrl": "https://mcp.cloud.cdata.com/mcp",
               "serverAuthToken": "Basic your_base64_encoded_email_PAT",
               "serverAuthTokenHeader": "Authorization"
           }
       }
   }

   Note: Theia IDE 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 serverAuthToken value becomes something like: Basic dXNlckBkb21haW4uY29tOkFCQzEyMy4uLlhZWjc4OQ==

   
5. Save the settings.json file

Enable AI and configure an LLM provider

Theia IDE requires AI features to be enabled and at least one LLM provider configured to power the agent's reasoning.

1. Return to Settings and under AI Features, select AI Enablement
2. Check the Enable AI box to activate Theia's AI capabilities
3. Under AI Features, choose your preferred LLM provider (e.g., Anthropic, OpenAI, Google, Hugging Face) and enter your API key

With the MCP server registered and an LLM provider configured, Theia's AI agents are ready to query live SingleStore data through Connect AI.

Step 3: Query live SingleStore data from the Theia AI Chat

With the integration complete, use the Theia AI Chat panel to interact with live SingleStore data.

1. Open the AI Chat panel from the right sidebar of the Theia IDE
2. At the bottom of the chat, click the Toggle Capabilities Configuration icon (or press Ctrl + Shift + .) to open the capabilities panel
3. Under Generic Capabilities, expand MCP and check the cdata server (and any specific tools you want to expose) to make the Connect AI tools available to the agent
4. Type @AppTester in the chat input followed by your prompt, 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
5. The agent calls the Connect AI MCP Server and returns live results from SingleStore data

At this point, your Theia IDE communicates with the Connect AI MCP Server and retrieves live SingleStore data through remote MCP directly from the editor.

Get CData Connect AI

To access hundreds of SaaS, Big Data, and NoSQL sources directly from your cloud applications, try CData Connect AI today! Start 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.