Ext Ops Panel
Open dashboard
Comparison

Vizro vs strategy-frameworks

Vizro is an MCP server published by mckinsey. Marketplaces we read that list it: 1 (Docker MCP Catalog). strategy-frameworks is a plugin bundle for AI coding tools published by ironyjk. Marketplaces we read that list it: 1 (Claude Code: claude-plugins-community). 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
MarketplaceVizrostrategy-frameworks
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
Claude Code: claude-plugins-community Not listed Listed
Version: 0.2.0
Forks (GitHub): 2
Stars (GitHub): 13
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 strategy-frameworks
FactVizrostrategy-frameworks
Marketplaces that list it11
Stars (GitHub) (differs)3 804 (better)13 (worse)
Pulls (Docker Hub) (differs)37 324No figure on Docker Hub
Forks (GitHub) (differs)303 (better)2 (worse)
Last releaseNot publishedNot published
Where it runs (differs)On your machine (mcp/vizro)Installs as a plugin bundle
Transport (differs)stdioNot stated
Tools it declares (differs)6Not published
Environment variables it asks forNot publishedNot published
Parts of the bundle (differs)Not a bundle27
Licence (differs)Apache-2.0MIT
Repository (differs)github.com/mckinsey/vizrogithub.com/ironyjk/strategy-frameworks
Changes in the last 7 days00
First seen (differs)2026-10-112026-10-12

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.

strategy-frameworks

In its own words, on Claude Code: claude-plugins-community:

Strategic Thinking Agent — meta-router for 47 business strategy frameworks (Porter Five Forces, Drucker MBO/5Q, Balanced Scorecard, Blue Ocean, Wardley Mapping, BCG Matrix, BMC, Lean Startup, OKR, Disruptive Innovation, Scenario Planning, Real Options, Game Theory, TRIZ, TOC, and more). Built on Korean business context (SME ecosystem, chaebol dynamics, regulatory environment). Invoke /think to auto-classify problems and select 1–3 optimal frameworks. Includes anti-pattern warnings for each framework.

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

strategy-frameworks As a Claude Code plugin

Claude Code
/plugin marketplace add anthropics/claude-plugins-community
/plugin install strategy-frameworks@claude-community

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

Tools each declares

The marketplaces of strategy-frameworks 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: strategy-frameworks · Compare two other plugins

Data comes from the Docker MCP Catalog (desktop.docker.com/mcp/catalog) and Docker Hub. Data comes from the public marketplace file https://github.com/anthropics/claude-plugins-community/blob/HEAD/.claude-plugin/marketplace.json. 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