Ext Ops Panel
Open dashboard
Comparison

Markdownify vs TinyFish

Markdownify is an MCP server published by zcaceres. Marketplaces we read that list it: 1 (Docker MCP Catalog). TinyFish is a plugin bundle for AI coding tools published by tinyfish-io. Marketplaces we read that list it: 2 (Claude: knowledge-work-plugins, Claude Code: claude-plugins-community). As of our marketplace pass on 2026-10-12. 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
MarketplaceMarkdownifyTinyFish
Docker MCP Catalog Listed
Version: sha256:afa1ab8e1563
Forks (GitHub): 254
Pulls (Docker Hub): 72 417
Stars (Docker Hub): 2
Stars (GitHub): 3 001
Not marked · First seen
Not listed
Claude: knowledge-work-plugins Not listed Listed
Version: 1.3.1
Forks (GitHub): 8
Stars (GitHub): 20
Not marked · First seen
Claude Code: claude-plugins-community Not listed Listed
Version: 1.1.0
No figure published
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 TinyFish
FactMarkdownifyTinyFish
Marketplaces that list it (differs)1 (worse)2 (better)
Stars (GitHub) (differs)3 001 (better)20 (worse)
Pulls (Docker Hub) (differs)72 417No figure on Docker Hub
Forks (GitHub) (differs)254 (better)8 (worse)
Last releaseNot publishedNot published
Where it runs (differs)On your machine (mcp/markdownify)Remote server (agent.tinyfish.ai/mcp)
Transport (differs)stdioStreamable HTTP
Tools it declares (differs)11Not published
Environment variables it asks forNot publishedNot published
Parts of the bundle (differs)Not a bundle6
LicenceMITMIT
Repository (differs)github.com/zcaceres/markdownify-mcpgithub.com/tinyfish-io/tinyfish-web-agent-integrations
Changes in the last 7 days00
First seen2026-10-112026-10-11
Endpoint at the last check (differs)no remote endpoint we checknot checked yet

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.

TinyFish

In its own words, on Claude: knowledge-work-plugins:

The complete web toolkit for your agent. Search the web and get answers in milliseconds. Fetch any URL and get clean markdown content back. Send a browser agent to navigate sites, fill forms, and extract structured data. Spin up a headless browser for full programmatic control when you need it.

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

TinyFish

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 TinyFish 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: Markdownify · What it can do: TinyFish · 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/knowledge-work-plugins/blob/HEAD/.claude-plugin/marketplace.json. 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