SingleStore MCP Server
Query and manage SingleStore workspaces, jobs, notebooks, and Stage files in natural language.
Add to your client
Copy the config for your MCP client and paste it into its config file.
uvx singlestore-mcp-server startPaste into ~/Library/Application Support/Claude/claude_desktop_config.json
{
"mcpServers": {
"singlestore-mcp-server": {
"command": "uvx",
"args": [
"singlestore-mcp-server",
"start"
]
}
}
}Requires `uv` (the Python package runner). Install it from https://docs.astral.sh/uv/ if `uvx` is not found.
Step-by-step guides: Add to Claude Desktop · Add to Cursor · Add to Windsurf
Before you start
- Python >= 3.10.0
- uvx (from uv) installed in your Python environment
- An MCP client such as VS Code, Cursor, Windsurf, Claude Desktop, Claude Code, or Goose
- A SingleStore account (authenticated via browser OAuth on first start)
About SingleStore MCP Server
An installable MCP server, distributed as the PyPI package singlestore-mcp-server and run with uvx, that connects MCP clients to the SingleStore Management API and database services. It supports workspace lifecycle management, SQL execution, notebooks, scheduled jobs, and Stage file operations, with zero-config browser OAuth authentication by default.
Tools & capabilities (24)
get_user_infoRetrieve details about the current user.
organization_infoRetrieve details about the user's current organization.
choose_organizationChoose from available organizations (only available when the API key environment variable is not set).
set_organizationSet the active organization by organization_id (only available when the API key environment variable is not set).
workspace_groups_infoRetrieve details about the workspace groups accessible to the user.
workspaces_infoRetrieve details about the workspaces in a specific workspace group (workspace_group_id).
resume_workspaceResume a suspended workspace by workspace_id.
list_starter_workspacesList all starter workspaces accessible to the user.
create_starter_workspaceCreate a new starter workspace from the given configuration parameters.
terminate_starter_workspaceTerminate an existing starter workspace by workspace_id.
list_regionsRetrieve a list of all regions that support workspaces.
list_sharedtier_regionsRetrieve a list of shared tier regions.
run_sqlExecute SQL operations on a connected workspace (workspace_id, database, sql_query, and connection parameters) and return structured results.
create_notebook_fileCreate a new notebook file in SingleStore Spaces (notebook_name, optional content).
upload_notebook_fileUpload a notebook file to SingleStore Spaces (file_path, notebook_name).
create_job_from_notebookCreate a scheduled job from a notebook (notebook_path, schedule_mode, etc.).
get_jobRetrieve details of an existing job by job_id.
delete_jobDelete an existing job by job_id.
stage_list_filesList files and folders in a Stage deployment's file system (deployment_id, optional path).
stage_get_fileGet a file from Stage by path, returning metadata, a download URL, or text content (deployment_id, path, return_type).
stage_create_folderCreate a folder in Stage (deployment_id, path).
stage_upload_fileUpload a file to Stage with text content (deployment_id, path, content, local_path).
stage_moveMove or rename a file or folder in Stage (deployment_id, source_path, destination_path).
stage_deleteDelete a file or folder from Stage (deployment_id, path).
What this server can do
SingleStore MCP Server provides tools for these capabilities — tap one to see every MCP server that does the same:
When to use it
- Querying SingleStore databases with natural language and returning structured SQL results
- Managing workspace lifecycle — listing, resuming, creating, and terminating starter workspaces
- Creating, uploading, and scheduling notebooks as jobs in SingleStore Spaces
- Managing files and folders in Stage deployments (list, get, upload, move, delete)
- Inspecting user, organization, workspace group, and region information
Security notes
The default setup uses browser-based OAuth and requires no static credentials. When running via Docker, OAuth is not supported, so an MCP_API_KEY environment variable must be supplied instead; treat that key as a secret. The run_sql tool executes arbitrary SQL against connected workspaces, so scope database permissions appropriately.
SingleStore MCP Server FAQ
Do I need an API key?
No. The default setup requires no API keys, tokens, or environment variables — the server authenticates automatically via browser OAuth when started. An MCP_API_KEY is only required for the Docker-based setup, where OAuth is not supported.
How do I install it?
Add the standard mcpServers config using command "uvx" with args ["singlestore-mcp-server", "start"], or run the automatic setup, e.g. `uvx singlestore-mcp-server init --client=claude-desktop`. For Claude Code you can also run `claude mcp add singlestore-mcp-server uvx singlestore-mcp-server start`.
Which clients are supported?
Any MCP-compatible client, including Claude Desktop, Claude Code, Cursor, VS Code, Windsurf, Gemini CLI, LM Studio, Goose, and Qodo Gen.
How do I discover what the server can do?
Call the /help prompt in your chat to see what the MCP server offers.
Alternatives to SingleStore MCP Server
Compare all alternatives →
Google's official MCP server with prebuilt BigQuery tools, querying datasets via Application Default Credentials.
Create, manage, and query your InstantDB apps, schemas, permissions, and data from your AI editor.
Compare SingleStore MCP Server with: