litedocs-mcp
Related Servers
Alternatives to litedocs-mcp
No user-submitted related servers found.
Related Servers
- AlicenseNot gradedqualityAmaintenanceTurns a local folder of documents into a queryable index that an LLM agent can pull from on demand, keeping only a compact table of contents in context. Exposes five tools (index, search, read, grep, neighbours) over a single offline SQLite FTS5 store so the model retrieves exact, citable sections instead of being handed whole files.MIT
- AlicenseAqualityBmaintenanceProvides fast, token-efficient search over coding agent documentation (e.g., Claude Code, Cursor) using local SQLite FTS5 indexing, with tools for searching snippets, reading pages, and grepping markdown.5MIT
- AlicenseAqualityAmaintenanceEnables AI agents to search local Markdown documents using natural language, with automatic indexing and section-level retrieval.1012 npm1MIT
- AlicenseNot gradedqualityDmaintenanceGives AI agents full-text search over any Markdown/MDX documentation folder.10 npmMIT
- FlicenseNot gradedqualityCmaintenanceEnables agents to search a local, fully offline personal document library (Markdown/txt/PDF/docx) via SQLite FTS5 trigram search with subject-terminology expansion, returning every hit with its domain, document title, section path, and page or offset provenance. It also exposes domain statistics, incremental ingestion, and document deprecation as tools, alongside a read-only, runtime-persona-scoped ask/coverage mode.-
- AlicenseAqualityBmaintenanceIndexes local documents (PDF, Word, Markdown, text) into a SQLite database for AI agents to search and retrieve bounded, source-located passages. Runs fully locally with optional OCR, preserving privacy.5MIT
TDQS
Scored across 3 tools
Each tool targets a distinct action on the docs index: search retrieves matching sections, list enumerates documents, reindex refreshes the index. Their boundaries are crisp and the descriptions reinforce when to prefer each over grep or file reads.
All three names follow the same verb_noun snake_case pattern (search_docs, list_docs, reindex_docs) with a shared '_docs' noun suffix. Fully predictable and readable.
Three tools is small but well-matched to a focused read-only documentation index; each tool clearly earns its place. It is on the lean side, with no room to trim and one arguably missing retrieval operation.
The surface covers search, listing, and index refresh, but there is no get_document tool to fetch a full document by path from a list_docs result. Agents can only see snippets or paths, creating a dead end when full content is needed.