by jgravelle
The leading, most token-efficient MCP server for documentation exploration and retrieval via structured section indexing
# Add to your Claude Code skills
git clone https://github.com/jgravelle/jdocmunch-mcpMost AI agents still explore documentation the expensive way:
open file → skim hundreds of irrelevant paragraphs → open another file → repeat
That burns tokens, floods context windows with noise, and forces models to reason through a lot of text they never needed in the first place.
jDocMunch-MCP lets AI agents navigate documentation by section instead of reading files by brute force.
It indexes a documentation set once, then retrieves exactly the section the agent actually needs, with byte-precise extraction from the original file.
| Task | Traditional approach | With jDocMunch | | --- | ---: | ---: | | Find a configuration section | ~12,000 tokens | ~400 tokens | | Browse documentation structure | ~40,000 tokens | ~800 tokens | | Explore a full doc set | ~100,000 tokens | ~2,000 tokens |
Index once. Query cheaply forever.
Precision context beats brute-force context.
Commercial licenses
jDocMunch-MCP is free for non-commercial use.
Commercial use requires a paid license.
No comments yet. Be the first to share your thoughts!
jDocMunch-only licenses
Want both code and docs retrieval?
Stop dumping documentation files into context windows. Start navigating docs structurally.
jDocMunch indexes documentation once by heading hierarchy and section structure, then gives MCP-compatible agents precise access to the explanations they actually need instead of forcing them to brute-read files.
It is built for workflows where token efficiency, context hygiene, and agent reliability matter.
Large context windows do not fix bad retrieval.
Agents waste money and reasoning bandwidth when they: