Ext Ops Panel
Open dashboard
Comparison

Markdownify vs One MCP, many parsers

Markdownify is an MCP server published by zcaceres. Marketplaces we read that list it: 1 (Docker MCP Catalog). One MCP, many parsers is an MCP server published by adelaidasofia. Marketplaces we read that list it: 3 (Official MCP Registry, Claude Code: claude-plugins-community, Community GitHub marketplaces). As of our marketplace pass on 2026-10-15. 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
MarketplaceMarkdownifyOne MCP, many parsers
Docker MCP Catalog Listed
Version: sha256:afa1ab8e1563
Forks (GitHub): 255
Pulls (Docker Hub): 72 666
Stars (Docker Hub): 2
Stars (GitHub): 2 997
Not marked · First seen
Not listed
Official MCP Registry Not listed Listed
Version: 0.1.0
Forks (GitHub): 1
Stars (GitHub): 0
Not marked · First seen
Claude Code: claude-plugins-community Not listed Listed
Version: 0.1.0
Forks (GitHub): 1
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

Markdownify vs One MCP, many parsers
FactMarkdownifyOne MCP, many parsers
Marketplaces that list it (differs)1 (worse)3 (better)
Stars (GitHub) (differs)2 997 (better)0 (worse)
Pulls (Docker Hub) (differs)72 666No figure on Docker Hub
Forks (GitHub) (differs)255 (better)1 (worse)
Last releaseNot publishedNot published
Where it runs (differs)On your machine (mcp/markdownify)On your machine (https://github.com/adelaidasofia/parse-mcp/releases/download/v0.1.0/parse-mcp.mcpb)
Transportstdiostdio
Tools it declares (differs)11Not published
Environment variables it asks for (differs)Not published1, secrets among them: 1
Hooks it runs (differs)Not published1
Parts of the bundle (differs)Not a bundle2
Licence (differs)MITNot stated
Repository (differs)github.com/zcaceres/markdownify-mcpgithub.com/adelaidasofia/parse-mcp
Changes in the last 7 days (differs)02
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

Markdownify

In its own words, on Docker MCP Catalog:

A Model Context Protocol server for converting almost anything to Markdown.

One MCP, many parsers

In its own words, on Official MCP Registry:

One MCP, many parsers. Routes between markitdown, Docling, and LlamaParse. Plus an interpret tool…

How to run each

Markdownify As a local MCP server: Docker image

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

One MCP, many parsers As a Claude Code plugin

Claude Code
/plugin marketplace add anthropics/claude-plugins-community
/plugin install parse-mcp@claude-community

Requires: LLAMAPARSE_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 One MCP, many parsers publish no list of tools, so we do not compare tools.

Settings each asks for

The marketplaces of Markdownify publish no settings it asks for, so we do not compare settings.

What it can do: Markdownify · What it can do: One MCP, many parsers · 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. Data comes from the public marketplace file https://github.com/anthropics/claude-plugins-community/blob/HEAD/.claude-plugin/marketplace.json. Data comes from public marketplace files in GitHub repositories of their authors. 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