Markitdown vs iWork Studio
Markitdown is an MCP server published by microsoft. Marketplaces we read that list it: 1 (Docker MCP Catalog). iWork Studio is an MCP server published by Arkanji. Marketplaces we read that list it: 2 (Official MCP Registry, Community GitHub marketplaces). 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 |  iWork Studio |
|---|---|---|
| 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: 2.6.1 Downloads/month (PyPI): 518 Downloads/week (PyPI): 149 Forks (GitHub): 0 Stars (GitHub): 2 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 | iWork Studio |
|---|---|---|
| Marketplaces that list it (differs) | 1 (worse) | 2 (better) |
| Stars (GitHub) (differs) | 189 990 (better) | 2 (worse) |
| Pulls (Docker Hub) (differs) | 157 779 | No figure on Docker Hub |
| Forks (GitHub) (differs) | 14 137 (better) | 0 (worse) |
| Last release (differs) | Not published | 2026-10-14 |
| Where it runs (differs) | On your machine (mcp/markitdown) | On your machine (iwork-studio) |
| Transport | stdio | stdio |
| Tools it declares (differs) | 1 | Not published |
| Environment variables it asks for (differs) | Not published | 2, secrets among them: 0 |
| Parts of the bundle (differs) | Not a bundle | 1 |
| Licence | MIT | MIT |
| Repository (differs) | github.com/microsoft/markitdown | github.com/arkanji/iwork-studio |
| Changes in the last 7 days (differs) | 0 | 4 |
| First seen | 2026-10-11 | 2026-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
Markitdown
A lightweight MCP server for calling MarkItDown.
iWork Studio
Create, edit, design and export Apple Numbers, Keynote and Pages files. Verified and Arabic-safe.
How to run each
Markitdown As a local MCP server: Docker image
claude mcp add --transport stdio markitdown -- docker run -i --rm mcp/markitdowniWork Studio As a local MCP server: PyPI package
claude mcp add --transport stdio iwork-studio -- uvx iwork-studioCommands built only from what the marketplaces declare; the full set for every client is on each card.
Tools each declares
The marketplaces of iWork Studio publish no list of tools, so we do not compare tools.
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: iWork Studio · 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.