librarian
Related Servers
Alternatives to librarian
No user-submitted related servers found.
Related Servers
- FlicenseNot gradedqualityAmaintenanceEnables AI agents and MCP hosts to search and ask questions across a local hybrid-retrieval index of scattered notes, documents, PDFs, and chat logs, returning section-level citations and agent-usable tools, resources, and prompts.-
- FlicenseNot gradedqualityAmaintenanceEnables AI agents and MCP hosts to query locally indexed notes, docs, chat logs, and other files via hybrid vector/BM25 retrieval with section-level citations. Exposes tools, resources, and prompts for searching and asking over the indexed content.-
- FlicenseNot gradedqualityAmaintenanceEnables AI hosts and agents to query a local hybrid index of scattered notes and documents, retrieve section-level citations, and access resources and prompts through MCP.-
- FlicenseNot gradedqualityAmaintenanceEnables MCP-compatible AI agents to search, ask, and retrieve section-level cited answers from a local hybrid index over scattered notes, documents, and chat logs.-
- AlicenseNot gradedqualityBmaintenanceEnables AI agents to search local text and Markdown collections using keyword BM25, semantic vector search, and reranked hybrid retrieval, with full-document retrieval and collection status over MCP.1,009 PyPIMIT
- FlicenseNot gradedqualityAmaintenanceEnables AI agents and MCP hosts to search and query a local hybrid vector/BM25 index of scattered notes, docs, PDFs, Office files, web pages, org files, and chat exports. It returns section-level citations so agents can ground answers in the user's own files.-
TDQS
Scored across 4 tools
search and fetch are clearly distinct (find vs. read), but outline and index_info overlap heavily — both are described as telling you 'what the index covers' (sources, dates, version coverage), with only counts vs. boards/terms differentiating them. An agent can plausibly pick the wrong one of the pair when it just wants to know what's available.
Two tools are bare verbs (search, fetch), one is a standalone noun (outline), and one uses a noun_noun form with an underscore (index_info). All are readable and snake_case-compatible, but there is no single consistent pattern across the set.
Four tools is lean and appropriate for a retrieval server: discover, search, fetch, plus one metadata helper. The only quibble is that the metadata helper is duplicated (outline vs. index_info), so one slot is arguably wasted.
The core retrieval lifecycle — orient on the index, search with filters, fetch full documents/threads with citation metadata — is fully covered with no dead ends. Minor gaps: no way to enumerate chunks within a document or browse a source without a query, though search filters partially compensate.