Summary

Account operations and SQL in one place, with browser sign-in instead of a pasted key.

Most database servers stop at the query; this one also creates and resumes the workspace the query runs against, so an idle starter environment can be brought back mid-conversation rather than in a console tab. The Stage tools and the notebook-to-job path extend the same idea to files and scheduled work.

What it is

The SingleStore server. It covers the account and the data alike: organisations and workspaces, SQL against a connected workspace, notebooks and scheduled jobs, and the Stage file system.

What you get

Sign-in handled in the browser when the server starts — nothing to paste into a configuration file
Who you are and which organisation you are in, with a switch when you belong to several (get_user_info, organization_info, choose_organization, set_organization)
Workspace groups and the workspaces inside them, and a suspended workspace resumed (workspace_groups_info, workspaces_info, resume_workspace)
Starter workspaces listed, created and terminated, with the regions that support them (list_starter_workspaces, create_starter_workspace, terminate_starter_workspace, list_regions, list_sharedtier_regions)
SQL run against a connected workspace and database, with results returned structured (run_sql)
Notebooks created in or uploaded to SingleStore Spaces (create_notebook_file, upload_notebook_file)
A notebook turned into a scheduled job, then inspected or removed (create_job_from_notebook, get_job, delete_job)
Stage treated as a file system: list, read as metadata or a download link or text, create folders, upload, move and delete (stage_list_files, stage_get_file, stage_create_folder, stage_upload_file, stage_move, stage_delete)
A help prompt that tells you what the server can do, from inside the chat

Requirements

A SingleStore account. On the normal path there are no keys, tokens or environment variables — authentication happens in a browser at startup. Running it in a container is the exception: the browser flow does not work there, so a key is required and the organisation-switching tools are not offered.

Setup effort

One command — uvx singlestore-mcp-server start