@oomkapwn/enquire-mcp weekly downloads statistics

<div align="center">

<a href="https://github.com/oomkapwn/enquire-mcp"><img src="./assets/social-preview.png" alt="enquire-mcp — the most advanced Obsidian MCP. Long-term memory for AI agents. Built on your Obsidian vault. Open-source, MCP-native, vendor-neutral. Hybrid retrieval, BGE reranker, HNSW, PDFs with OCR. For Claude Code, Claude Desktop, Cursor, ChatGPT, Codex, OpenClaw." width="100%"></a>

enquire-mcp

_{English · 中文 · Español · हिन्दी · العربية · Русский · Português · Français · 日本語 · 한국어 · Deutsch}

_{TL;DR for AI agents — MCP server exposing a local Obsidian markdown vault to Claude Code, Claude Desktop, Cursor, ChatGPT, Codex, and OpenClaw as persistent searchable memory. Hybrid retrieval (BM25 + ML embeddings + BGE reranker, RRF-fused), HNSW + int8 quantization, agentic RAG (HyDE + sub-question), GraphRAG-light, PDFs + OCR, standalone Bases. Vendor-neutral, MIT, zero cloud calls during serve. Install: npm i -g @oomkapwn/enquire-mcp. Docs: llms.txt · AGENTS.md · API.}

The most advanced Obsidian MCP. Long-term memory for AI agents.

Stop re-explaining context to Claude, Cursor, ChatGPT, Codex, OpenClaw every session. Your Obsidian notes become shared, searchable memory across every MCP-compatible agent — your knowledge, every model, forever yours.

Measured: the BGE cross-encoder reranker adds +15.5 NDCG@10 / +24.7 MRR over plain hybrid on a reproducible 60-query ablation — the full modern IR stack, recalling the markdown you wrote (cited, editable), never a cloud paraphrase.

⚡ 30-second install · 🧠 Use cases · 📊 Benchmarks · 📖 API reference · 💬 Compare alternatives

Claude Code — one line:

claude mcp add obsidian -- npx -y @oomkapwn/enquire-mcp serve --vault ~/Documents/Obsidian\ Vault

</div>

---

The problem

Every AI session starts from zero. You re-explain your project, your design decisions, the conclusions of last week's research. Vendor "memory" features (Claude Memory, ChatGPT Memory, Cursor memory) lock your knowledge into one provider's cloud — and forget it again when you switch tools. Your knowledge keeps starting over.

The solution

Your Obsidian vault becomes persistent, queryable long-term memory for any MCP-compatible agent. One install — your knowledge is instantly accessible from Claude Code, Claude Desktop, Cursor, ChatGPT custom GPT, Codex, OpenClaw, and every other MCP client. Plain markdown files you own, indexed locally, searched with the full modern IR stack, recalled across every session and every model.

Grounded, not extracted. Conversation-memory tools (mem0, Zep, Supermemory, Memobase) extract facts from your chat logs into a separate store you can't read. enquire-mcp is the inverse: it's grounded in the knowledge you already wrote — your own .md notes, verbatim, with citations — so recall is auditable, editable in any editor, and never a lossy summary of a chat you half-remember. And unlike server-side fleet-memory platforms — multi-tenant cloud stores that paraphrase agent traffic into a shared database — enquire is single-user and local-first: one vault you own outright and can read, edit, and delete yourself, with zero cloud calls during serve. (That "extracted" critique is specific to the chat-memory cohort — not to knowledge-graph / ETL tools like cognee, nor to personal-search peers like Khoj.)

Grounded — and freshness-aware. Recalling a fact is half the problem; knowing whether it's still true is the other half. The Memora benchmark (Apr 2026) showed memory systems systematically fail at stale-fact reuse — recalling a year-old note as if it were written today. Because enquire's memory is your real markdown files, every search hit carries age_days + a stale flag derived from the note's live last-modified time, and you can opt into recency-weighted ranking (--recency-weight) so fresher notes surface first. Your knowledge, freshness-aware — not a timeless blob.…