Metabase vs Vizro
Metabase is an MCP server published by easecloudio. Marketplaces we read that list it: 1 (Docker MCP Catalog). Vizro is an MCP server published by mckinsey. Marketplaces we read that list it: 1 (Docker MCP Catalog). As of our marketplace pass on 2026-10-12. 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
| Marketplace | ||
|---|---|---|
| Docker MCP Catalog | Listed Version: sha256:02e633ae77a1 Forks (GitHub): 25 Pulls (Docker Hub): 50 623 Stars (Docker Hub): 3 Stars (GitHub): 82 Not marked · First seen |
Listed Version: sha256:ddec90039ea1 Forks (GitHub): 304 Pulls (Docker Hub): 37 315 Stars (Docker Hub): 1 Stars (GitHub): 3 798 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
| Fact | Metabase | Vizro |
|---|---|---|
| Marketplaces that list it | 1 | 1 |
| Stars (GitHub) (differs) | 82 (worse) | 3 798 (better) |
| Pulls (Docker Hub) (differs) | 50 623 (better) | 37 315 (worse) |
| Forks (GitHub) (differs) | 25 (worse) | 304 (better) |
| Last release | Not published | Not published |
| Where it runs (differs) | On your machine (mcp/metabase) | On your machine (mcp/vizro) |
| Transport | stdio | stdio |
| Tools it declares (differs) | 28 | 6 |
| Environment variables it asks for (differs) | 4, secrets among them: 2 | Not published |
| Licence (differs) | MIT | Apache-2.0 |
| Repository (differs) | github.com/easecloudio/mcp-metabase-server | github.com/mckinsey/vizro |
| Changes in the last 7 days | 0 | 0 |
| First seen | 2026-10-11 | 2026-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.
Tools each declares
Only Metabase declares
add_card_to_dashboardcreate_cardcreate_collectioncreate_dashboardcreate_database_connectioncreate_permission_groupcreate_userdelete_carddelete_dashboardexecute_cardexecute_queryget_dashboard_cards
Show the remaining 16
get_database_schemaget_database_sync_statusget_database_tableslist_cardslist_collectionslist_dashboardslist_databaseslist_permission_groupslist_usersremove_card_from_dashboardsearch_contentsync_database_schematest_database_connectionupdate_cardupdate_dashboardupdate_dashboard_card
Only Vizro declares
get_model_json_schemaget_sample_data_infoget_vizro_chart_or_dashboard_planload_and_analyze_datavalidate_chart_codevalidate_dashboard_config
Both declare
None
Tool names as each marketplace publishes them. More tools is not better in itself: compare what each needs for the job.
Settings each asks for
The marketplaces of Vizro publish no settings it asks for, so we do not compare settings.
What it can do: Metabase · What it can do: Vizro · Compare two other plugins
Data comes from the Docker MCP Catalog (desktop.docker.com/mcp/catalog) and Docker Hub. Figures come from our own regular passes over the marketplaces, last read on . We publish no contact details for plugin publishers.