M
MCP Directory CURATED DIRECTORY
911 MCP servers indexed
中文
← Back to directory
COMPARE UP TO 4 SERVERS

Compare MCP servers

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

DimensionObsidian Web MCPSecure remote access to your Obsidian vault over HTTPS with OAuth 2.0 authentication.Vault Cortex MCP ServerStandalone MCP server for Obsidian vaults: hybrid search, notes & files, structured memory, tasks, OAuth 2.1.
FMRS68 / 100 · C79 / 100 · B
Reliability9 / 2012 / 20
Security and permissions16 / 2018 / 20
Maintenance14 / 2015 / 20
Documentation17 / 2019 / 20
Setup experience12 / 2015 / 20
Best for
  • 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.
  • 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
  • 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).
  • 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
  • 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).
  • 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
  • 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.
  • 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 clientsClaude Desktop, Claude Mobile, Claude WebClaude Code, Claude Desktop, Claude.ai, Cursor, OpenCode, MCP Inspector
Tools2030