Integration

SingleStore integration

SingleStore Management API. Create and terminate workspace groups, size, suspend and resume the workspaces inside them, read the connection endpoint of a workspace, list regions, read the current organization and its members, manage starter workspaces on the shared tier, list secrets and teams, and pull the compute and storage usage of the organization. This is the control plane: running SQL happens on the per workspace Data API, whose host is the workspace endpoint and whose credential is a database user and password rather than the token used here.

Connect SingleStore How integrations work

Ask it in chat

Say what should happen.
The workflow builds itself.

When this happens, do that in SingleStore.Built from the 21 SingleStore tools below, on the connection you add once.

Common SingleStore use cases

tearing down a temporary environment
auditing who has access to the organization
charging back compute credits per workspace
spinning up a small database for a prototype
opening a deployment to a new office IP range
reading the connection endpoint of a workspace
waking a workspace before a scheduled job runs
checking which IP ranges may reach a deployment
confirming which account a script is running as
provisioning a deployment for a new environment

What you can do with SingleStore

Each of these is one operation on one endpoint, available both as a workflow step and as a tool an AI agent can call on its own. Nothing bundles several operations into one action, so what a run did stays readable afterwards.

Most endpoints run on the free plan. A few, mainly the ones that publish on your behalf, need a paid plan.

Workspace, 7 operations

create_workspaceCreate workspacePOSTCreates a workspace of a chosen size inside an existing workspace group.
delete_workspaceDelete workspaceDELETETerminates a workspace and detaches its databases.
get_workspaceGet workspaceGETReturns a workspace with its size, state, endpoint and autoscaling settings.
list_workspacesList workspacesGETLists the workspaces of a group with their size, state and connection endpoint.
resume_workspaceResume workspacePOSTStarts a suspended workspace back up.
suspend_workspaceSuspend workspacePOSTStops the compute of a workspace while keeping its data.
update_workspaceUpdate workspacePATCHResizes a workspace or changes its cache, autoscaling and auto suspend settings.

Workspace group, 5 operations

create_workspace_groupCreate workspace groupPOSTCreates a workspace group and returns its generated admin password.
delete_workspace_groupDelete workspace groupDELETETerminates a workspace group and everything inside it.
get_workspace_groupGet workspace groupGETReturns a workspace group with its firewall ranges and maintenance window.
list_workspace_groupsList workspace groupsGETLists workspace groups with their region, firewall ranges and state.
update_workspace_groupUpdate workspace groupPATCHRenames a workspace group or changes its firewall ranges, expiry or admin password.

Starter workspace, 2 operations

create_starter_workspaceCreate starter workspacePOSTCreates a shared tier starter workspace with one database.
list_starter_workspacesList starter workspacesGETLists shared tier starter workspaces with their database name and endpoint.

User, 2 operations

get_current_userGet current userGETReturns the user or service account the token belongs to.
list_usersList usersGETLists the members of the organization, including service accounts.

Billing usage, 1 operation

get_billing_usageGet billing usageGETReturns compute credit and storage usage over a time range, aggregated by hour, day or month.

Organization, 1 operation

get_current_organizationGet current organizationGETReturns the organization the token belongs to and the IP ranges allowed to use the API.

Region, 1 operation

list_regionsList regionsGETLists the regions a workspace group can be created in.

Secret, 1 operation

list_secretsList secretsGETLists stored secrets with their creation and update history.

Team, 1 operation

list_teamsList teamsGETLists teams with their member users and nested member teams.

Use SingleStore from Claude Code, Cursor or Codex

Connect SingleStore in LiveContext, create an API key in Settings, then add the LiveContext MCP server to your client. Its SingleStore operations become tools the client can call, next to every other integration you connected.

Claude Code

claude mcp add --transport http livecontext https://livecontext.ai/mcp --header "X-API-Key: YOUR_API_KEY"

Codex (~/.codex/config.toml)

[mcp_servers.livecontext]
url = "https://livecontext.ai/mcp"

[mcp_servers.livecontext.http_headers]
"X-API-Key" = "YOUR_API_KEY"

Cursor, Claude Desktop and other JSON configs

{
  "mcpServers": {
    "livecontext": {
      "type": "http",
      "url": "https://livecontext.ai/mcp",
      "headers": {
        "X-API-Key": "YOUR_API_KEY"
      }
    }
  }
}

Set up the MCP server step by step

How to connect SingleStore

Create your workspace
Sign up free. Nothing to install.
Connect SingleStore once
Add your SingleStore connection in Settings. Every tool from this integration reuses it, and secrets are encrypted at rest and visible only to you.
Describe the job in chat
The workflow builds itself in front of you and picks the endpoints it needs. Drag the steps yourself on the canvas whenever you would rather be explicit.

SingleStore integration FAQ

What can you do with the SingleStore integration?

LiveContext exposes 21 operations on SingleStore, covering workspace, workspace group, starter workspace and user. Common uses include tearing down a temporary environment, auditing who has access to the organization and charging back compute credits per workspace.