- Vault access servers — expose your vault to an agent as tools. The large majority.
- Retrieval engines — the vault as a search corpus: embeddings, BM25, graph, rerank.
- Memory engines — durable agent memory (what happened, what was learned, what is no longer true), usually in a knowledge base beside your vault rather than in it.
Where the others win, plainly:
- Zero-config start.
mcpvaultis onenpxline andengraphis onebrew installwith local models bundled — no config file, no separate embeddings pull. reliquary-tc’snpx reliquary-tc /path/to/vaultmatches that for a single vault (lexical search and every note tool work immediately); multi-vault, ACLs, and custom embeddings still want a config file, and semantic/graph retrieval still wants an embeddings backend. - Nothing outside Obsidian.
aaronsb/obsidian-mcp-pluginruns inside the app — no external process at all. reliquary-tc is a standalone server. - Offline retrieval quality, as core rather than opt-in.
engraphships cross-encoder reranking and a query orchestrator as core, on local models, everywhere it runs. reliquary-tc’s cross-encoder reranker is now also local and gateway-free — an optional npm package (@the-40-thieves/reliquary-tc-reranker-local), auto-selected when norerankerblock, noembeddings.modelTier.full, and no gateway URL are configured, that fetches and checksum-verifies its weights on first use — but it is opt-in machinery, not core: the standalone compiled binaries, musl (Alpine) installs, and macOS x64 can’t reach it. - Memory as a portable KB.
basic-memorykeeps memory in its own markdown store that syncs to any vault. If you want memory decoupled from one vault, that is the better fit.
When NOT to use reliquary-tc
Honest guidance — reliquary-tc is deliberately a heavier product:- You want the smallest possible footprint. A single trusted human driving a chat client over one vault is well served by the simpler community servers above; the governance pipeline here mostly pays off with autonomous or multi-agent access.
- You only need read access. A read-only wrapper (cyanheads’
OBSIDIAN_READ_ONLY, or aaronsb’s read-only mode) is less machinery for a similar safety outcome. - You want everything inside Obsidian. reliquary-tc is a standalone server, not an Obsidian plugin — the optional companion plugin only bridges plugin-specific features. If you never leave the app, aaronsb/obsidian-mcp-plugin runs the whole server in-process, and community plugins may be all you need.
- You want the best search with no setup and no network. engraph is a single binary with local models and no configuration. Our retrieval goes further on fusion and diversity and is gated by a statistical ship rule, but it asks more of you and its rerank stage is opt-in machinery today, not core: unreachable from the standalone compiled binaries, musl (Alpine) installs, or macOS x64.
- You want agent memory that is not tied to one vault. basic-memory keeps memory in its own portable markdown KB. Ours is deliberately inside the vault, so it inherits the vault’s ACL and audit trail — a different trade, not a strictly better one.
- You don’t need MCP at all. Obsidian URI or the Local REST API plugin can cover simple scripting directly.