Ext Ops Panel
Open dashboard
Comparison

MemoFS MCP Server vs Files

MemoFS MCP Server is an MCP server published by memofs.dev. Marketplaces we read that list it: 1 (Official MCP Registry). Files is an MCP server published by Abhishekkumar2021. Marketplaces we read that list it: 1 (Official MCP Registry). As of our marketplace pass on 2026-10-19. 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
MarketplaceMemoFS MCP ServerFiles
Official MCP Registry Listed
Version: 1.3.0-beta.3
Downloads/month (npm): 269
Downloads/week (npm): 66
Forks (GitHub): 2
Stars (GitHub): 6
Not marked · First seen
Listed
Version: 0.2.0
Downloads/month (npm): 197
Downloads/week (npm): 28
Forks (GitHub): 0
Stars (GitHub): 1
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

MemoFS MCP Server vs Files
FactMemoFS MCP ServerFiles
Marketplaces that list it11
Stars (GitHub) (differs)6 (better)1 (worse)
Forks (GitHub) (differs)2 (better)0 (worse)
Last releaseNot publishedNot published
Where it runs (differs)Remote server (memofs.dev/api/v1/projects/%7BprojectId%7D/mcp)On your machine (@abhishekmcp/files)
Transport (differs)Streamable HTTPstdio
Tools it declaresNot publishedNot published
Environment variables it asks for (differs)2, secrets among them: 12, secrets among them: 0
Licence (differs)Not statedMIT
Repository (differs)github.com/memo-fs/memofsgithub.com/abhishekkumar2021/mcp-suite
Changes in the last 7 days (differs)02
First seen2026-10-112026-10-11
Endpoint at the last check (differs)Responded 46 h agono remote endpoint we check

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

MemoFS MCP Server

In its own words, on Official MCP Registry:

Persistent memory and virtual filesystem MCP server for AI agents.

Files

In its own words, on Official MCP Registry:

Sandboxed local filesystem: read, search, edit, copy, archive, and safely manage files.

How to run each

MemoFS MCP Server

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

Requires: MEMOFS_API_KEY (secret), Authorization header

Files As a local MCP server: npm package

Claude Code
claude mcp add --env "FS_ROOTS=<YOUR_FS_ROOTS>" --transport stdio files -- npx -y @abhishekmcp/files

Requires: FS_ROOTS

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

Only MemoFS MCP Server 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 MemoFS MCP Server asks for

  • MEMOFS_API_KEY (secret)
  • MEMOFS_RUNTIME

Only Files asks for

  • FS_READONLY
  • FS_ROOTS

Settings as each marketplace publishes them. Asking for fewer is not better in itself.

What it can do: MemoFS MCP Server · What it can do: Files · Compare two other plugins

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.

Where the data comes from: how the catalog is built