{"id":"acuvity-mcp-server-filesystem","name":"mcp-server-filesystem","af_score":42.8,"security_score":35.0,"reliability_score":27.5,"what_it_does":"MCP server that exposes a filesystem interface to an AI agent, enabling read/write (and possibly directory listing/search) operations through MCP tools, based on a server-side configuration of allowed paths/permissions.","best_when":"Used inside a trusted environment (local dev machine, CI runner, or tightly sandboxed container) with explicit allowlists for filesystem paths.","avoid_when":"Avoid when you cannot strictly constrain accessible directories/files, or when the MCP server could be reachable by untrusted users/agents.","last_evaluated":"2026-04-04T19:48:40.328826+00:00","has_mcp":true,"has_api":false,"auth_methods":["None documented / local auth typical for MCP servers (not confirmed)"],"has_free_tier":false,"known_gotchas":["Agents may attempt path traversal (e.g., `../`) unless the server strictly normalizes and allowlists paths.","Write tools can cause unintended edits—agents should be constrained to safe directories and consider dry-run/preview if supported.","Large file reads may exceed model/tool limits; agents may need to request bounded reads (if supported).","Concurrency/race conditions during file edits can lead to inconsistent states unless the server provides versioning/locking."],"error_quality":0.0}