| FMRS | 43 / 100 · D | 84 / 100 · B | 79 / 100 · B |
|---|
| Reliability | 5 / 20 | 17 / 20 | 12 / 20 |
|---|
| Security and permissions | 8 / 20 | 16 / 20 | 18 / 20 |
|---|
| Maintenance | 12 / 20 | 16 / 20 | 15 / 20 |
|---|
| Documentation | 11 / 20 | 17 / 20 | 19 / 20 |
|---|
| Setup experience | 7 / 20 | 18 / 20 | 15 / 20 |
|---|
| Best for | - Developers with basic knowledge of at least one supported programming language
- Learners who want a hands-on introduction to MCP
- Developers looking for cross-language MCP learning material
| - Local assistants that need to work inside explicitly approved directories
- Individuals and development teams that want path-based data boundaries
| - 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 | - Users seeking a ready-to-use production tool or business integration
- Users requiring documented tools, transport details, or client configuration
- Users without basic programming, client-server, and API knowledge
| - Highly sensitive environments that cannot allow model access to local file contents
- Shared remote file-service use cases
| - 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 | - The source does not specify any required system, network, account, or data permissions for the server
- Accessing the curriculum requires at least permission to read or clone the GitHub repository
| - Read access to every local directory listed in the configuration
- Filesystem write access when write or move tools are enabled
| - 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 | - The source does not document the sample server's specific tools, runtime behavior, or permission boundaries
- The curriculum covers security, authentication, and deployment, but that does not establish that this sample implements those capabilities
- Review the sample code and dependencies before use, and avoid treating an unreviewed example as production-ready
| - Sensitive files inside an allowed directory may enter model context
- Write and move tools change real files; keep scopes narrow and maintain backups
| - 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 clients | | Claude Desktop, Cursor, Cline, Windsurf | Claude Code, Claude Desktop, Claude.ai, Cursor, OpenCode, MCP Inspector |
|---|
| Tools | 0 | 6 | 30 |
|---|