Ext Ops Panel
Open dashboard
Comparison

Markitdown vs APITemplate.io MCP by usefulapi

Markitdown is an MCP server published by microsoft. Marketplaces we read that list it: 1 (Docker MCP Catalog). APITemplate.io MCP by usefulapi is an MCP server published by usefulapi.io. Marketplaces we read that list it: 1 (Official MCP Registry). 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

Where each is published
MarketplaceMarkitdownAPITemplate.io MCP by usefulapi
Docker MCP Catalog Listed
Version: sha256:9cb5f26d30b6
Forks (GitHub): 14 135
Pulls (Docker Hub): 158 298
Stars (Docker Hub): 5
Stars (GitHub): 190 251
Not marked · First seen
Not listed
Official MCP Registry Not listed Listed
Version: 1.0.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

Markitdown vs APITemplate.io MCP by usefulapi
FactMarkitdownAPITemplate.io MCP by usefulapi
Marketplaces that list it11
Stars (GitHub) (differs)190 251 (better)0 (worse)
Pulls (Docker Hub) (differs)158 298No figure on Docker Hub
Forks (GitHub) (differs)14 135 (better)0 (worse)
Last releaseNot publishedNot published
Where it runs (differs)On your machine (mcp/markitdown)Remote server (apitemplate.usefulapi.io/mcp)
Transport (differs)stdioStreamable HTTP
Tools it declares (differs)1Not published
Environment variables it asks forNot publishedNot published
Licence (differs)MITNot stated
Repository (differs)github.com/microsoft/markitdowngithub.com/m190/usefulapi-mcp
Changes in the last 7 days (differs)02
First seen (differs)2026-10-112026-10-12
Endpoint at the last check (differs)no remote endpoint we checkResponded 2 days ago, requires a key

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

In its own words, on Docker MCP Catalog:

A lightweight MCP server for calling MarkItDown.

APITemplate.io MCP by usefulapi

In its own words, on Official MCP Registry:

Generate PDFs and images with APITemplate.io from templates, HTML, Markdown or a URL.

How to run each

Markitdown As a local MCP server: Docker image

Claude Code
claude mcp add --transport stdio markitdown -- docker run -i --rm mcp/markitdown

APITemplate.io MCP by usefulapi As a remote MCP server

Claude Code
claude mcp add --transport http apitemplate https://apitemplate.usefulapi.io/mcp

Commands built only from what the marketplaces declare; the full set for every client is on each card.

Only APITemplate.io MCP by usefulapi has a remote endpoint we check. How we check endpoints

Tools each declares

The marketplaces of APITemplate.io MCP by usefulapi 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: APITemplate.io MCP by usefulapi · 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.

Where the data comes from: how the catalog is built