The project marks this as version 1.0 with 13 of 30 planned features complete: reading, listing and pattern search work now, and semantic embeddings and vector search are on the roadmap. Take it for what it does today — a sandboxed reader that keeps your files on your machine.
A TypeScript server scoped to one folder. It reads files, searches by glob pattern, lists recursively and reports folder metadata, with path validation that blocks anything resolving outside the folder you named.
- One file read from inside the folder — read_file
- Files found by pattern, such as *.md, config.* or **/*.js — search_files
- Every file listed recursively — list_files
- Folder metadata including the file count — get_folder_info
- A connection check that returns processing information — get_status
- node_modules, .git and .folder-mcp excluded from every operation, and directory traversal blocked
Node.js with npm. Clone the repository, npm install, npm run build, then point your client at dist/mcp-server.js with the folder path as an argument. Configuration lives in config.yaml at the project root — embeddings, cache, chunking and logging. Logging must go to stderr, since anything on stdout breaks the connection.