n8n vs vizro-e2e-flow
n8n is an MCP server published by czlonkowski. Marketplaces we read that list it: 1 (Docker MCP Catalog). vizro-e2e-flow is a plugin bundle for AI coding tools published by Vizro Team. Marketplaces we read that list it: 1 (Community GitHub marketplaces). As of our marketplace pass on 2026-10-19. 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 |   n8n | |
|---|---|---|
| Docker MCP Catalog | Listed Version: sha256:061cdb8fbaa7 Forks (GitHub): 3 669 Pulls (Docker Hub): 155 215 Stars (Docker Hub): 23 Stars (GitHub): 23 103 Not marked · First seen |
Not listed |
| Community marketplace mckinsey/vizro | Not listed | Listed Version: 0.1.8 Forks (GitHub): 305 Stars (GitHub): 3 810 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 | n8n | vizro-e2e-flow |
|---|---|---|
| Marketplaces that list it | 1 | 1 |
| Stars (GitHub) (differs) | 23 103 (better) | 3 810 (worse) |
| Pulls (Docker Hub) (differs) | 155 215 | No figure on Docker Hub |
| Forks (GitHub) (differs) | 3 669 (better) | 305 (worse) |
| Last release | Not published | Not published |
| Where it runs (differs) | On your machine (mcp/n8n) | On your machine (@playwright/mcp) |
| Transport (differs) | stdio | Not stated |
| Tools it declares (differs) | 42 | Not published |
| Environment variables it asks for (differs) | 3, secrets among them: 1 | Not published |
| Parts of the bundle (differs) | Not a bundle | 6 |
| Licence (differs) | MIT | Not stated |
| Repository (differs) | github.com/czlonkowski/n8n-mcp | github.com/mckinsey/vizro |
| Changes in the last 7 days (differs) | 0 | 2 |
| First seen (differs) | 2026-10-11 | 2026-10-14 |
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
n8n
Bridges n8n's workflow automation platform with AI models, providing access to 543 n8n nodes, workflow templates, and AI-capable automation tools.
vizro-e2e-flow
Build Vizro dashboards from concept to deployment. Enforces a 2-phase workflow covering requirements, layout design, visualization selection, implementation with Python, and testing.
How to run each
n8n As a local MCP server: Docker image
claude mcp add --env "N8N_API_KEY=<YOUR_N8N_API_KEY>" --transport stdio n8n -- docker run -i --rm -e N8N_API_KEY mcp/n8nRequires: N8N_API_KEY (secret)
vizro-e2e-flow As a Claude Code plugin
/plugin marketplace add mckinsey/vizro
/plugin install vizro-e2e-flow@vizro-marketplaceCommands built only from what the marketplaces declare; the full set for every client is on each card.
Tools each declares
The marketplaces of vizro-e2e-flow publish no list of tools, so we do not compare tools.
Settings each asks for
The marketplaces of vizro-e2e-flow publish no settings it asks for, so we do not compare settings.
What it can do: n8n · What it can do: vizro-e2e-flow · 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.