Ext Ops Panel
Open dashboard
Comparison

Singlestore vs omni-integrations

Singlestore is an MCP server published by singlestore-labs. Marketplaces we read that list it: 1 (Docker MCP Catalog). omni-integrations is a plugin bundle for AI coding tools published by Omni Analytics. Marketplaces we read that list it: 1 (Community GitHub marketplaces). As of our marketplace pass on 2026-11-03. 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
MarketplaceSinglestoreomni-integrations
Docker MCP Catalog Listed
Version: sha256:94913307e8b1
Forks (GitHub): 17
Pulls (Docker Hub): 10 908
Stars (Docker Hub): 0
Stars (GitHub): 33
Not marked · First seen
Not listed
Community marketplace exploreomni/omni-agent-skills Not listed Listed
Version: 1.24.1
Forks (GitHub): 9
Stars (GitHub): 45
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 omni-integrations
FactSinglestoreomni-integrations
Marketplaces that list it11
Stars (GitHub) (differs)33 (worse)45 (better)
Pulls (Docker Hub) (differs)10 908No figure on Docker Hub
Forks (GitHub) (differs)17 (better)9 (worse)
Last release (differs)Not published2026-11-03
Where it runs (differs)On your machine (mcp/singlestore)Installs as a plugin bundle
Transport (differs)stdioNot stated
Tools it declares (differs)28Not published
Environment variables it asks for (differs)1, secrets among them: 1Not published
Parts of the bundle (differs)Not a bundle3
Licence (differs)MITApache-2.0
Repository (differs)github.com/singlestore-labs/mcp-server-singlestoregithub.com/exploreomni/omni-agent-skills
Changes in the last 7 days (differs)04
First seen (differs)2026-10-112026-10-18

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.

omni-integrations

In its own words, on Community GitHub marketplaces:

Integration skills for connecting Omni Analytics with external data platforms — Snowflake Semantic Views, Databricks Metric Views, dbt MetricFlow, and more.

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)

omni-integrations As a Claude Code plugin

Claude Code
/plugin marketplace add exploreomni/omni-agent-skills
/plugin install omni-integrations@omni-analytics

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

Tools each declares

The marketplaces of omni-integrations publish no list of tools, so we do not compare tools.

Settings each asks for

The marketplaces of omni-integrations publish no settings it asks for, so we do not compare settings.

What it can do: Singlestore · What it can do: omni-integrations · Compare two other plugins

Data comes from the Docker MCP Catalog (desktop.docker.com/mcp/catalog) and Docker Hub. Data comes from public marketplace files in GitHub repositories of their authors. 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