In-depth architectural comparison of the Not Just Another Docs Tool and Minirag MCP MCP servers. Compare execution transports, security boundaries, tool capabilities, quality scores, and ready-to-paste client installation snippets for Claude, Cursor, Windsurf, and VS Code.
At a Glance & Executive Verdict
Not Just Another Docs Tool
Knowledge & Memory · Local stdio
Quality: 39/100 (Fair) | Auth: No auth required
Minirag MCP
Knowledge & Memory · Local stdio
Quality: 55/100 (Good) | Auth: No auth required
Verdict Summary: Choose Not Just Another Docs Tool if you need specialized Knowledge & Memory tools running via a local process. Choose Minirag MCP if your workspace requires Knowledge & Memory integration with local subprocess execution. Both servers can be configured concurrently in your client's mcpServers manifest.
Which MCP Server Should You Choose?
Choose Not Just Another Docs Tool when:
You need dedicated capabilities in the Knowledge & Memory domain.
You prefer local stdio subprocess transport architecture.
Your security boundary fits: No auth required (Free / Open Source).
Not Just Another Docs Tool is categorized under Knowledge & Memory and uses a local stdio subprocess. In contrast, Minirag MCP belongs to Knowledge & Memory using local stdio subprocess. Select Not Just Another Docs Tool when you need capabilities focused on knowledge & memory and Minirag MCP when you require tools for knowledge & memory.
Hybrid search: semantic similarity plus a keyword boost for exact terms. Each hit carries `text` (the passage that matched) and `parentId`; the enclosing sections come back once each in the response's `parents` map — see [Chunking](#chunking).
read_chunk_neighbors
Read the chunks immediately before and after a search result, for context.
read_file
Read a source's entire indexed content as Markdown, reconstructed from its chunks rather than concatenated from them.
list_files
List files found on disk under the document roots, plus indexed data/url sources.
delete_file
Delete an indexed file, data item, or url item from the index.
status
Report configuration and index status, including whether the index predates the current chunking scheme. Works even when configuration is invalid.