MarkIndex
Related Servers
Alternatives to MarkIndex
No user-submitted related servers found.
Related Servers
- AlicenseNot gradedqualityDmaintenanceEnables agentic document retrieval over markdown, CSV, and JSONL using BM25 and tree navigation, without vector databases or embeddings, allowing AI agents to search, browse, and retrieve structured document sections.39 npm1MIT
- AlicenseAqualityBmaintenanceEnables AI agents to search local Markdown documents using natural language, with automatic indexing and section-level retrieval.1017 npm1MIT
- FlicenseAqualityAmaintenanceLets AI agents navigate documentation by section instead of reading files by brute force, reducing token usage and improving precision.64898 PyPI207-

docs-mcpofficial
AlicenseAqualityBmaintenanceLets AI agents search and read a folder of Markdown documentation at query time, exposing heading-level search, whole-page or section retrieval, and page listing as tools and resources over stdio or Streamable HTTP. Can run as a CLI, a hosted endpoint, or a library inside an existing Node or Next.js site.3475 npm1MIT- AlicenseNot gradedqualityBmaintenanceEnables AI agents to search, read, and traverse a local knowledge base of Markdown files using full-text search and relationship graph, reducing token usage.MIT
- AlicenseAqualityCmaintenanceEnables AI agents to search a local folder of Markdown, AsciiDoc, and text files through a SQLite FTS5 keyword index, returning the most relevant sections with file paths, line ranges, and heading breadcrumbs instead of grepping through a repo. It also exposes tools to list indexed documents and refresh the index incrementally, all offline with no dependencies, network calls, or embeddings.3MIT
TDQS
Scored across 5 tools
Each tool maps to a distinct step in a read-only workflow: folder browsing, document metadata, section outline, node content, and keyword search. The descriptions explicitly state the escalation order (browse before search, structure before reading large docs), so even the adjacent pair get_document/get_document_structure is clearly separated by 'metadata' vs 'outline'.
All names follow a snake_case verb_noun pattern (browse_documents, get_document, get_document_structure, get_node_content, search_documents). The verbs are meaningful and the noun targets (documents/document/node) are used consistently.
Five tools is tightly scoped for a read-only Markdown library: discovery, inspection, outlining, reading, and search. No tool appears redundant and none feels like it is missing from the minimal set.
The read lifecycle is fully covered with no dead ends: browse, check metadata, get structure, read content, and search, with pagination handled throughout. Minor gaps exist for a document library — no frontmatter/tag-based filtering or cross-document listing beyond folders, and no way to read a whole small document in one plain-text call without walking nodes.