| FMRS | 47 / 100 · D | 84 / 100 · B | 79 / 100 · B |
|---|
| Reliability | 6 / 20 | 17 / 20 | 12 / 20 |
|---|
| Security and permissions | 8 / 20 | 16 / 20 | 18 / 20 |
|---|
| Maintenance | 10 / 20 | 16 / 20 | 15 / 20 |
|---|
| Documentation | 12 / 20 | 17 / 20 | 19 / 20 |
|---|
| Setup experience | 11 / 20 | 18 / 20 | 15 / 20 |
|---|
| Best for | - AI agent developers who already use bash and want one filesystem interface instead of many SDKs/MCPs
- Workflows that need to pipe data between S3, Google Drive, Slack, OneDrive/SharePoint, and similar backends
- Teams embedding an agent workspace directly inside a Python/TypeScript app (FastAPI, Express, etc.)
| - Local assistants that need to work inside explicitly approved directories
- Individuals and development teams that want path-based data boundaries
| - Serious Obsidian users who want AI agents reading and writing their vault
- Users wanting self-hosted, plugin-free operation with no external APIs
- Mobile/multi-device workflows accessing the vault remotely
- Security-conscious users (OAuth 2.1, atomic writes, container hardening)
|
|---|
| Not for | - Simple single-service use cases that don't need a unified cross-backend interface
- Non-macOS/Linux environments where FUSE-based mounts aren't supported
- High-security scenarios requiring fine-grained, per-action permission control rather than a general bash execution interface
| - Highly sensitive environments that cannot allow model access to local file contents
- Shared remote file-service use cases
| - Users unwilling to run Docker or self-host a server
- Non-Obsidian note tools (Notion, Logseq, etc.)
- Scenarios requiring only a stdio local process without an HTTP server
- Remote multi-device sync without an Obsidian Sync subscription (the remote image requires one)
|
|---|
| Required permissions | - Access credentials or API tokens for each mounted backend (e.g., OneDrive, SharePoint, S3, Slack, Gmail)
- Local filesystem read/write access (for RAM/Disk resources and caching)
- Outbound network access to reach remote backend APIs
| - Read access to every local directory listed in the configuration
- Filesystem write access when write or move tools are enabled
| - Read/write access to the Obsidian vault folder (bind mount /vault, rw)
- Persistent /data volume (search index, OAuth token DB, logs)
- MCP_AUTH_TOKEN as Bearer token (also the JWT signing key)
- Obsidian Sync token for headless sync in remote mode
- Local download of embedding/reranker models (~45MB total), no external API calls
|
|---|
| Risks and side effects | - A single bash-like execution interface can let an agent broadly read, copy, or overwrite data across every mounted, potentially sensitive backend
- Content pulled in from mounted sources (e.g., Slack messages, email) carries prompt-injection risk that could influence subsequent agent behavior
- Index and file caches (default TTL 10 minutes / default 512MB) can serve stale data until they expire
- Once credentials are configured for a workspace, an agent may end up with broader cross-service access than intended for a given task
| - Sensitive files inside an allowed directory may enter model context
- Write and move tools change real files; keep scopes narrow and maintain backups
| - The server can read and write personal notes — guard MCP_AUTH_TOKEN carefully; leaking it exposes the whole vault
- Writes to real note files; despite atomic writes and protected paths, misconfiguration can alter data
- OAuth token DB lives on the /data volume; container compromise could expose valid sessions
- Remote deployments expose a public port — set PUBLIC_URL and reverse proxy correctly
- The remote image bundles proprietary obsidian-headless (not MIT-licensed); requires an active Obsidian Sync subscription
|
|---|
| Supported clients | Claude Code | Claude Desktop, Cursor, Cline, Windsurf | Claude Code, Claude Desktop, claude.ai, Cursor, OpenCode, MCP Inspector |
|---|
| Tools | 1 | 6 | 30 |
|---|