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 Local REST APIA secure REST API and MCP server for your Obsidian vaultVault Cortex MCP ServerStandalone MCP server for Obsidian vaults: hybrid search, notes & files, structured memory, tasks, OAuth 2.1.
FMRS64 / 100 · C79 / 100 · B
Reliability7 / 2012 / 20
Security and permissions14 / 2018 / 20
Maintenance13 / 2015 / 20
Documentation16 / 2019 / 20
Setup experience14 / 2015 / 20
Best for
  • 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.
  • 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 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.
  • 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
  • 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.
  • 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
  • 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.
  • 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 DesktopClaude Code, Claude Desktop, Claude.ai, Cursor, OpenCode, MCP Inspector
Tools1630