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 MCP ServerManage Obsidian knowledge bases through MCP.Filesystem MCP ServerSecure local file read/write access
FMRS60 / 100 · C84 / 100 · B
Reliability10 / 2017 / 20
Security and permissions11 / 2016 / 20
Maintenance10 / 2016 / 20
Documentation16 / 2017 / 20
Setup experience13 / 2018 / 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.
  • Local assistants that need to work inside explicitly approved directories
  • Individuals and development teams that want path-based data boundaries
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.
  • Highly sensitive environments that cannot allow model access to local file contents
  • Shared remote file-service use cases
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 access to every local directory listed in the configuration
  • Filesystem write access when write or move tools are enabled
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.
  • Sensitive files inside an allowed directory may enter model context
  • Write and move tools change real files; keep scopes narrow and maintain backups
Supported clientsClaude Desktop, Cursor, VS CodeClaude Desktop, Cursor, Cline, Windsurf
Tools146