Ext Ops Panel
Open dashboard
Comparison

Vizro vs io.github.zhugejun/chartone

Vizro is an MCP server published by mckinsey. Marketplaces we read that list it: 1 (Docker MCP Catalog). io.github.zhugejun/chartone is an MCP server published by zhugejun. Marketplaces we read that list it: 1 (Official MCP Registry). 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

Where each is published
MarketplaceVizroio.github.zhugejun/chartone
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.7
Downloads/month (npm): 429
Downloads/week (npm): 260
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

Vizro vs io.github.zhugejun/chartone
FactVizroio.github.zhugejun/chartone
Marketplaces that list it11
Stars (GitHub) (differs)3 804 (better)0 (worse)
Pulls (Docker Hub) (differs)37 324No figure on Docker Hub
Forks (GitHub) (differs)303 (better)0 (worse)
Last releaseNot publishedNot published
Where it runs (differs)On your machine (mcp/vizro)On your machine (@chartone/mcp)
Transportstdiostdio
Tools it declares (differs)6Not published
Environment variables it asks for (differs)Not published1, secrets among them: 1
Licence (differs)Apache-2.0Not stated
Repository (differs)github.com/mckinsey/vizrogithub.com/zhugejun/chartone-mcp
Changes in the last 7 days00
First seen2026-10-112026-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

In its own words, on Docker MCP Catalog:

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

io.github.zhugejun/chartone

In its own words, on Official MCP Registry:

Render themed charts as hosted URLs. Embed in markdown, emails, and Slack. Hosted MCP, zero setup.

How to run each

Vizro As a local MCP server: Docker image

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

io.github.zhugejun/chartone As a local MCP server: npm package

Claude Code
claude mcp add --env "CHARTONE_API_KEY=<YOUR_CHARTONE_API_KEY>" --transport stdio chartone -- npx -y @chartone/mcp

Requires: CHARTONE_API_KEY (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 io.github.zhugejun/chartone 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: io.github.zhugejun/chartone · 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.

Where the data comes from: how the catalog is built