Vizro vs archify
archify is no longer listed on any marketplace we read: these are its last known data, as of 2026‑10‑16.
Vizro is an MCP server published by mckinsey. Marketplaces we read that list it: 1 (Docker MCP Catalog). archify is a plugin bundle for AI coding tools published by iowarp. No marketplace we read lists it any more. As of our marketplace pass on 2026-10-19. A plugin in this pair is no longer listed on any marketplace we read, so search engines are asked not to index the page.
Where each is published
| Marketplace |  Vizro | |
|---|---|---|
| Docker MCP Catalog | Listed Version: sha256:ddec90039ea1 Forks (GitHub): 305 Pulls (Docker Hub): 37 393 Stars (Docker Hub): 1 Stars (GitHub): 3 810 Not marked · First seen |
Not listed |
| Community marketplace iowarp/clio-kit | Not listed | Removed on 2026-10-16 Version: 0.1.0 Forks (GitHub): 5 Stars (GitHub): 8 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 | archifyno longer listed · |
|---|---|---|
| Marketplaces that list it (differs) | 1 | 0 |
| Stars (GitHub) (differs) | 3 810 | 8 |
| Pulls (Docker Hub) (differs) | 37 393 | No figure on Docker Hub |
| Forks (GitHub) (differs) | 305 | 5 |
| 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 |
| Licence (differs) | Apache-2.0 | MIT |
| Repository (differs) | github.com/mckinsey/vizro | github.com/iowarp/clio-coder |
| Changes in the last 7 days (differs) | 0 | 4 |
| First seen (differs) | 2026-10-11 | 2026-10-13 |
Lines where the two differ have a tinted background and bold values. No value is marked better or worse: a plugin no marketplace lists any more is shown with its last known data, which we do not rank against current figures.
What to use instead of archify
Plugins still listed whose own names, descriptions, tools and skills are closest in meaning to it. Comparable, not endorsed.
-
flowzap io.github.flowzap-xyz/flowzap
Create workflow, sequence, architecture, and mind map diagrams via AI assistants.
-
Create and edit architecture diagrams from your AI agent; get an SVG and a live editable canvas.
-
A Claude Code plugin to create custom JointJS-powered interactive playgrounds. It enables you to build code maps for library/codebase architectures, data explorers for database…
-
Mermaid to assets. Source code to maps. MCP for agents.
-
drawarch io.github.Ajey95/drawarch
Create editable Draw.io architecture diagrams from prompts and reference images.
-
Create and update live animated architecture diagrams on CloudArch from a prompt or script.
What each says it does
Vizro
provides tools and templates to create a functioning Vizro chart or dashboard step by step.
archify
Validated interactive system maps and diagrams as standalone HTML from a typed JSON spec, for one of five diagram types (architecture, workflow, sequence, dataflow, lifecycle). Use when the user asks to visualize architecture, a workflow, a call sequence, a data pipeline, or a state machine, or to map this repository. Not for ad hoc drawings or slide art, and not for Mermaid output; use the artifact tool for plain Markdown.
How to run each
Vizro As a local MCP server: Docker image
claude mcp add --transport stdio vizro -- docker run -i --rm mcp/vizroarchify
No data for an automatic command: what its marketplaces declare does not say unambiguously how to connect it.
Commands built only from what the marketplaces declare; the full set for every client is on each card.
Tools each declares
The marketplaces of archify 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: archify · 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.