Markitdown vs BrewPage
Markitdown is an MCP server published by microsoft. Marketplaces we read that list it: 1 (Docker MCP Catalog). BrewPage is a plugin bundle for AI coding tools published by kochetkov-ma. Marketplaces we read that list it: 1 (Community GitHub marketplaces). As of our marketplace pass on 2026-11-10. 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
| Marketplace |  Markitdown |  BrewPage |
|---|---|---|
| Docker MCP Catalog | Listed Version: sha256:9cb5f26d30b6 Forks (GitHub): 14 681 Pulls (Docker Hub): 169 885 Stars (Docker Hub): 5 Stars (GitHub): 194 704 Not marked · First seen |
Not listed |
| Community marketplace davepoon/buildwithclaude | Not listed | Listed Version: 0.1.0 Forks (GitHub): 0 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
| Fact | Markitdown | BrewPage |
|---|---|---|
| Marketplaces that list it | 1 | 1 |
| Stars (GitHub) (differs) | 194 704 (better) | 0 (worse) |
| Pulls (Docker Hub) (differs) | 169 885 | No figure on Docker Hub |
| Forks (GitHub) (differs) | 14 681 (better) | 0 (worse) |
| Last release | Not published | Not published |
| Where it runs (differs) | On your machine (mcp/markitdown) | Remote server (brewpage.app/mcp) |
| Transport (differs) | stdio | Streamable HTTP |
| Tools it declares (differs) | 1 | Not published |
| Environment variables it asks for | Not published | Not published |
| Parts of the bundle (differs) | Not a bundle | 2 |
| Licence | MIT | MIT |
| Repository (differs) | github.com/microsoft/markitdown | github.com/kochetkov-ma/brewpage-publish-plugins |
| Changes in the last 7 days (differs) | 0 | 2 |
| First seen (differs) | 2026-10-11 | 2026-11-08 |
| Endpoint at the last check (differs) | no remote endpoint we check | Status out of date: last check 33 h ago returned HTTP 405 |
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
A lightweight MCP server for calling MarkItDown.
BrewPage
Publish HTML, Markdown, files and multi-file static sites from Claude Code to BrewPage and get an HTTPS link back, with no account or API key: a brewpage-publish skill plus the BrewPage remote MCP server (https://brewpage.app/mcp). Only content you ask it to publish is uploaded; links are unlisted but readable by anyone who has them (optional password), and content expires (15 days by default, 30 at most).
How to run each
Markitdown As a local MCP server: Docker image
claude mcp add --transport stdio markitdown -- docker run -i --rm mcp/markitdownBrewPage As a Claude Code plugin
/plugin marketplace add davepoon/buildwithclaude
/plugin install brewpage@buildwithclaudeCommands built only from what the marketplaces declare; the full set for every client is on each card.
Only BrewPage has a remote endpoint we check. How we check endpoints
Tools each declares
Only Markitdown has
convert_to_markdown
Only BrewPage has
bind_tokendelete_resourceget_jsonget_kvget_limitsget_pageget_statsmint_tokenpublish_filepublish_htmlpublish_jsonpublish_kv
Show the remaining 8
publish_siterepublish_sitesearch_galleryset_kvset_visibilityupdate_hostingupdate_htmlupdate_json
Both have
None
Tool names as the marketplaces declare them and as Ext Ops observed them on the endpoints (BrewPage as of 2026-11-09). More tools is not better in itself: compare what each needs for the job.
Settings each asks for
Neither one's marketplaces publish the settings it asks for.
What it can do: Markitdown · What it can do: BrewPage · Compare two other plugins
Data comes from the Docker MCP Catalog (desktop.docker.com/mcp/catalog) and Docker Hub. 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.