← Back to directory
COMPARE UP TO 4 SERVERS

Compare MCP servers

Compare scores, permissions, risks, and fit in one decision-focused table.

DimensionFilesystem MCP ServerLocal project-file access over stdio.Filesystem MCP ServerSecure local file read/write access
FMRS35 / 100 · D84 / 100 · B
Reliability6 / 2017 / 20
Security and permissions6 / 2016 / 20
Maintenance11 / 2016 / 20
Documentation5 / 2017 / 20
Setup experience7 / 2018 / 20
Best for
  • Developers who need an MCP client to access a specified Claude Code project directory.
  • Local assistants that need to work inside explicitly approved directories
  • Individuals and development teams that want path-based data boundaries
Not for
  • Users who need database access or custom API tools.
  • Users who need remote deployment, SSE, or streamable-http transport.
  • Highly sensitive environments that cannot allow model access to local file contents
  • Shared remote file-service use cases
Required permissions
  • Access to the local project directory specified by ${CLAUDE_PROJECT_DIR}.
  • The exact read/write scope depends on the client, operating system, and server implementation; the source does not specify it.
  • Read access to every local directory listed in the configuration
  • Filesystem write access when write or move tools are enabled
Risks and side effects
  • The MCP server may access local files; specify only a directory you are willing to authorize.
  • The README warns that MCP servers, files, or other software included in plugins may not be controlled by Anthropic and are not guaranteed to work as intended or avoid making changes.
  • Sensitive files inside an allowed directory may enter model context
  • Write and move tools change real files; keep scopes narrow and maintain backups
Supported clientsClaude Desktop, Cursor, Cline, Windsurf
Tools06