Ext Ops Panel
Open dashboard
Comparison

Metabase vs Data Visualisation And Publishing

Metabase is an MCP server published by easecloudio. Marketplaces we read that list it: 1 (Docker MCP Catalog). Data Visualisation And Publishing is a plugin bundle for AI coding tools published by danielrosehill. Marketplaces we read that list it: 1 (Community GitHub marketplaces). As of our marketplace pass on 2026-10-17. 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
MarketplaceMetabaseData Visualisation And Publishing
Docker MCP Catalog Listed
Version: sha256:02e633ae77a1
Forks (GitHub): 25
Pulls (Docker Hub): 50 863
Stars (Docker Hub): 3
Stars (GitHub): 82
Not marked · First seen
Not listed
Community marketplace danielrosehill/claude-code-plugins Not listed Listed
Version: 1.1.0
Forks (GitHub): 0
Stars (GitHub): 2
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 Data Visualisation And Publishing
FactMetabaseData Visualisation And Publishing
Marketplaces that list it11
Stars (GitHub) (differs)82 (better)2 (worse)
Pulls (Docker Hub) (differs)50 863No figure on Docker Hub
Forks (GitHub) (differs)25 (better)0 (worse)
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 bundle7
LicenceMITMIT
Repository (differs)github.com/easecloudio/mcp-metabase-servergithub.com/danielrosehill/claude-data-visualisation-and-publishing-plugin
Changes in the last 7 days (differs)02
First seen (differs)2026-10-112026-10-15

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.

Data Visualisation And Publishing

In its own words, on Community GitHub marketplaces:

Create static and interactive data visualisations for reports, repos, and data storytelling. Purpose-organised inventory of 60+ validated open-source tools as a head start — static figures (Matplotlib, Seaborn, ggplot2), web charts (Chart.js, ECharts, Plotly.js, ApexCharts, Highcharts), high-perf (uPlot, Perspective, Lightweight Charts), bespoke (D3, Observable Plot, Vega/Vega-Lite, visx, Victory), Python/R apps (Bokeh, Dash, Altair, Streamlit, Gradio, Shiny, D-Tale, Briefer, Preswald), storytelling (Vizzu, VChart, vue-data-ui, SandDance), graphs (G6, sigma.js, Cytoscape, Gephi, Graphviz, GoJS, 3d-force-graph, Constellation), maps (deck.gl, react-map-gl, Leaflet, MapLibre, OpenLayers, folium, react-globe.gl), mobile (fl_chart, F2), BI (Superset, Metabase, Grafana, Kibana, Redash, Chartbrew), diagrams-as-code (Mermaid, PlantUML), domain-specific (Iris, QuantInvestStrats, XCharts, BizCharts, Tablesaw).

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)

Data Visualisation And Publishing As a Claude Code plugin

Claude Code
/plugin marketplace add danielrosehill/claude-code-plugins
/plugin install data-visualisation-and-publishing@danielrosehill

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

Tools each declares

The marketplaces of Data Visualisation And Publishing publish no list of tools, so we do not compare tools.

Settings each asks for

The marketplaces of Data Visualisation And Publishing publish no settings it asks for, so we do not compare settings.

What it can do: Metabase · What it can do: Data Visualisation And Publishing · 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