Virtual Fs vs Filestash
A side-by-side look at the Virtual Fs and Filestash MCP servers: transport, auth, tools, quality signals, and the config to install either one in Claude, Cursor, Windsurf or VS Code.
Verdict: choose Virtual Fs for file systems work as a local process; choose Filestash for file systems over a hosted endpoint. You can also run both side by side in one mcpServers block.
Which MCP server should you choose?
Choose Virtual Fs when
- You need dedicated capabilities in the File Systems domain.
- You prefer a local stdio subprocess transport.
- You have the keys it needs:
DATABASE_URL. - You want tools like
read, write, append.
Choose Filestash when
- You need dedicated capabilities in the File Systems domain.
- You prefer a remote HTTP/SSE transport.
- Its auth model fits you: No auth required.
Feature & specification comparison
Rows where the two servers differ are marked.
| Spec | ||
|---|---|---|
| Category | File Systems | File Systems |
| Quality signal | 51/100 · Good | 51/100 · Good |
| Install command | Confirmed | Confirmed |
| Transport | Local subprocess (stdio) | Remote HTTP/SSE |
| Auth | Not declared | No auth required |
| Pricing | Not declared | Free |
| Required env vars | DATABASE_URL | None listed |
| Verified owner | Community listing | Community listing |
| GitHub stars | 3 | 14,825 |
| Directory activity | 1 views 0 installs 0 upvotes | 3 views 0 installs 0 upvotes |
| Tools | 11 | Not listed |
| Full listing | View Virtual Fs | View Filestash |
Tools & capabilities
Virtual Fs tools 11
readRead file contentswriteWrite file (creates parents automatically)appendAppend to file (creates if missing)statCheck existence and get metadatalsList directory (dirs first, then alphabetical)mkdirCreate directory and parents (mkdir -p)rmRemove file or directory recursivelymvMove/rename file or directoryglobFind files by glob (e.g., `**/*.ts`, `**/*.{js,ts}`)grepSearch file contents by regexstoresList all persistent store names
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.
Virtual Fs
{
"mcpServers": {
"virtual-fs": {
"command": "npx",
"args": [
"-y",
"mcp-virtual-fs"
],
"env": {
"DATABASE_URL": "YOUR_DATABASE_URL_HERE"
}
}
}
}
Filestash
{
"mcpServers": {
"mickaelkerjean-filestash": {
"url": "https://demo.filestash.app/sse"
}
}
}
Frequently asked questions
Virtual Fs is categorized under File Systems and uses a local stdio subprocess. Filestash belongs to File Systems and uses a remote HTTP/SSE transport. Pick Virtual Fs 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.
Virtual Fs 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 virtual-fs and mickaelkerjean-filestash as separate keys in the same mcpServers object, and your assistant will call tools from either one.
On AllMCPs, Virtual Fs has a quality signal of 51/100 (Good) with 1 views, 0 installs and 3 GitHub stars. Filestash has 51/100 (Good) with 3 views, 0 installs and 14,825 GitHub stars.
