SingleStore MCP Server
by Rodriguespn
MCP server for interacting with SingleStore Management API and services
What is SingleStore MCP Server
SingleStore MCP Server
Model Context Protocol (MCP) is a standardized protocol designed to manage context between large language models (LLMs) and external systems. This repository provides an installer and an MCP Server for Singlestore, enabling seamless integration.
With MCP, you can use Claude Desktop or any compatible MCP client to interact with SingleStore using natural language, making it easier to perform complex operations effortlessly.
Claude Setup
Installing via Smithery
To install mcp-server-singlestore for Claude Desktop automatically via Smithery:
npx -y @smithery/cli install @singlestore-labs/mcp-server-singlestore --client claude
Requirements
- Python >= v3.11.0
- Pipx installed on your python environment
- Claude Desktop
How to use locally
- Add the following config to your Claude Desktop config file
- Restart Claude Desktop after making changes to the configuration
{
"mcpServers": {
"singlestore-mcp-server": {
"command": "pipx",
"args": [
"run",
"singlestore-mcp-server"
],
"env": {
"SINGLESTORE_DB_USERNAME": "your-database-username",
"SINGLESTORE_DB_PASSWORD": "your-database-password",
"SINGLESTORE_API_KEY": "your-api-key"
}
}
}
}
Note:
You can get your API key and DB credentials on SingleStore's Helios Portal
Components
Tools
The server implements the following tools:
- workspace_groups_info: Retrieve details about the workspace groups accessible to the user
- No arguments required
- Returns details of the workspace groups
- workspaces_info: Retrieve details about the workspaces in a specific workspace group
- Arguments:
workspaceGroupID
(string) - Returns details of the workspaces
- Arguments:
- organization_info: Retrieve details about the user's current organization
- No arguments required
- Returns details of the organization
- list_of_regions: Retrieve a list of all regions that support workspaces for the user
- No arguments required
- Returns a list of regions
- execute_sql: Execute SQL operations on a connected workspace
- Arguments:
workspace_group_identifier
,workspace_identifier
,username
,password
,database
,sql_query
- Returns the results of the SQL query in a structured format
- Arguments:
- list_virtual_workspaces: List all starter workspaces accessible to the user
- No arguments required
- Returns details of available starter workspaces
- create_virtual_workspace: Create a new starter workspace with a user
- Arguments:
name
: Name of the starter workspacedatabase_name
: Name of the database to createusername
: Username for accessing the workspacepassword
: Password for the userworkspace_group
: Object containingname
(optional) andcellID
(mandatory)
- Returns details of the created workspace and user
- Arguments:
- execute_sql_on_virtual_workspace: Execute SQL operations on a virtual workspace
- Arguments:
virtual_workspace_id
,username
,password
,sql_query
- Returns the results of the SQL query in a structured format including data, row count, columns, and status
- Arguments:
- list_notebook_samples: List all notebook samples available in SingleStore Spaces
- No arguments required
- Returns details of available notebook samples
- create_notebook: Create a new notebook in the user's personal space
- Arguments:
notebook_name
,content
(optional) - Returns details of the created notebook
- Arguments:
- list_personal_files: List all files in the user's personal space
- No arguments required
- Returns details of all files in the user's personal space
- create_scheduled_job: Create a new scheduled job to run a notebook
- Arguments:
name
: Name for the jobnotebook_path
: Path to the notebook to executeschedule_mode
: Once or Recurringexecution_interval_minutes
: Minutes between executions (optional)start_at
: When to start the job (optional)description
: Description of the job (optional)create_snapshot
: Whether to create notebook snapshots (optional)runtime_name
: Name of the runtime environmentparameters
: Parameters for the job (optional)target_config
: Target configuration for the job (optional)
- Returns details of the created job
- Arguments:
- get_job_details: Get details about a specific job
- Arguments:
job_id
- Returns detailed information about the specified job
- Arguments:
- list_job_executions: List execution history for a specific job
- Arguments:
job_id
,start
(optional),end
(optional) - Returns execution history for the specified job
- Arguments:
Configuration
The server requires the following environment variables:
# SingleStore's management API key (required)
SINGLESTORE_API_KEY=your_api_key_here
# Database credentials (optional - can be provided as input parameters)
SINGLESTORE_DB_USERNAME=your_db_username_here
SINGLESTORE_DB_PASSWORD=your_db_password_here
Leave a Comment
Comments section will be available soon. Stay tuned!
Frequently Asked Questions
What is MCP?
MCP (Model Context Protocol) is an open protocol that standardizes how applications provide context to LLMs. Think of MCP like a USB-C port for AI applications, providing a standardized way to connect AI models to different data sources and tools.
What are MCP Servers?
MCP Servers are lightweight programs that expose specific capabilities through the standardized Model Context Protocol. They act as bridges between LLMs like Claude and various data sources or services, allowing secure access to files, databases, APIs, and other resources.
How do MCP Servers work?
MCP Servers follow a client-server architecture where a host application (like Claude Desktop) connects to multiple servers. Each server provides specific functionality through standardized endpoints and protocols, enabling Claude to access data and perform actions through the standardized protocol.
Are MCP Servers secure?
Yes, MCP Servers are designed with security in mind. They run locally with explicit configuration and permissions, require user approval for actions, and include built-in security features to prevent unauthorized access and ensure data privacy.
Related MCP Servers
21st.dev Magic AI Agent
It's like v0 but in your Cursor/WindSurf/Cline. 21st dev Magic MCP server for working with your frontend like Magic
Requirements:
A Model Context Protocol Server for connecting with Adfin APIs
AgentQL MCP Server
Model Context Protocol server that integrates AgentQL's data extraction capabilities.
AgentRPC
A universal RPC layer for AI agents. Connect to any function, any language, any framework, in minutes.
Aiven MCP Server
Model Context Protocol server for Aiven
IoTDB MCP Server
Apache IoTDB MCP Server
Apify Model Context Protocol (MCP) Server
Model Context Protocol (MCP) Server for Apify's Actors
APIMatic Validator MCP Server
APIMatic Validator MCP Server for validating OpenAPI specs via APIMatic's API with MCP
๐ Audiense Insights MCP Server
Audiense Insights MCP Server is a server based on the Model Context Protocol (MCP) that allows Claude and other MCP-compatible clients to interact with your Audiense Insights account
Bankless Onchain MCP Server
Bringing the bankless onchain API to MCP
Submit Your MCP Server
Share your MCP server with the community
Submit Now