M
MCP Directory CURATED DIRECTORY
693 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.

DimensionFast Filesystem MCPHigh-performance filesystem MCP server for Claude Desktop with large file handling and advanced editing.Filesystem MCP ServerSecure local file read/write accessObsidian Web MCPSecure remote access to your Obsidian vault over HTTPS with OAuth 2.0 authentication.
FMRS47 / 100 · D84 / 100 · B68 / 100 · C
Reliability7 / 2017 / 209 / 20
Security and permissions8 / 2016 / 2016 / 20
Maintenance9 / 2016 / 2014 / 20
Documentation11 / 2017 / 2017 / 20
Setup experience12 / 2018 / 2012 / 20
Best for
  • Claude Desktop users needing fast file operations
  • Developers handling large files or streaming data
  • Scenarios requiring backups and fault-tolerant editing
  • Automated file management and sync tasks
  • Local assistants that need to work inside explicitly approved directories
  • Individuals and development teams that want path-based data boundaries
  • 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.
Not for
  • Environments with high security requirements that distrust third-party MCP servers
  • Remote scenarios requiring network transport (e.g., SSE or HTTP)
  • Fully offline environments without Node.js
  • Needs for graphical interface or interactive file management
  • Highly sensitive environments that cannot allow model access to local file contents
  • Shared remote file-service use cases
  • 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).
Required permissions
  • Read/write filesystem: can read, write, modify, and delete files and directories
  • Create backup files (if enabled)
  • Execute commands: via `npx`
  • Access network (for installation)
  • Read access to every local directory listed in the configuration
  • Filesystem write access when write or move tools are enabled
  • 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).
Risks and side effects
  • File operations may cause data loss or overwrites, despite backup mechanisms
  • Malicious prompts could induce unintended operations, requiring user confirmation
  • Third-party server may contain vulnerabilities
  • Improper allowed directories configuration may expose sensitive files
  • Sensitive files inside an allowed directory may enter model context
  • Write and move tools change real files; keep scopes narrow and maintain backups
  • 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.
Supported clientsClaude DesktopClaude Desktop, Cursor, Cline, WindsurfClaude Desktop, Claude Mobile, Claude Web
Tools26620