MCP Directory

How to add SingleStore MCP Server to Cursor

Query and manage SingleStore workspaces, jobs, notebooks, and Stage files in natural language. Paste the config into ~/.cursor/mcp.json and restart Cursor.

Last updated June 14, 2026 · 33★ · stdio · oauth

Cursor config for SingleStore MCP Server

uvx singlestore-mcp-server start
{
  "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.

Setup steps

  1. 1Open Cursor → Settings → MCP → Add new MCP server (or edit ~/.cursor/mcp.json directly).
  2. 2Paste the SingleStore MCP Server config below into the "mcpServers" object.
  3. 3Fill in placeholder secrets, then save.
  4. 4Cursor reloads MCP servers automatically — check Settings → MCP for a green status dot.
  5. 5Ask Cursor to use one of SingleStore MCP Server's tools to confirm it's connected.

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)

What SingleStore MCP Server can do in Cursor

get_user_info

Retrieve details about the current user.

organization_info

Retrieve details about the user's current organization.

choose_organization

Choose from available organizations (only available when the API key environment variable is not set).

set_organization

Set the active organization by organization_id (only available when the API key environment variable is not set).

workspace_groups_info

Retrieve details about the workspace groups accessible to the user.

workspaces_info

Retrieve details about the workspaces in a specific workspace group (workspace_group_id).

resume_workspace

Resume a suspended workspace by workspace_id.

list_starter_workspaces

List all starter workspaces accessible to the user.

Security

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 + Cursor FAQ

Where is the Cursor config file?

Cursor reads MCP servers from ~/.cursor/mcp.json. Paste the SingleStore MCP Server config there under the "mcpServers" key and restart the client.

Is SingleStore MCP Server safe to use with Cursor?

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.

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.

View repo Full SingleStore MCP Server page