Vizro vs flowsery
Vizro is an MCP server published by mckinsey. Marketplaces we read that list it: 1 (Docker MCP Catalog). flowsery is a plugin bundle for AI coding tools published by Flowsery. Marketplaces we read that list it: 1 (Claude Code: claude-plugins-community). 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
| Marketplace | ||
|---|---|---|
| Docker MCP Catalog | Listed Version: sha256:ddec90039ea1 Forks (GitHub): 304 Pulls (Docker Hub): 37 320 Stars (Docker Hub): 1 Stars (GitHub): 3 801 Not marked · First seen |
Not listed |
| Claude Code: claude-plugins-community | Not listed | Listed Version: 1.0.0 Forks (GitHub): 0 Stars (GitHub): 0 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 | Vizro | flowsery |
|---|---|---|
| Marketplaces that list it | 1 | 1 |
| Stars (GitHub) (differs) | 3 801 (better) | 0 (worse) |
| Pulls (Docker Hub) (differs) | 37 320 | No figure on Docker Hub |
| Forks (GitHub) (differs) | 304 (better) | 0 (worse) |
| Last release | Not published | Not published |
| Where it runs (differs) | On your machine (mcp/vizro) | Installs as a plugin bundle |
| Transport (differs) | stdio | Not stated |
| Tools it declares (differs) | 6 | Not published |
| Environment variables it asks for | Not published | Not published |
| Parts of the bundle (differs) | Not a bundle | 1 |
| Licence (differs) | Apache-2.0 | MIT |
| Repository (differs) | github.com/mckinsey/vizro | github.com/flowsery/claude-plugin |
| 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.
What each says it does
Vizro
provides tools and templates to create a functioning Vizro chart or dashboard step by step.
flowsery
Query privacy-first, cookie-free web analytics directly from Claude Code. A Google Analytics alternative with real-time visitor data, traffic breakdowns, revenue attribution, and full visitor profiles. Key features: - Real-time active visitor count with geographic map - Site overview, time series, and 24 breakdown dimensions (pages, referrers, countries, devices, browsers, UTM params, channels, and more) - Visitor profiles with full activity timelines, identity, and revenue - Goal tracking and custom event recording - Revenue tracking with auto-detection for Stripe, LemonSqueezy, and Polar - Filter every query by country, device, UTM source, page, channel, and 15+ other dimensions
How to run each
Vizro As a local MCP server: Docker image
claude mcp add --transport stdio vizro -- docker run -i --rm mcp/vizro
flowsery As a Claude Code plugin
/plugin marketplace add anthropics/claude-plugins-community
/plugin install flowsery@claude-community
Commands built only from what the marketplaces declare; the full set for every client is on each card.
Tools each declares
The marketplaces of flowsery publish no list of tools, so we do not compare tools.
Settings each asks for
Neither one's marketplaces publish the settings it asks for.
What it can do: Vizro · What it can do: flowsery · 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/anthropics/claude-plugins-community/blob/HEAD/.claude-plugin/marketplace.json. Figures come from our own regular passes over the marketplaces, last read on . We publish no contact details for plugin publishers.