Developer · Local MCP server
Virtual Filesystem
PostgreSQL-backed virtual filesystem for agents: session isolation, shared stores, POSIX ops, RLS.
What the MCP Registry states
The entry as published to the official MCP Registry (read 2026-10-04), latest version.
- Registry name
io.github.lu-zhengda/virtual-fs- Version
- 0.2.2
- Status
- Active
- Category
- developer
- Transport
- stdio (local process)
- Package
- npm
- Published
- 2026-02-11
- Updated
- 2026-02-11
- Publisher
- lu-zhengda (GitHub) · 2 servers with pages here
- Namespace
- Namespace verified by the MCP Registry via GitHub (github.com/lu-zhengda) · how
- Listed under
- PostgreSQL MCP servers
- Website
- github.com/lu-zhengda/mcp-virtual-fs#readme
- Repository
- github.com/lu-zhengda/mcp-virtual-fs
- Source
- Registry API entry
Packages
| Registry | Package | Version | Transport |
|---|---|---|---|
| npm | mcp-virtual-fs | 0.2.2 | stdio |
How to connect Virtual Filesystem
Virtual Filesystem runs locally from a Node.js package published to the npm registry: mcp-virtual-fs version 0.2.2. It speaks MCP over stdio, so the client starts it as a program and talks to it through standard input and output. It needs Node.js; clients usually start it with npx - the usual command is npx -y mcp-virtual-fs@0.2.2. It reads these environment variables: DATABASE_URL (required, secret), VFS_AUTO_INIT, VFS_SESSION_ID and VFS_ENABLE_RLS; set them in the client's configuration for this server.
In the mcpServers JSON format that many desktop and editor MCP clients read, the entry looks like this (placeholders in angle brackets):
{
"mcpServers": {
"virtual-fs": {
"command": "npx",
"args": [
"-y",
"mcp-virtual-fs@0.2.2"
],
"env": {
"DATABASE_URL": "<secret>",
"VFS_AUTO_INIT": "<value>",
"VFS_SESSION_ID": "<value>",
"VFS_ENABLE_RLS": "<value>"
}
}
}
}Derived from the registry entry, not tested here. What the server does, and on what terms, is set by its publisher; check its repository or website before giving it access to your accounts or files. How to add an MCP server to an assistant · Before you connect
More from lu-zhengda (GitHub)
| Server | Runs |
|---|---|
| Python Exec SandboxSandboxed Python execution for AI agents. PEP 723 inline deps, multi-version Python, zero pollution. | Local · stdio |
More developer servers
| Server | Runs |
|---|---|
| VigilisGate AI-written tests: heal safe drift, refuse to hide real bugs, sign a verifiable receipt. | Local · stdio |
| Vim MCPConnect Claude Code to Vim/Neovim - query state, execute commands, search help, record macros. | Local · stdio |
| VinktarProduct analytics and error tracking your coding agent can use. | Remote · HTTPLive check: sign-in required |
| VinvVinv runs, tests, and finds issues in your services - with zero code changes. | Local · stdio |
| Visily UI DesignUI design from prompts, screenshots, and URLs for AI coding agents and theme tokens. | Remote · HTTPLive check: sign-in required |
| vivacProvenance tree for coding agents: where you are, why, and what was already decided. | Local · stdio |
| Vivado MCP NativeNative MCP server for controlling AMD/Xilinx Vivado on Windows and Linux via persistent Tcl. | Local · stdio |
| VivereKnow when cron jobs and AI agents stop running: create monitors and check in from your agent. | Remote · HTTPLive check: ✓ handshake |