Ext Ops Panel
Open dashboard
Comparison

Filesystem (Reference) vs Transloadit Media Processing

Filesystem (Reference) is an MCP server published by modelcontextprotocol. Marketplaces we read that list it: 1 (Docker MCP Catalog). Transloadit Media Processing is an MCP server published by transloadit. Marketplaces we read that list it: 1 (Official MCP Registry). As of our marketplace pass on 2026-10-12. 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
MarketplaceFilesystem (Reference)Transloadit Media Processing
Docker MCP Catalog Listed
Version: sha256:35fcf0217ca0
Forks (GitHub): 11 778
Pulls (Docker Hub): 287 528
Stars (Docker Hub): 28
Stars (GitHub): 91 146
Not marked · First seen
Not listed
Official MCP Registry Not listed Listed
Version: 0.3.9
Forks (GitHub): 26
Stars (GitHub): 73
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

Filesystem (Reference) vs Transloadit Media Processing
FactFilesystem (Reference)Transloadit Media Processing
Marketplaces that list it11
Stars (GitHub) (differs)91 146 (better)73 (worse)
Pulls (Docker Hub) (differs)287 528No figure on Docker Hub
Forks (GitHub) (differs)11 778 (better)26 (worse)
Last releaseNot publishedNot published
Where it runs (differs)On your machine (mcp/filesystem)Remote server (api2.transloadit.com/mcp)
Transport (differs)stdioStreamable HTTP
Tools it declares (differs)11Not published
Environment variables it asks for (differs)Not published2, secrets among them: 1
Licence (differs)NOASSERTIONNot stated
Repository (differs)github.com/modelcontextprotocol/serversgithub.com/transloadit/node-sdk
Changes in the last 7 days00
First seen2026-10-112026-10-11
Endpoint at the last check (differs)no remote endpoint we checknot 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

Filesystem (Reference)

In its own words, on Docker MCP Catalog:

Local filesystem access with configurable allowed paths.

Transloadit Media Processing

In its own words, on Official MCP Registry:

Process video, audio, images, and documents with 86+ cloud media processing robots.

How to run each

Filesystem (Reference) As a local MCP server: Docker image

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

Transloadit Media Processing

No data for an automatic command: what its marketplaces declare does not say unambiguously how to connect it.

Requires: TRANSLOADIT_KEY, TRANSLOADIT_SECRET (secret)

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

Tools each declares

The marketplaces of Transloadit Media Processing publish no list of tools, so we do not compare tools.

Settings each asks for

The marketplaces of Filesystem (Reference) publish no settings it asks for, so we do not compare settings.

What it can do: Filesystem (Reference) · What it can do: Transloadit Media Processing · 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