Ext Ops Panel
Open dashboard
Comparison

Vizro vs SlideForge

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

Where each is published
MarketplaceVizroSlideForge
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: 5.9.0
Downloads/month (PyPI): 227
Downloads/week (PyPI): 48
Forks (GitHub): 1
Stars (GitHub): 4
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 SlideForge
FactVizroSlideForge
Marketplaces that list it11
Stars (GitHub) (differs)3 801 (better)4 (worse)
Pulls (Docker Hub) (differs)37 320No figure on Docker Hub
Forks (GitHub) (differs)304 (better)1 (worse)
Last releaseNot publishedNot published
Where it runs (differs)On your machine (mcp/vizro)Remote server (api.slideforge.dev/mcp)
Transport (differs)stdioStreamable HTTP
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/smartdatabrokers/slideforge-mcp
Changes in the last 7 days00
First seen2026-10-112026-10-11
Endpoint at the last check (differs)no remote endpoint we checkResponded 2 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

In its own words, on Docker MCP Catalog:

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

SlideForge

In its own words, on Official MCP Registry:

Deterministic, fully editable PowerPoint from typed slide intents. 200+ layouts, brand templates.

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

SlideForge As a remote MCP server

Claude Code
claude mcp add --transport http slideforge https://api.slideforge.dev/mcp/

Requires: SLIDEFORGE_API_KEY (secret)

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

Only SlideForge has a remote endpoint we check. How we check endpoints

Tools each declares

The marketplaces of SlideForge 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: SlideForge · 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