| FMRS | 62 / 100 · C | 84 / 100 · B | 68 / 100 · C |
|---|
| Reliability | 8 / 20 | 17 / 20 | 9 / 20 |
|---|
| Security and permissions | 14 / 20 | 16 / 20 | 16 / 20 |
|---|
| Maintenance | 14 / 20 | 16 / 20 | 14 / 20 |
|---|
| Documentation | 16 / 20 | 17 / 20 | 17 / 20 |
|---|
| Setup experience | 10 / 20 | 18 / 20 | 12 / 20 |
|---|
| Best for | - Users who want a real-time view of disk space distribution.
- Users who want AI-assisted disk cleanup and data management.
- Users needing a cross-platform (macOS, Windows, Linux) storage analyzer.
| - Local assistants that need to work inside explicitly approved directories
- Individuals and development teams that want path-based data boundaries
| - Users who want secure remote access to their Obsidian vault from any device.
- Integrating Claude.ai (web) or mobile with Obsidian.
- Those needing concurrent writes with Obsidian Sync without file conflicts.
|
|---|
| Not for | - Users who need permanent deletion (rather than moving to trash).
- Users who need content-level cloud scanning (metadata only).
- Users who cannot install Node.js for MCP usage.
| - Highly sensitive environments that cannot allow model access to local file contents
- Shared remote file-service use cases
| - Users who only need local stdio MCP access without remote capabilities.
- Those unwilling to set up an OAuth password or use a Cloudflare Tunnel.
- Users with extremely high security requirements who distrust network exposure (though encrypted).
|
|---|
| Required permissions | - Read file and folder metadata (size, path, etc.).
- Move files to the system trash (via OS APIs, recoverable).
- Access system trash size.
- Optionally listen on the LAN in a separate process (Fleet feature, off by default).
| - Read access to every local directory listed in the configuration
- Filesystem write access when write or move tools are enabled
| - Read and write files in the directory specified by VAULT_PATH.
- Perform file operations (move, delete with soft delete to .trash).
- Create daily notes, write binary files.
- Maintain an in-memory frontmatter index, potentially modifying index files.
- Access the network (for Cloudflare Tunnel, heartbeat URLs).
|
|---|
| Risks and side effects | - AI might accidentally trash important files, but deletions go to the system trash and can be manually restored.
- AI may scan folders with sensitive information, but data is processed locally and not uploaded.
- Cloud interactions are metadata-only; no file contents are downloaded.
- Offload requires sufficient space on the target drive; failure rolls back safely.
| - Sensitive files inside an allowed directory may enter model context
- Write and move tools change real files; keep scopes narrow and maintain backups
| - Credential leakage: exposed OAuth password or MCP token could allow unauthorized access.
- Path traversal mitigation is not infallible; keep updated.
- Extension system is not sandboxed; loading untrusted extensions could be risky.
- Audit log is best-effort and not tamper-evident; records may be dropped at runtime.
- Misconfiguration may cause the server to fail to start or expose vulnerabilities.
|
|---|
| Supported clients | Claude Desktop, Claude Code, Cursor | Claude Desktop, Cursor, Cline, Windsurf | Claude Desktop, Claude Mobile, Claude Web |
|---|
| Tools | 8 | 6 | 20 |
|---|