Local automation
Filesystem
Controlled local file access for assistants running in a developer workspace.
Deep ReviewMCP Rank ReviewedHigh confidencemedium riskclaudecursorcodexVS Code
Score breakdown
Install + docs88
Maintenance84
Auth handling72
Client compatibility93
Real usefulness91
Safety signals73
Evidence history
Review snapshots show why the current score, confidence, and risk labels changed over time.
| Date | Change | Score | Confidence | Risk |
|---|---|---|---|---|
| May 14, 2026 | Initial MCP Rank review captured from the curated seed dataset. The server is easy to install and widely referenced in MCP client setup examples. seed snapshot · reviewed | 84 | high | medium |
Evidence notes
The server is easy to install and widely referenced in MCP client setup examples.
Its utility is extremely high for coding agents, document workflows, and local project inspection.
Safety depends almost entirely on directory allowlists and whether sensitive folders are exposed.
A restricted project-root configuration is materially different from broad home-directory access.
High confidence comes from reference-server provenance and repeatable local configuration review.
Best-fit use cases
Best for developer workspaces where agents need project-local files.
Useful for documentation teams reviewing generated artifacts.
Not a good fit for unmanaged employee machines without a clear allowlist policy.
Risk analysis
Local file access can leak secrets through prompt context if the exposed root is too broad.
Workspace scoping and explicit approvals reduce risk more than any score label can.
Risk increases when paired with write tools or autonomous agents.
Use-case examples
Read a project README before editing.
List generated artifacts after a build.
Inspect config files inside a scoped repository.