Filesystem

Is it right for your task?

Use it when

You use an MCP-capable desktop client and repeatedly need to inspect or update a folder of local documents.

Skip it when

You only need to discuss one uploaded document, or your coding assistant already has suitable filesystem tools.

Start simpler

Upload a single document for a one-off question. In Claude Code, start with its existing file tools before adding a second filesystem interface.

Compare two meeting notes without changing them

Example brief. Adapt it to your own test project.

What to expect

With the sample files: launch moves from October 10 to October 12, the pilot shrinks from 20 agents to 10, Mira remains the owner, and accessibility review is still pending. Each statement should cite its source file. This is the answer key for synthetic fixtures, not a recorded MCP test result.

Check the result

• Both filenames appear in the answer and their cited details match the files.
• Missing or contradictory information is stated explicitly.
• The original files remain unchanged.

Before you start

• A local MCP client such as Claude Desktop, or Claude Code with stdio MCP support.
• Node.js and npm for the documented npx setup.
• A dedicated folder containing non-sensitive test files. Use its absolute path, not the example placeholder.

Claude Desktop

Local configuration is documented by the publisher. Not run by this directory.

Claude Code

Supports local stdio MCP servers. This server/client combination has not been executed here.

Claude.ai

This local stdio package is not a hosted connector URL. Do not paste its command into a remote connector field.

Setup and first use

1. Open the publisher setup below. Select its local npx configuration and replace the allowed-directory example with your test folder.
2. Add the configuration using your client's MCP setup flow and restart or reconnect as required. In Claude Code, inspect the connection using /mcp.
3. Ask the client to list the server's allowed directories before reading files. Client-provided roots can replace the command-line directory list.
4. Try the read-only exercise below. Inspect the result before permitting any write, edit, or move operation.

Access, cost, and limits

What access are you granting?

The server can read and write inside allowed directories. Its documented tools include overwrite, edit, and move operations. Directory scope is not a read-only guarantee. Files returned to your AI client enter that client's processing context; local execution does not mean the AI analysis stays local. To stop access, remove or disable the server in your client's MCP configuration and restart/reconnect. This does not undo prior file edits; keep backups.

What does it cost?

The repository is MIT-licensed. Running it locally still requires your computer and a compatible client; Claude plan or API usage costs are separate. No fixed usage price is asserted here.

Limitations to keep in mind

• At least one allowed directory must be supplied through arguments or client roots.
• Roots supplied by a supporting client replace the server-side allowed directory list.
• This directory has not run an installation, tested access boundaries, or audited the package.

If something goes wrong