Ext Ops Panel
Open dashboard
Comparison

Metabase vs Salesforce (Headless 360, Beta)

Metabase is an MCP server published by easecloudio. Marketplaces we read that list it: 1 (Docker MCP Catalog). Salesforce (Headless 360, Beta) is a plugin bundle for AI coding tools published by Cursor. Marketplaces we read that list it: 1 (Cursor: cursor/plugins). As of our marketplace pass on 2026-10-13. 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
MarketplaceMetabaseSalesforce (Headless 360, Beta)
Docker MCP Catalog Listed
Version: sha256:02e633ae77a1
Forks (GitHub): 25
Pulls (Docker Hub): 50 672
Stars (Docker Hub): 3
Stars (GitHub): 82
Not marked · First seen
Not listed
Cursor: cursor/plugins Not listed Listed
Version: 1.0.0
Forks (GitHub): 1 086
Stars (GitHub): 11 186
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

Metabase vs Salesforce (Headless 360, Beta)
FactMetabaseSalesforce (Headless 360, Beta)
Marketplaces that list it11
Stars (GitHub) (differs)82 (worse)11 186 (better)
Pulls (Docker Hub) (differs)50 672No figure on Docker Hub
Forks (GitHub) (differs)25 (worse)1 086 (better)
Last releaseNot publishedNot published
Where it runs (differs)On your machine (mcp/metabase)Installs as a plugin bundle
Transport (differs)stdioNot stated
Tools it declares (differs)28Not published
Environment variables it asks for (differs)4, secrets among them: 2Not published
Parts of the bundle (differs)Not a bundle1
LicenceMITMIT
Repository (differs)github.com/easecloudio/mcp-metabase-servergithub.com/cursor/plugins
Changes in the last 7 days00
First seen2026-10-112026-10-11

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

Metabase

In its own words, on Docker MCP Catalog:

A comprehensive MCP server for Metabase with 70+ tools.

Salesforce (Headless 360, Beta)

In its own words, on Cursor: cursor/plugins:

Manage records, users, and org setup across Salesforce.

How to run each

Metabase As a local MCP server: Docker image

Claude Code
claude mcp add --env "METABASE_API_KEY=<YOUR_METABASE_API_KEY>" --env "METABASE_PASSWORD=<YOUR_METABASE_PASSWORD>" --transport stdio metabase -- docker run -i --rm -e METABASE_API_KEY -e METABASE_PASSWORD mcp/metabase

Requires: METABASE_API_KEY (secret), METABASE_PASSWORD (secret)

Salesforce (Headless 360, Beta)

No data for an automatic command: what its marketplaces declare does not say unambiguously how to connect it.

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

Tools each declares

The marketplaces of Salesforce (Headless 360, Beta) publish no list of tools, so we do not compare tools.

Settings each asks for

The marketplaces of Salesforce (Headless 360, Beta) publish no settings it asks for, so we do not compare settings.

What it can do: Metabase · What it can do: Salesforce (Headless 360, Beta) · Compare two other plugins

Data comes from the Docker MCP Catalog (desktop.docker.com/mcp/catalog) and Docker Hub. Data comes from the public marketplace file https://github.com/cursor/plugins/blob/HEAD/.cursor-plugin/marketplace.json. 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