enquire-mcp

Adoption judgment: this is best understood as an MCP retrieval layer for an Obsidian knowledge base, not a general chatbot or a standalone vector database. Nearly all available evidence comes from the official GitHub repo copy, which supports the positioning and feature scope, but not strong claims about real-world quality, reliability, or ease of setup.

In practical terms, the repo description says it offers long-term memory, hybrid retrieval, reranking, agentic RAG, and PDF/OCR support for people who want AI agents to access Obsidian notes. A more accurate analogy is a retrieval-and-memory interface over a personal knowledge base that MCP clients can call, not a Notion-style collaborative workspace and not a full agent framework by itself.

On cost and effort, the evidence only confirms that it is open source. There is no official pricing, hosted plan, or API fee information in the sources, so total cost should not be assumed. Conservatively, the main costs are likely self-hosting/setup time, model or reranker configuration, and compute for OCR/PDF processing, but that is an inference from the architecture rather than an official promise.