Kompressr vs Transloadit Media Processing
Kompressr is an MCP server published by kompressr.com. Marketplaces we read that list it: 1 (Official MCP Registry). Transloadit Media Processing is an MCP server published by transloadit. Marketplaces we read that list it: 2 (Official MCP Registry, npm registry (MCP servers)). As of our marketplace pass on 2026-11-10. 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 |  Kompressr |   Transloadit Media Processing |
|---|---|---|
| Official MCP Registry | Listed Version: 2.0.3 Downloads/month (npm): 518 Downloads/week (npm): 288 Forks (GitHub): 0 Stars (GitHub): 0 Not marked · First seen |
Listed Version: 0.8.6 Downloads/month (npm): 9 597 Downloads/week (npm): 2 125 Forks (GitHub): 25 Stars (GitHub): 73 Not marked · First seen |
| npm registry (MCP servers) | Not listed | Listed Version: 0.8.6 Downloads/month (npm): 9 597 Downloads/week (npm): 2 125 Forks (GitHub): 25 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
| Fact | Kompressr | Transloadit Media Processing |
|---|---|---|
| Marketplaces that list it (differs) | 1 (worse) | 2 (better) |
| Stars (GitHub) (differs) | 0 (worse) | 73 (better) |
| Forks (GitHub) (differs) | 0 (worse) | 25 (better) |
| Last release (differs) | 2026-10-24 (worse) | 2026-11-06 (better) |
| Where it runs (differs) | On your machine (@kompressr/mcp-server) | Remote server or your machine |
| Transport (differs) | stdio | Streamable HTTP |
| Tools it declares | Not published | Not published |
| Environment variables it asks for | 2, secrets among them: 1 | 2, secrets among them: 1 |
| Licence (differs) | Not stated | MIT |
| Repository (differs) | github.com/kompressrcdn/clients | github.com/transloadit/node-sdk |
| Changes in the last 7 days (differs) | 0 | 4 |
| First seen (differs) | 2026-10-19 | 2026-10-11 |
| Endpoint at the last check (differs) | no remote endpoint we check | Responded 28 h ago, requires authentication |
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
Kompressr
Upload, optimize and manage files, wait for processing, and generate private delivery links.
Transloadit Media Processing
Process video, audio, images and documents with Transloadit Robots. Connect by URL with OAuth.
How to run each
Kompressr As a local MCP server: npm package
claude mcp add --env "KOMPRESSR_API_KEY=<YOUR_KOMPRESSR_API_KEY>" --transport stdio kompressr -- npx -y @kompressr/mcp-serverRequires: KOMPRESSR_API_KEY (secret)
Transloadit Media Processing As a remote MCP server
claude mcp add --transport http transloadit-media-processing https://api2.transloadit.com/mcpRequires: TRANSLOADIT_KEY, TRANSLOADIT_SECRET (secret)
Commands built only from what the marketplaces declare; the full set for every client is on each card.
Only Transloadit Media Processing has a remote endpoint we check. How we check endpoints
Tools each declares
Neither one's marketplaces publish a list of tools, so there is nothing to compare.
Settings each asks for
Only Kompressr asks for
KOMPRESSR_API_KEY (secret)KOMPRESSR_PROJECT_ID
Only Transloadit Media Processing asks for
TRANSLOADIT_KEYTRANSLOADIT_SECRET (secret)
Settings as each marketplace publishes them. Asking for fewer is not better in itself.
What it can do: Kompressr · What it can do: Transloadit Media Processing · Compare two other plugins
Data comes from the Official MCP Registry (registry.modelcontextprotocol.io), CC0 1.0. Package data comes from the public npm registry (registry.npmjs.org). Figures come from our own regular passes over the marketplaces, last read on . We publish no contact details for plugin publishers.