Interact with Live SingleStore Data in Warp via CData Connect AI

Warp is an agentic development environment that combines a modern terminal with an AI agent. It supports large language model (LLM) interactions and Model Context Protocol (MCP) server integrations, so the agent can reach live external data sources without leaving the terminal.

By integrating Warp with CData Connect AI through its built-in MCP Server, the Warp Agent gets governed, real-time access to live SingleStore data. You can explore SingleStore data, ask questions in plain language, and work with your records without writing custom integration code.

This article walks through configuring SingleStore connectivity in Connect AI, configuring the CData MCP Server in Warp, and interacting with live SingleStore data from the Warp Agent.

Step 1: Configure SingleStore connectivity for Warp

Connectivity to SingleStore from Warp is made possible through Connect AI's Remote MCP Server. To interact with SingleStore data from Warp, 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 Warp. 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 Personal 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, Warp can now connect to SingleStore data through Connect AI.

Step 2: Configure Connect AI in Warp

Enable the Warp Agent, configure an LLM provider, and the Connect AI MCP endpoint in Warp so the agent can discover and call live data tools.

1. Download and install Warp, and then sign up or log in to your Warp account
2. Click the Tabs panel icon at the top left of the window, or press Ctrl + Shift + B
3. Click Settings, expand Agents, select Warp Agent, and toggle Warp Agent on

Configure an LLM provider

The Warp Agent needs an LLM provider to interpret your prompts and decide which MCP tools to call. Add an API key for your preferred provider.

1. On the same Warp Agent page, scroll down to the Custom Inference section
2. Enter the API key for the LLM provider of your choice (e.g., OpenAI, Anthropic, or Google)

Add the Connect AI MCP Server

1. Under Agents, click MCP servers, and then click Add
2. In the Add New MCP Server editor, paste the following JSON configuration:

   {
     "mcpServers": {
       "CData_Connect_AI": {
         "url": "https://mcp.cloud.cdata.com/mcp",
         "headers": {
           "Authorization": "Basic your_base64_encoded_email_PAT"
         }
       }
     }
   }

   Note: Combine your Connect AI email and PAT in the format email:PAT, Base64 encode the combined string, and prefix it with Basic. For example, given [email protected]:ABC123...XYZ, the header value becomes something like: Basic dXNlckBteWRvbWFpbjphSzkvbVB4Mi9Rcjd2TjQ...

   
3. Click Save to add the MCP server
4. Under My MCPs, confirm that CData_Connect_AI appears with the toggle enabled and the tools available

With the MCP server and an LLM provider configured, the Warp Agent is ready to interact with live SingleStore data through Connect AI.

Step 3: Interact with live SingleStore data from the Warp Agent

Use natural language prompts in the Warp Agent to explore live SingleStore data.

1. Click the icon in the left navigation bar and select Agent
2. Enter a prompt to interact with your data, for example:
   • List the sources available in my CData_Connect_AI mcp connection
   • Show me what I can explore in SingleStore
   • Fetch the five most recent records from SingleStore data
   
3. The agent calls the Connect AI MCP Server and returns live results from SingleStore data

Your Warp Agent now calls the Connect AI MCP Server to interact with live SingleStore data through remote MCP tools, all from the terminal.

Get CData Connect AI

To interact with hundreds of SaaS and enterprise data sources directly from your AI agents and cloud applications, try CData Connect AI. Download a free 14-day trial of CData Connect AI, and our Support Team is available to answer any questions.