Filesystem vs Filestash

A side-by-side look at the Filesystem and Filestash MCP servers: transport, auth, tools, quality signals, and the config to install either one in Claude, Cursor, Windsurf or VS Code.

Filesystem logoFilesystemFile Systems · Local subprocess (stdio)MCP server for filesystem operations - read, create, and edit files52GoodAuth: not declaredFilestash logoFilestashFile SystemsRemote Storage Access: SFTP, S3, FTP, SMB, NFS, WebDAV, GIT, FTPS, gcloud, azure blob, sharepoint, etc.44FairAuth: no auth required

Verdict: choose Filesystem for file systems work as a local process; choose Filestash for file systems. You can also run both side by side in one mcpServers block.

Which MCP server should you choose?

Filesystem logoChoose Filesystem when

  • You need dedicated capabilities in the File Systems domain.
  • You prefer a local stdio subprocess transport.
  • You want tools like view, create, str_replace.
Explore Filesystem

Filestash logoChoose Filestash when

  • You need dedicated capabilities in the File Systems domain.
  • Its auth model fits you: No auth required.
Explore Filestash

Feature & specification comparison

Rows where the two servers differ are marked.

SpecFilesystem logoFilesystemFilestash logoFilestash
CategoryFile SystemsFile Systems
Quality signal52/100 · Good44/100 · Fair
Install commandConfirmedNot confirmed yet
TransportLocal subprocess (stdio)—
AuthNot declaredNo auth required
PricingNot declaredFree
Required env varsNone listedNone listed
Verified ownerCommunity listingCommunity listing
GitHub stars314,817
Directory activity 2 views 0 installs 0 upvotes 3 views 0 installs 0 upvotes
Tools4Not listed

Tools & capabilities

Filesystem tools 4

  • viewRead file contents or list directory (with line numbers)
  • createCreate or overwrite a file
  • str_replaceReplace an exact string in a file
  • insertInsert text at a specific line

Filestash tools

No tool names declared yet. Check the project README from the listing page.

Ready-to-paste client configs

Paste either block (or both) into your client config, e.g. claude_desktop_config.json or ~/.cursor/mcp.json. We only show a config when the install command is confirmed.

Filesystem

mcpServers (Claude Desktop / Cursor)
{
  "mcpServers": {
    "filesystem-2": {
      "command": "npx",
      "args": [
        "-y",
        "filesystem-mcp"
      ]
    }
  }
}

Filestash

No confirmed install command for Filestash yet — follow the setup steps linked from its listing page rather than a guessed package name.

Frequently asked questions

Filesystem is categorized under File Systems and uses a local stdio subprocess. Filestash belongs to File Systems and uses an install path we have not confirmed yet. Pick Filesystem for file systems work and Filestash for file systems.

Copy the mcpServers block from the config section on this page into your client's config (for example claude_desktop_config.json or ~/.cursor/mcp.json), then fully restart the client. Filestash has no confirmed install command yet — follow its own setup instructions.

Filesystem has no declared pricing — check the project's own site. Filestash is listed as free. Auth: no auth required. If a server needs environment variables such as API keys, define them under the env key in your client's MCP config.

Yes. MCP clients support multiple servers: add filesystem-2 and mickaelkerjean-filestash as separate keys in the same mcpServers object, and your assistant will call tools from either one.

On AllMCPs, Filesystem has a quality signal of 52/100 (Good) with 2 views, 0 installs and 3 GitHub stars. Filestash has 44/100 (Fair) with 3 views, 0 installs and 14,817 GitHub stars.