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.

DimensionScan MCPMCP server for scanner discovery and batch capture via SANE on LinuxVault Cortex MCP ServerStandalone MCP server for Obsidian vaults: hybrid search, notes & files, structured memory, tasks, OAuth 2.1.
FMRS53 / 100 · D79 / 100 · B
Reliability10 / 2012 / 20
Security and permissions9 / 2018 / 20
Maintenance10 / 2015 / 20
Documentation13 / 2019 / 20
Setup experience11 / 2015 / 20
Best for
  • Linux users with SANE-compatible scanners
  • Those needing local, privacy-first scanning automation (stdio)
  • Developers or advanced users who want programmable batch and multipage scanning
  • 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
  • Windows or macOS users (Linux-only)
  • Those relying on networked authentication or secure transport (HTTP lacks authentication)
  • Users needing camera or non-SANE backends (although it attempts to avoid such devices)
  • 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
  • System permissions to execute scanimage/scanadf commands
  • Write access to INBOX_DIR (default: scanned_documents/inbox)
  • Filesystem permissions to access temp and output directories
  • Optional: network permissions and TCP port access if using HTTP transport
  • 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
  • HTTP transport has no built-in authentication; only suitable for trusted internal networks
  • Scanning failures could lead to data loss or incomplete outputs; use job cancellation and status monitoring
  • Incorrect device options or high resolutions may consume significant disk space
  • External command dependencies: missing tools or misconfigured SANE can make the server non-functional
  • 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
Tools830