| FMRS | 35 / 100 · D | 84 / 100 · B | 60 / 100 · C |
|---|
| Reliability | 6 / 20 | 17 / 20 | 9 / 20 |
|---|
| Security and permissions | 6 / 20 | 16 / 20 | 13 / 20 |
|---|
| Maintenance | 11 / 20 | 16 / 20 | 10 / 20 |
|---|
| Documentation | 5 / 20 | 17 / 20 | 15 / 20 |
|---|
| Setup experience | 7 / 20 | 18 / 20 | 13 / 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
| - Users who want to access a local Obsidian vault through multiple MCP clients.
- Note workflows that need to preserve raw formatting for unmodified frontmatter fields.
- Knowledge-base users who need local file operations, search, and tag management.
|
|---|
| 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
| - Users without an Obsidian vault or local vault directory.
- Users seeking a remote network service, cloud-hosted service, or non-MCP integration.
- Users who do not want an AI assistant to access or modify vault content and structure.
|
|---|
| 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
| - Requires Node.js 18 or later.
- Requires read access to the specified vault; writing, moving, and deleting also require the corresponding write permissions.
- The server can access allowed `.md`, `.markdown`, `.txt`, `.base`, and `.canvas` files.
- The AI assistant can see allowed file content, directory structure, and some file metadata.
|
|---|
| 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
| - The server provides full read/write access within its security boundaries, so incorrect instructions can modify or delete notes.
- Vault content, structure, and file metadata may be exposed to AI conversations with access.
- Permanent deletion may be unrecoverable; back up the vault before write operations.
- Path filtering does not isolate content, so sensitive data in allowed files remains readable.
|
|---|
| Supported clients | | Claude Desktop, Cursor, Cline, Windsurf | Claude Desktop, Claude Code, OpenCode, Goose Desktop, ChatGPT Desktop, IntelliJ IDEA 2025.1+, Cursor IDE, Windsurf IDE, Ontheia, Microsoft Copilot Studio, OpenAI Codex |
|---|
| Tools | 0 | 6 | 14 |
|---|