| Obsidian MCP bridges — mcp-obsidian, obsidian-local-rest-api, wrappers around the Obsidian CLI | Expose a running Obsidian desktop app to agents over MCP. | Headless server: no Obsidian process needed, runs on a box or in a container, multi-user with roles, per-project visibility and grants (accounts and teams), tokens narrowed to each account, audit trail. The vault stays a plain Obsidian vault. |
| Markdown memory servers — basic-memory, mcp-vault | Same "files, not a database" idea; usually add hybrid semantic search, a cloud tier or WebDAV sync. | Ships a full web UI, real multi-user, an agent handoff bus and a server-served working method (versioned directives, lint, stale detection). No semantic search by design (ADR-007), no hosted tier. |
| Client-side wiki skills — obsidian-wiki and the "LLM Wiki" pattern | Slash-commands the agent runs locally to compile and maintain a wiki. No server, no auth, no UI. | The same pattern implemented server-side and agent-agnostic: one-call scaffold, directives served at bootstrap, handoffs, audit. Complementary: those skills work against a gosidian vault too. |
| Agent memory services — mem0, agentmemory, mcp-memory-service | Memory as an opaque store: embeddings, recall benchmarks, auto-capture hooks. | Memory is markdown that humans read in Obsidian or the web UI, retrieved by identity and graph, with no embeddings; a language model is called only by the pipelines you turn on. Auto-capture through Claude Code hooks (contrib/claude-code/: focus injected at session start, session digests at compaction and end) rather than inside the binary. No published recall numbers yet. |
| Note apps with community MCP servers — SilverBullet, Trilium, SiYuan | Mature editors, mobile apps, sometimes real-time collaboration; MCP added by third-party servers on top of their API. | MCP-first: the server is in the binary, behind the same login, roles and audit as the UI. No mobile app, no real-time collaboration, no WYSIWYG editor. |