Ext Ops Panel
Open dashboard
Comparison

Singlestore vs Camber - Remote Agentic Data Science

Singlestore is an MCP server published by singlestore-labs. Marketplaces we read that list it: 1 (Docker MCP Catalog). Camber - Remote Agentic Data Science is an MCP server published by camber-mcp.cambercloud.com. Marketplaces we read that list it: 1 (Official MCP Registry). As of our marketplace pass on 2026-10-27. This pair was picked by a reader, not by our comparison rule, so search engines are asked not to index the page.

Where each is published

Where each is published
MarketplaceSinglestoreCamber - Remote Agentic Data Science
Docker MCP Catalog Listed
Version: sha256:94913307e8b1
Forks (GitHub): 17
Pulls (Docker Hub): 10 843
Stars (Docker Hub): 0
Stars (GitHub): 33
Not marked · First seen
Not listed
Official MCP Registry Not listed Listed
Version: 1.0.4
No figure published
Not marked · First seen

Each figure is the marketplace's own and is never added up across marketplaces. A marketplace that publishes no figure shows none: no number is not zero.

The facts side by side

Singlestore vs Camber - Remote Agentic Data Science
FactSinglestoreCamber - Remote Agentic Data Science
Marketplaces that list it11
Stars (GitHub) (differs)33No figure on GitHub
Pulls (Docker Hub) (differs)10 843No figure on Docker Hub
Forks (GitHub) (differs)17No figure on GitHub
Last releaseNot publishedNot published
Where it runs (differs)On your machine (mcp/singlestore)Remote server (camber-mcp.cambercloud.com/mcp)
Transport (differs)stdioStreamable HTTP
Tools it declares (differs)28Not published
Environment variables it asks for (differs)1, secrets among them: 1Not published
Licence (differs)MITNot stated
Repository (differs)github.com/singlestore-labs/mcp-server-singlestoreNot stated
Changes in the last 7 days00
First seen2026-10-112026-10-11
Endpoint at the last check (differs)no remote endpoint we checkResponded 4 days ago

Lines where the two differ have a tinted background and bold values. Where the data itself says which value is better (more marketplaces, a larger figure of the same marketplace, a fresher release, a verified mark on a marketplace that lists both), the better one is also marked green with ▲ and the worse one red with ▼. Where it runs, the transport, the tools, the settings, hooks, the bundle's parts, the licence and the week's changes are marked only as different: more or fewer is not better in itself.

What each says it does

Singlestore

In its own words, on Docker MCP Catalog:

MCP server for interacting with SingleStore Management API and services.

Camber - Remote Agentic Data Science

In its own words, on Official MCP Registry:

Remote data science agents for Snowflake, Databricks & BigQuery in Claude/Cursor via MCP

How to run each

Singlestore As a local MCP server: Docker image

Claude Code
claude mcp add --env "MCP_API_KEY=<YOUR_MCP_API_KEY>" --transport stdio singlestore -- docker run -i --rm -e MCP_API_KEY mcp/singlestore

Requires: MCP_API_KEY (secret)

Camber - Remote Agentic Data Science As a remote MCP server

Claude Code
claude mcp add --transport http camber-mcp-server https://camber-mcp.cambercloud.com/mcp --header "Authorization: Bearer <YOUR_CAMBER_API_KEY>"

Requires: Authorization header

Commands built only from what the marketplaces declare; the full set for every client is on each card.

Only Camber - Remote Agentic Data Science has a remote endpoint we check. How we check endpoints

Tools each declares

The marketplaces of Camber - Remote Agentic Data Science publish no list of tools, so we do not compare tools.

Settings each asks for

The marketplaces of Camber - Remote Agentic Data Science publish no settings it asks for, so we do not compare settings.

What it can do: Singlestore · What it can do: Camber - Remote Agentic Data Science · Compare two other plugins

Data comes from the Docker MCP Catalog (desktop.docker.com/mcp/catalog) and Docker Hub. Data comes from the Official MCP Registry (registry.modelcontextprotocol.io), CC0 1.0. Figures come from our own regular passes over the marketplaces, last read on . We publish no contact details for plugin publishers.

Where the data comes from: how the catalog is built