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.Safe Docx MCP ServerAI-native surgical editing of Word and OpenDocument files with formatting preservation
FMRS60 / 100 · C68 / 100 · C
Reliability10 / 208 / 20
Security and permissions11 / 2016 / 20
Maintenance10 / 2014 / 20
Documentation16 / 2018 / 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.
  • Developers who need precise, format-preserving edits to .docx/.odt files via coding agents
  • Workflows that require tracked-changes output for human review
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.
  • Visual editing scenarios needing browser rendering, real-time collaboration, or pixel-level pagination guarantees
  • Using .dotx templates directly (they must be converted to .docx first)
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.
  • Filesystem access to read and write local .docx / .odt documents
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.
  • Edits apply to local files; incorrect targeted changes could overwrite original content — use the clean/tracked-changes dual output for review
  • The project is not a visual editor or layout engine, so complex layout results should be verified manually
Supported clientsClaude Desktop, Cursor, VS Code
Tools140