mcp-virtual-fs

Virtual Fs MCP Server

mcp-virtual-fs gives AI agents a PostgreSQL-backed workspace for persistent files without using the host filesystem. It supports isolated session data, shared named stores, and tools for editing, organizing, and searching files.

Server facts

mcp-virtual-fs

Tech

Runtime / language
node
Transports
stdio
Remote available
No
Authentication
Not specified

Activity

GitHub stars
3
Last commit
Data as of

Tags

  • Filesystem
  • Postgresql
  • agent memory
  • rls
  • session isolation
  • storage
  • virtual fs

Overview

Agent notes, accumulated context, and build artifacts can live in PostgreSQL rather than alongside an agent process. mcp-virtual-fs exposes file operations through MCP, allowing agents to read, replace, or append content; inspect paths; organize directories; and move or delete files. Writes create missing parent directories, while appends can start a new file. For retrieval, glob locates files by path pattern, and grep returns matching content lines with their paths and line numbers, optionally narrowing the search by a path pattern. Tool results use structured JSON.

Session namespaces separate each agent's working files by default. For information that needs to cross session boundaries, agents can select a named store on file operations and discover existing stores with the stores tool. This supports shared project notes, longer-lived agent memory, and collaboration between agents. A configured session identifier also allows an earlier workspace to be resumed. Deployment uses Node.js and PostgreSQL, with optional automatic table creation and optional database-level session isolation through Row Level Security.

mcp-virtual-fs setup notes

  • mcp-virtual-fs records stdio only; confirm a network transport upstream before planning remote access.

Related MCP servers