Markitdown vs Glif
Markitdown is an MCP server published by microsoft. Marketplaces we read that list it: 1 (Docker MCP Catalog). Glif is an MCP server published by glif.app. Marketplaces we read that list it: 3 (Official MCP Registry, Docker MCP Catalog, 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
| Marketplace |  Markitdown |  Glif |
|---|---|---|
| Docker MCP Catalog | Listed Version: sha256:9cb5f26d30b6 Forks (GitHub): 14 135 Pulls (Docker Hub): 158 529 Stars (Docker Hub): 5 Stars (GitHub): 190 251 Not marked · First seen |
Listed Version: sha256:3f93ddceeb99 Forks (GitHub): 33 Pulls (Docker Hub): 19 662 Stars (Docker Hub): 2 Stars (GitHub): 214 Not marked · First seen |
| Official MCP Registry | Not listed | Listed Version: 1.0.1 Forks (GitHub): 33 Stars (GitHub): 214 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 | Glif |
|---|---|---|
| Marketplaces that list it (differs) | 1 (worse) | 3 (better) |
| Stars (GitHub) (differs) | 190 251 (better) | 214 (worse) |
| Pulls (Docker Hub) (differs) | 158 529 (better) | 19 662 (worse) |
| Forks (GitHub) (differs) | 14 135 (better) | 33 (worse) |
| Last release | Not published | Not published |
| Where it runs (differs) | On your machine (mcp/markitdown) | Remote server or your machine |
| Transport (differs) | stdio | Streamable HTTP, stdio |
| Tools it declares (differs) | 1 | 10 |
| Environment variables it asks for (differs) | Not published | 3, secrets among them: 1 |
| Parts of the bundle (differs) | Not a bundle | 11 |
| Licence | MIT | MIT |
| Repository (differs) | github.com/microsoft/markitdown | github.com/glifxyz/glif-mcp-server |
| Changes in the last 7 days (differs) | 0 | 2 |
| First seen | 2026-10-11 | 2026-10-11 |
| Endpoint at the last check (differs) | no remote endpoint we check | not 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
Markitdown
A lightweight MCP server for calling MarkItDown.
Glif
Generate images, video, and audio with Glif's media-generation agent
How to run each
Markitdown As a local MCP server: Docker image
claude mcp add --transport stdio markitdown -- docker run -i --rm mcp/markitdownGlif As a remote MCP server
claude mcp add --transport http glif https://glif.app/api/mcpCommands built only from what the marketplaces declare; the full set for every client is on each card.
Tools each declares
Only Markitdown declares
convert_to_markdown
Only Glif declares
glif_infolist_featured_glifslist_saved_glif_toolsmy_glif_user_infomy_glifsremove_all_glif_toolsremove_glif_toolrun_glifsave_glif_as_toolsearch_glifs
Both declare
None
Tool names as each marketplace publishes them. More tools is not better in itself: compare what each needs for the job.
Settings each asks for
The marketplaces of Markitdown publish no settings it asks for, so we do not compare settings.
What it can do: Markitdown · What it can do: Glif · 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 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.