Vizro vs FlowScope UX Flow Analyser
Vizro is an MCP server published by mckinsey. Marketplaces we read that list it: 1 (Docker MCP Catalog). FlowScope UX Flow Analyser is an MCP server published by DavidNgugi. Marketplaces we read that list it: 2 (Official MCP Registry, Community GitHub marketplaces). As of our marketplace pass on 2026-10-14. 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 |  Vizro |  FlowScope UX Flow Analyser |
|---|---|---|
| Docker MCP Catalog | Listed Version: sha256:ddec90039ea1 Forks (GitHub): 303 Pulls (Docker Hub): 37 324 Stars (Docker Hub): 1 Stars (GitHub): 3 804 Not marked · First seen |
Not listed |
| Official MCP Registry | Not listed | Listed Version: 0.1.1 Downloads/month (PyPI): 0 Downloads/week (PyPI): 346 Forks (GitHub): 1 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
| Fact | Vizro | FlowScope UX Flow Analyser |
|---|---|---|
| Marketplaces that list it (differs) | 1 (worse) | 2 (better) |
| Stars (GitHub) (differs) | 3 804 (better) | 2 (worse) |
| Pulls (Docker Hub) (differs) | 37 324 | No figure on Docker Hub |
| Forks (GitHub) (differs) | 303 (better) | 1 (worse) |
| Last release | Not published | Not published |
| Where it runs (differs) | On your machine (mcp/vizro) | On your machine (flowscope-mcp) |
| Transport | stdio | stdio |
| Tools it declares (differs) | 6 | Not published |
| Environment variables it asks for (differs) | Not published | 3, secrets among them: 1 |
| Parts of the bundle (differs) | Not a bundle | 3 |
| Licence (differs) | Apache-2.0 | MIT |
| Repository (differs) | github.com/mckinsey/vizro | github.com/davidngugi/flowscope |
| Changes in the last 7 days (differs) | 0 | 2 |
| 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.
FlowScope UX Flow Analyser
Turn YouTube product demos into structured UX flow reports, and compare demos side by side.
How to run each
Vizro As a local MCP server: Docker image
claude mcp add --transport stdio vizro -- docker run -i --rm mcp/vizroFlowScope UX Flow Analyser As a local MCP server: PyPI package
claude mcp add --env "FLOWSCOPE_API_TOKEN=<YOUR_FLOWSCOPE_API_TOKEN>" --transport stdio flowscope -- uvx flowscope-mcpRequires: FLOWSCOPE_API_TOKEN (secret)
Commands built only from what the marketplaces declare; the full set for every client is on each card.
Tools each declares
The marketplaces of FlowScope UX Flow Analyser publish no list of tools, so we do not compare tools.
Settings each asks for
The marketplaces of Vizro publish no settings it asks for, so we do not compare settings.
What it can do: Vizro · What it can do: FlowScope UX Flow Analyser · Compare two other plugins
Data comes from the Docker MCP Catalog (desktop.docker.com/mcp/catalog) and Docker Hub. Data comes from the Official MCP Registry (registry.modelcontextprotocol.io), CC0 1.0. 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.