get_statusLABSCO SUMMARY
Careful file reads today; the semantic layer is still coming.
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.
What it is
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.
What you get
- 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
Requirements
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.
Setup effort
Build from source — git clone https://github.com/okets/folder-mcp.git
USE CASES
01
Letting an assistant read a project without uploading it
The folder is the boundary: paths are validated, traversal is blocked, and nothing leaves the machine.
02
Finding the file you half-remember
Glob patterns narrow a large tree to the handful worth reading, with node_modules and .git already out of the way.
03
Sizing up an unfamiliar directory
Folder metadata and a recursive listing answer how big and how deep before you start opening things.
04
Checking the client actually connected
A status call returns processing information, which is the quickest way to confirm the server is wired up correctly.
5 tools
Listed in project docs. Your client may show a different list.
read_filesearch_fileslist_filesget_folder_infoBEFORE YOU INSTALL
What to know first
Tools you get
5 tools named in the project's documentation.
Where it runs
The documented client runs the server on your machine.
INSTALLATION
Connect your client
Server setup
TERMINAL
git clone https://github.com/okets/folder-mcp.git
cd folder-mcp
npm install
npm run buildMCP Clients
Claude Desktop
CLAUDE DESKTOP · JSON
{
"mcpServers": {
"folder-mcp": {
"command": "node",
"args": [
"<YOUR_PATH_TO_FOLDER_MCP>\\dist\\mcp-server.js",
"<YOUR_PATH_TO_FOLDER_MCP>"
],
"env": {}
}
}
}
