← Back to directory
COMPARE UP TO 4 SERVERS

Compare MCP servers

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

DimensionObsidian MCP ServerManage Obsidian knowledge bases through MCP.Obsidian Web MCPSecure remote access to your Obsidian vault over HTTPS with OAuth 2.0 authentication.
FMRS60 / 100 · C68 / 100 · C
Reliability10 / 209 / 20
Security and permissions11 / 2016 / 20
Maintenance10 / 2014 / 20
Documentation16 / 2017 / 20
Setup experience13 / 2012 / 20
Best for
  • Obsidian users already running the Local REST API plugin.
  • MCP client users who need structured note search and surgical editing.
  • Deployments that need vault access restricted by read and write folder allowlists.
  • 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
  • Environments without the Obsidian Local REST API plugin installed and enabled.
  • Teams seeking a cloud-native multi-user database or collaboration platform.
  • Situations where note write access or local API-key management is unacceptable.
  • 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
  • Requires OBSIDIAN_API_KEY to access the Obsidian Local REST API.
  • By default, the full vault is accessible; OBSIDIAN_READ_PATHS and OBSIDIAN_WRITE_PATHS can restrict folders.
  • All writes can be disabled globally with OBSIDIAN_READ_ONLY=true.
  • HTTP deployments support none, jwt, or oauth authentication; JWT mode requires MCP_AUTH_SECRET_KEY.
  • 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
  • Write tools can modify or delete vault content; obsidian_delete_note permanently deletes notes.
  • Command-palette commands may be destructive and are disabled by default.
  • An unauthenticated public HTTP deployment may let callers use the server's API key to access the vault.
  • The HTTPS plugin endpoint uses a self-signed certificate and TLS verification defaults to false.
  • The tag list and obsidian://tags resource are vault-wide and may expose tag names outside the read scope.
  • 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, Cursor, VS CodeClaude Desktop, Claude Mobile, Claude Web
Tools1420