| FMRS | 59 / 100 · C | 84 / 100 · B | 68 / 100 · C |
|---|
| Reliability | 7 / 20 | 17 / 20 | 9 / 20 |
|---|
| Security and permissions | 11 / 20 | 16 / 20 | 16 / 20 |
|---|
| Maintenance | 13 / 20 | 16 / 20 | 14 / 20 |
|---|
| Documentation | 15 / 20 | 17 / 20 | 17 / 20 |
|---|
| Setup experience | 13 / 20 | 18 / 20 | 12 / 20 |
|---|
| Best for | - Users already managing a personal or team knowledge base in Obsidian
- Scenarios where the AI needs to understand link structure between notes, not just isolated files
- Users of Claude Desktop, Claude Code, or other local MCP clients
| - 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 don't use Obsidian
- Setups requiring a cloud-hosted MCP service with no local server to run
- Scenarios requiring official support from the Obsidian team (this is a third-party community plugin)
| - 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 | - API key authentication (Bearer token) to access the local HTTP/HTTPS server port
- Read, write, create, move, split, and combine permissions on vault files
- Configurable to read-only mode, per-operation authorization, and path allow/block lists
| - 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 | - In default (non-read-only) mode, the AI can modify, move, or merge notes in the vault; misuse could cause data loss or structural disruption
- HTTPS relies on a self-signed certificate that must be trusted carefully — avoid globally disabling certificate verification via NODE_TLS_REJECT_UNAUTHORIZED=0
- This is a third-party community plugin (not maintained by the Obsidian team), so updates and long-term support depend on the maintainer
| - 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, Cline, Continue.dev | Claude Desktop, Cursor, Cline, Windsurf | Claude Desktop, Claude Mobile, Claude Web |
|---|
| Tools | 8 | 6 | 20 |
|---|