← Back to directory
COMPARE UP TO 4 SERVERS

Compare MCP servers

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

DimensionUI-TARS Filesystem MCP ServerRestricted filesystem access for MCPFilesystem MCP ServerSecure local file read/write access
FMRS46 / 100 · D84 / 100 · B
Reliability8 / 2017 / 20
Security and permissions8 / 2016 / 20
Maintenance13 / 2016 / 20
Documentation7 / 2017 / 20
Setup experience10 / 2018 / 20
Best for
  • MCP clients that need controlled local file access
  • Developers who want to explicitly constrain filesystem operations
  • Local assistants that need to work inside explicitly approved directories
  • Individuals and development teams that want path-based data boundaries
Not for
  • Workflows that require access to unauthorized directories
  • Users seeking a server with documented tool names or broader capabilities
  • Highly sensitive environments that cannot allow model access to local file contents
  • Shared remote file-service use cases
Required permissions
  • The server needs file-operation access to the directories listed in allowed-directories
  • SSE and Streamable HTTP modes require use of the configured local port
  • Read access to every local directory listed in the configuration
  • Filesystem write access when write or move tools are enabled
Risks and side effects
  • An overly broad allowed-directories value may expand the scope of local files that can be exposed or modified
  • When using a local SSE or HTTP endpoint, port and access-scope configuration should be reviewed
  • The source does not specify individual filesystem tools, authentication, or authorization mechanisms
  • 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