Ext Ops Panel
Open dashboard
Comparison

html-to-markdown vs Firecrawl MCP Server

html-to-markdown is a plugin bundle for AI coding tools published by Kreuzberg, Inc.. Marketplaces we read that list it: 1 (Community GitHub marketplaces). Firecrawl MCP Server is an MCP server published by firecrawl. Marketplaces we read that list it: 3 (Official MCP Registry, Docker MCP Catalog, Community GitHub marketplaces). As of our marketplace pass on 2026-11-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
Marketplacehtml-to-markdownFirecrawl MCP Server
Community marketplace xberg-io/html-to-markdown Listed
Version: 3.22.1
Forks (GitHub): 76
Stars (GitHub): 887
Not marked · First seen
Not listed
Official MCP Registry Not listed Listed
Version: 3.40.0
Downloads/month (npm): 517 013
Downloads/week (npm): 158 613
Forks (GitHub): 930
Stars (GitHub): 7 813
Not marked · First seen
Docker MCP Catalog Not listed Listed
Version: sha256:3b22a74af198
Forks (GitHub): 930
Pulls (Docker Hub): 151 195
Stars (Docker Hub): 20
Stars (GitHub): 7 813
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

html-to-markdown vs Firecrawl MCP Server
Facthtml-to-markdownFirecrawl MCP Server
Marketplaces that list it (differs)1 (worse)3 (better)
Stars (GitHub) (differs)887 (worse)7 813 (better)
Pulls (Docker Hub) (differs)No figure on Docker Hub151 195
Forks (GitHub) (differs)76 (worse)930 (better)
Last release (differs)2026-11-13 (better)2026-11-12 (worse)
Where it runs (differs)Installs as a plugin bundleRemote server or your machine
Transport (differs)Not statedStreamable HTTP, stdio
Tools it declares (differs)Not published28
Environment variables it asks for (differs)Not published2, secrets among them: 1
Parts of the bundle (differs)918
LicenceMITMIT
Repository (differs)github.com/xberg-io/html-to-markdowngithub.com/firecrawl/firecrawl-mcp-server
Changes in the last 7 days (differs)32
First seen (differs)2026-11-112026-10-11
Endpoint at the last check (differs)no remote endpoint we checkResponded 21 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

html-to-markdown

In its own words, on Community GitHub marketplaces:

Fast, lossless HTML→Markdown conversion with structured metadata, tables, and document-structure extraction.

Firecrawl MCP Server

In its own words, on Official MCP Registry:

Firecrawl, the context API for AI agents: search, scrape, interact with the web, plus paper search.

How to run each

html-to-markdown As a Claude Code plugin

Claude Code
/plugin marketplace add xberg-io/html-to-markdown
/plugin install html-to-markdown@html-to-markdown

Firecrawl MCP Server As a remote MCP server

Claude Code
claude mcp add --transport http firecrawl-mcp-server https://mcp.firecrawl.dev/v2/mcp --header "Authorization: Bearer <YOUR_TOKEN>"

Requires: FIRECRAWL_API_KEY (secret), Authorization header

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

Only Firecrawl MCP Server has a remote endpoint we check. How we check endpoints

Tools each declares

The marketplaces of html-to-markdown publish no list of tools, so we do not compare tools.

Settings each asks for

The marketplaces of html-to-markdown publish no settings it asks for, so we do not compare settings.

What it can do: html-to-markdown · What it can do: Firecrawl MCP Server · Compare two other plugins

Data comes from public marketplace files in GitHub repositories of their authors. Data comes from the Official MCP Registry (registry.modelcontextprotocol.io), CC0 1.0. 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 . We publish no contact details for plugin publishers.

Where the data comes from: how the catalog is built