← Back to directory
COMPARE UP TO 4 SERVERS

Compare MCP servers

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

DimensionFilesystem MCP ServerLocal project-file access over stdio.Obsidian Web MCPSecure remote access to your Obsidian vault over HTTPS with OAuth 2.0 authentication.
FMRS35 / 100 · D68 / 100 · C
Reliability6 / 209 / 20
Security and permissions6 / 2016 / 20
Maintenance11 / 2014 / 20
Documentation5 / 2017 / 20
Setup experience7 / 2012 / 20
Best for
  • Developers who need an MCP client to access a specified Claude Code project directory.
  • 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 database access or custom API tools.
  • Users who need remote deployment, SSE, or streamable-http transport.
  • 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
  • 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 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
  • 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.
  • 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 clientsClaude Desktop, Claude Mobile, Claude Web
Tools020