How to Query Live SingleStore Data in Claude Desktop
Model Context Protocol (MCP) is an emerging, open-source standard for connecting LLMs with external services and data sources. Through MCP Servers, AI clients can perform actions like opening Jira tickets, posting Slack messages, committing GitHub branches and more. With CData MCP Servers, these capabilities expand exponentially.
In this article, we guide the reader through installing the CData MCP Server for SingleStore, configuring the connection to SingleStore, and asking questions of the data in Claude Desktop.
Prerequisites
You need to download Claude Desktop (download) and create an account before continuing.
Overview
Here's a quick overview of the steps:
- Download and install the CData MCP Server for SingleStore
- Configure the connection to SingleStore
- Ask questions about the data in Claude Desktop
Step 1: Download and install the CData MCP Server
- To begin, navigate to https://www.cdata.com/solutions/mcp/connectors and download the CData MCP Server for SingleStore.
- Find and double-click the installer to begin the installation.
- Follow the prompts to complete the installation.
When the installation is complete, you are ready to configure your MCP Server by connecting to SingleStore.
Step 2: Configure the connection to SingleStore
- After installation, the CData MCP Server configuration wizard should open automatically.
NOTE: If the wizard does not open automatically, search for "CData MCP Server" in the Windows search bar and double-click the application.

- Click the dropdown menu in MCP Configuration > Configuration Name and select "
"
- Name the configuration (e.g. "cdatasinglestore") and click "OK."
NOTE: This name is used as the name for the MCP server and as the prefix for all of the MCP Server's tools.
Connecting 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.
Enter the appropriate connection properties in the configuration wizard.
- Click "Connect" to authenticate with SingleStore.
- Finally, click "Save Configuration" to save the MCP server.
NOTE: This saves the configuration details to a separate file and updates the Claude Desktop configuration file (claude_desktop_config.json) to start the CData MCP Server when the Claude Desktop client starts.
With the CData MCP Server configured, you are ready to start asking questions of your live data from Claude.
Step 3: Ask AI for answers from live SingleStore data
Now that we have installed the CData MCP Server and configured a connection, we are ready to start with SingleStore data in Claude Desktop.
- Open Claude Desktop. It may take a moment for the MCP Servers to start, but you will see the list of servers and tools available in the Claude interface (look for the settings icon below the prompt bar).
You can individually enable and disable specific tools by clicking on the server name.
- Now that you have connected, you can ask Claude questions about the SingleStore data. For example: "Can you give me a quantitative analysis about my closed-won opportunities by industry?"
NOTE: Claude may need to explore the SingleStore data to make sense of it before it can begin answering questions of the data. The tabular model presented by CData alongside the database tools available simplify the data exploration and analysis for an LLM.
Connect your AI to your data today!
CData MCP Servers make it easier than ever for LLMs to work with live enterprise data. To explore the technology hands-on, download a free, 30-day trial or visit the CData Community to share insights, ask questions, and help shape the future of enterprise-ready AI.