Ext Ops Panel
Open dashboard
Comparison

Markitdown vs html-plan

Markitdown is an MCP server published by microsoft. Marketplaces we read that list it: 1 (Docker MCP Catalog). html-plan is a plugin bundle for AI coding tools published by Thariq Shihipar. Marketplaces we read that list it: 1 (Claude Code: claude-plugins-community). 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
MarketplaceMarkitdownhtml-plan
Docker MCP Catalog Listed
Version: sha256:9cb5f26d30b6
Forks (GitHub): 14 119
Pulls (Docker Hub): 157 340
Stars (Docker Hub): 5
Stars (GitHub): 189 777
Not marked · First seen
Not listed
Claude Code: claude-plugins-community Not listed Listed
Version: 1.0.0
Forks (GitHub): 330
Stars (GitHub): 4 630
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

Markitdown vs html-plan
FactMarkitdownhtml-plan
Marketplaces that list it11
Stars (GitHub) (differs)189 777 (better)4 630 (worse)
Pulls (Docker Hub) (differs)157 340No figure on Docker Hub
Forks (GitHub) (differs)14 119 (better)330 (worse)
Last releaseNot publishedNot published
Where it runs (differs)On your machine (mcp/markitdown)Installs as a plugin bundle
Transport (differs)stdioNot stated
Tools it declares (differs)1Not published
Environment variables it asks forNot publishedNot published
Parts of the bundle (differs)Not a bundle1
LicenceMITMIT
Repository (differs)github.com/microsoft/markitdowngithub.com/anthropics/claude-plugins-community
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

Markitdown

In its own words, on Docker MCP Catalog:

A lightweight MCP server for calling MarkItDown.

html-plan

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

Write an implementation plan as one interactive HTML page: a tree of claims, each proved by a mockup, state machine, call stack, schema or code, with the decisions you need to make placed where they matter. Use /html-plan <what to build>.

How to run each

Markitdown As a local MCP server: Docker image

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

html-plan

No data for an automatic command: what its marketplaces declare does not say unambiguously how to connect it.

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

Tools each declares

The marketplaces of html-plan 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: Markitdown · What it can do: html-plan · 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