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.Obsidian Local REST APIA secure REST API and MCP server for your Obsidian vault
FMRS68 / 100 · C64 / 100 · C
Reliability9 / 207 / 20
Security and permissions16 / 2014 / 20
Maintenance14 / 2013 / 20
Documentation17 / 2016 / 20
Setup experience12 / 2014 / 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.
  • Users who need programmatic control over their Obsidian vault for automation and AI integration.
  • Developers and power users building note-taking automation workflows.
  • Scenarios where AI agents need to act on your notes directly without exporting or manual copying.
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 uncomfortable with technical setup or unable to handle self-signed certificates.
  • Scenarios requiring public access or non-local servers, as the server is designed for local use.
  • Clients that require other MCP transports (like SSE or stdio) or don't support Streamable HTTP.
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).
  • Full read, write, and delete access to all files in your Obsidian vault.
  • Execute any Obsidian command (equivalent to using the command palette).
  • Access information about the currently active file.
  • Open files in the Obsidian UI.
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.
  • If the API key is compromised, an attacker can view and modify all your notes, execute commands, or delete files.
  • The self-signed certificate could be susceptible to man-in-the-middle attacks if not verified properly.
  • Executing commands can lead to unintended modifications, such as deleting or overwriting notes.
  • The local HTTP server could be exploited by other local programs if port binding is not secure.
Supported clientsClaude Desktop, Claude Mobile, Claude WebClaude Desktop
Tools2016