Vizro vs LetDraw
Vizro is an MCP server published by mckinsey. Marketplaces we read that list it: 1 (Docker MCP Catalog). LetDraw is an MCP server published by letdraw. Marketplaces we read that list it: 1 (Official MCP Registry). 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 |  Vizro |  LetDraw |
|---|---|---|
| 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 |
| Official MCP Registry | Not listed | Listed Version: 1.0.1 Downloads/month (npm): 516 Downloads/week (npm): 52 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 | LetDraw |
|---|---|---|
| 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) | Remote server (api.letdraw.com/mcp) |
| Transport (differs) | stdio | Streamable HTTP |
| Tools it declares (differs) | 6 | Not published |
| Environment variables it asks for (differs) | Not published | 2, secrets among them: 1 |
| Licence (differs) | Apache-2.0 | Not stated |
| Repository (differs) | github.com/mckinsey/vizro | github.com/letdraw/letdraw-mcp |
| Changes in the last 7 days | 0 | 0 |
| First seen | 2026-10-11 | 2026-10-11 |
| Endpoint at the last check (differs) | no remote endpoint we check | Responded 1 h ago |
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.
LetDraw
Create, edit, share and export hand-drawn LetDraw diagrams, from code or a prompt.
How to run each
Vizro As a local MCP server: Docker image
claude mcp add --transport stdio vizro -- docker run -i --rm mcp/vizroLetDraw As a remote MCP server
claude mcp add --transport http letdraw https://api.letdraw.com/mcp --header "Authorization: Bearer <YOUR_TOKEN>"Requires: LETDRAW_TOKEN (secret), Authorization header
Commands built only from what the marketplaces declare; the full set for every client is on each card.
Only LetDraw has a remote endpoint we check. How we check endpoints
Tools each declares
The marketplaces of LetDraw 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: LetDraw · 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. Figures come from our own regular passes over the marketplaces, last read on . We publish no contact details for plugin publishers.