Comparison

AWS Diagram vs Vizro

AWS Diagram is an MCP server published by awslabs. Marketplaces we read that list it: 1 (Docker MCP Catalog). Vizro is an MCP server published by mckinsey. Marketplaces we read that list it: 1 (Docker MCP Catalog). 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

Where each is published
Marketplace	AWS Diagram	Vizro
Docker MCP Catalog	Listed Version: sha256:453d5fc6b50b Forks (GitHub): 1 805 Pulls (Docker Hub): 60 602 Stars (Docker Hub): 1 Stars (GitHub): 9 776 Not marked · First seen 2026-10-11	Listed Version: sha256:ddec90039ea1 Forks (GitHub): 303 Pulls (Docker Hub): 37 320 Stars (Docker Hub): 1 Stars (GitHub): 3 804 Not marked · First seen 2026-10-11

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

AWS Diagram vs Vizro
Fact	AWS Diagram	Vizro
Marketplaces that list it	1	1
Stars (GitHub) (differs)	9 776 (better)	3 804 (worse)
Pulls (Docker Hub) (differs)	60 602 (better)	37 320 (worse)
Forks (GitHub) (differs)	1 805 (better)	303 (worse)
Last release	Not published	Not published
Where it runs (differs)	On your machine (mcp/aws-diagram)	On your machine (mcp/vizro)
Transport	stdio	stdio
Tools it declares (differs)	3	6
Environment variables it asks for	Not published	Not published
Licence	Apache-2.0	Apache-2.0
Repository (differs)	github.com/awslabs/mcp	github.com/mckinsey/vizro
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

AWS Diagram

In its own words, on Docker MCP Catalog:

Seamlessly create diagrams using the Python diagrams package DSL. This server allows you to generate AWS diagrams, sequence diagrams, flow diagrams, and class diagrams using Python code.

Vizro

In its own words, on Docker MCP Catalog:

provides tools and templates to create a functioning Vizro chart or dashboard step by step.

How to run each

AWS Diagram As a local MCP server: Docker image

Claude Code

claude mcp add --transport stdio aws-diagram -- docker run -i --rm mcp/aws-diagram

Vizro As a local MCP server: Docker image

Claude Code

claude mcp add --transport stdio vizro -- docker run -i --rm mcp/vizro

Commands built only from what the marketplaces declare; the full set for every client is on each card.

Tools each declares

Only AWS Diagram declares

generate_diagram
get_diagram_examples
list_icons

Only Vizro declares

get_model_json_schema
get_sample_data_info
get_vizro_chart_or_dashboard_plan
load_and_analyze_data
validate_chart_code
validate_dashboard_config

Both declare

None

Tool names as each marketplace publishes them. More tools is not better in itself: compare what each needs for the job.

Settings each asks for

Neither one's marketplaces publish the settings it asks for.

What it can do: AWS Diagram · What it can do: Vizro · Compare two other plugins

Data comes from the Docker MCP Catalog (desktop.docker.com/mcp/catalog) and Docker Hub. Figures come from our own regular passes over the marketplaces, last read on 2026-10-13. We publish no contact details for plugin publishers.