com.mcparmory/files-com vs Filelayer
com.mcparmory/files-com is an MCP server published by mcparmory.com. Marketplaces we read that list it: 1 (Official MCP Registry). Filelayer is an MCP server published by filelayer.dev. Marketplaces we read that list it: 1 (Official MCP Registry). As of our marketplace pass on 2026-10-16. 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 |  com.mcparmory/files-com |  Filelayer |
|---|---|---|
| Official MCP Registry | Listed Version: 1.0.3 Downloads/month (PyPI): 799 Downloads/week (PyPI): 180 Forks (GitHub): 4 Stars (GitHub): 32 Not marked · First seen |
Listed Version: 0.33.0 Downloads/month (npm): 6 427 Downloads/week (npm): 3 300 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
| Fact | com.mcparmory/files-com | Filelayer |
|---|---|---|
| Marketplaces that list it | 1 | 1 |
| Stars (GitHub) (differs) | 32 (better) | 0 (worse) |
| Forks (GitHub) (differs) | 4 (better) | 0 (worse) |
| Last release (differs) | Not published | 2026-10-16 |
| Where it runs (differs) | On your machine (mcparmory-files-com) | On your machine (@filelayer/core) |
| Transport | stdio | stdio |
| Tools it declares | Not published | Not published |
| Environment variables it asks for (differs) | Not published | 14, secrets among them: 3 |
| Licence | Not stated | Not stated |
| Repository (differs) | github.com/mcparmory/registry | github.com/filelayer/filelayer |
| Changes in the last 7 days (differs) | 0 | 7 |
| 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
com.mcparmory/files-com
Manage files, users, and automated workflows across cloud storage and protocols
Filelayer
User files for a SaaS, under one person's authority: list, share with an expiry, revoke.
How to run each
com.mcparmory/files-com As a local MCP server: PyPI package
claude mcp add --transport stdio files-com -- uvx mcparmory-files-comFilelayer As a local MCP server: npm package
claude mcp add --env "DATABASE_URL=<YOUR_DATABASE_URL>" --env "FILELAYER_AS=<YOUR_FILELAYER_AS>" --env "FILELAYER_ORG=<YOUR_FILELAYER_ORG>" --env "S3_ACCESS_KEY_ID=<YOUR_S3_ACCESS_KEY_ID>" --env "S3_SECRET_ACCESS_KEY=<YOUR_S3_SECRET_ACCESS_KEY>" --transport stdio core -- npx -y @filelayer/core -p @filelayer/core filelayer-mcpRequires: DATABASE_URL (secret), FILELAYER_AS, FILELAYER_ORG, S3_ACCESS_KEY_ID (secret), S3_SECRET_ACCESS_KEY (secret)
Commands built only from what the marketplaces declare; the full set for every client is on each card.
Tools each declares
Neither one's marketplaces publish a list of tools, so there is nothing to compare.
Settings each asks for
The marketplaces of com.mcparmory/files-com publish no settings it asks for, so we do not compare settings.
What it can do: com.mcparmory/files-com · What it can do: Filelayer · Compare two other plugins
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.