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.Safe Docx MCP ServerAI-native surgical editing of Word and OpenDocument files with formatting preservation
FMRS68 / 100 · C68 / 100 · C
Reliability9 / 208 / 20
Security and permissions16 / 2016 / 20
Maintenance14 / 2014 / 20
Documentation17 / 2018 / 20
Setup experience12 / 2012 / 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.
  • 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
  • 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).
  • 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
  • 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).
  • Filesystem access to read and write local .docx / .odt documents
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.
  • 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, Claude Mobile, Claude Web
Tools200