Markitdown vs TweekIT MCP Server
Markitdown is an MCP server published by microsoft. Marketplaces we read that list it: 1 (Docker MCP Catalog). TweekIT MCP Server is an MCP server published by equilibrium-team. Marketplaces we read that list it: 1 (Official MCP Registry). As of our marketplace pass on 2026-10-14. 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 |  TweekIT MCP Server |
|---|---|---|
| Docker MCP Catalog | Listed Version: sha256:9cb5f26d30b6 Forks (GitHub): 14 137 Pulls (Docker Hub): 157 779 Stars (Docker Hub): 5 Stars (GitHub): 189 990 Not marked · First seen |
Not listed |
| Official MCP Registry | Not listed | Listed Version: 1.6.1 Forks (GitHub): 1 Stars (GitHub): 1 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 | TweekIT MCP Server |
|---|---|---|
| Marketplaces that list it | 1 | 1 |
| Stars (GitHub) (differs) | 189 990 (better) | 1 (worse) |
| Pulls (Docker Hub) (differs) | 157 779 | No figure on Docker Hub |
| Forks (GitHub) (differs) | 14 137 (better) | 1 (worse) |
| Last release | Not published | Not published |
| Where it runs (differs) | On your machine (mcp/markitdown) | Remote server (mcp.tweekit.io/mcp) |
| Transport (differs) | stdio | Streamable HTTP |
| Tools it declares (differs) | 1 | Not published |
| Environment variables it asks for | Not published | Not published |
| Licence (differs) | MIT | Not stated |
| Repository (differs) | github.com/microsoft/markitdown | github.com/equilibrium-team/tweekit-mcp |
| Changes in the last 7 days | 0 | 0 |
| First seen | 2026-10-11 | 2026-10-11 |
| Endpoint at the last check (differs) | no remote endpoint we check | Answered with HTTP 307 (10 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
Markitdown
A lightweight MCP server for calling MarkItDown.
TweekIT MCP Server
Normalize and convert more than 400 file types via TweekIT's hosted MCP streamable HTTP endpoint.
How to run each
Markitdown As a local MCP server: Docker image
claude mcp add --transport stdio markitdown -- docker run -i --rm mcp/markitdownTweekIT MCP Server As a remote MCP server
claude mcp add --transport http tweekit https://mcp.tweekit.io/mcp --header "ApiKey: <YOUR_APIKEY>" --header "ApiSecret: <YOUR_APISECRET>"Requires: ApiKey header, ApiSecret header
Commands built only from what the marketplaces declare; the full set for every client is on each card.
Only TweekIT MCP Server has a remote endpoint we check. How we check endpoints
Tools each declares
The marketplaces of TweekIT MCP Server 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: Markitdown · What it can do: TweekIT MCP Server · 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. Figures come from our own regular passes over the marketplaces, last read on . We publish no contact details for plugin publishers.