
Documentation Search
io.github.alyioxPublished by GitHub account alyioxv0.4.0Updated Oct 24, 2026
Local RAG MCP for markdown documentation. Retrieval only; host synthesizes answers.
Overview
Local RAG server that indexes markdown documentation repos and returns grounded passages with citations for the host assistant to answer from.
- What you can do
- List configured documentation collections, their layer filters and index state
- Retrieve grounded passages with heading paths and numbered citations from a chosen collection or layer
- Sync a git source and rebuild the vector index on demand
- Index local paths or git URLs, with automatic rebuild when files, config or the embedding model change
- When to use it
- Useful when you want an assistant to answer questions from a specific markdown documentation repo, such as product guides or an API reference, and cite the source passages instead of relying on general knowledge.
- Requirements
- Runs locally over stdio via uvx; needs Python 3.13+ and uv. git on PATH only for git URL sources, plus existing git credentials for private repos. A config file at ~/.config/mcp-docs-ask/config.json defines the collections. First run downloads sentence-transformers embedding model weights; on Linux the torch wheel pulls large CUDA packages.
Installation
In SourceWeft
- Open Documentation Search in the dashboard and add it to a workspace.
- Enable the server for the chats that should use its tools.
Desktop only via STDIO. STDIO servers start a local process, so they need the SourceWeft desktop host.
Other MCP clients
Follow the launch instructions in the repository.
README
mcp-docs-ask
[CI] [PyPI] [Python 3.13+] [License: MIT]
Local RAG MCP for documentation. Point source at any markdown repository
(local path or git URL).
The server does retrieval only (no answer LLM). ask_docs returns grounded
passages and citations; the MCP host (Cursor / Claude) synthesizes the answer.
Features
- Any markdown repo as a source: a local path, or a git URL fetched on
reindex - Runs locally: sentence-transformers embeddings, no API keys, no answer LLM
- Path-based layers to narrow a search (e.g. guides vs. API reference)
- Full passages with heading paths and
[n]citations, capped by a character budget - No manual rebuilds: the index refreshes itself when local files, config, or the embedding model change
Requirements
- Python 3.13+
uvgiton PATH (only ifsourceis a git URL)- Git credentials on the machine when
sourceis a private git URL (gh auth login, HTTPS credential helper, or SSH). No tokens in config. - First run downloads the embedding model weights once (sentence-transformers)
Quick start
Configuration
Config path: ~/.config/mcp-docs-ask/config.json
Windows:
%USERPROFILE%\.config\mcp-docs-ask\config.json
product is a git URL (ref applies). team-notes is a filesystem path (ref unused).
Optional desc on each docs collection and layer helps agents pick the right target.
embedding_model, top_k, chunk_max_chars, and max_context_chars resolve as:
docs.<id>.X → default.X → built-in. Omit per-docs keys to inherit.
Embedding model recommendation
Any Hugging Face id loadable by sentence-transformers works. Pick by language mix:
Changing embedding_model rebuilds the index on the next call; no reindex needed.
Layers partition indexed files by path glob. First match wins. Names are
case-insensitive; all is reserved (cannot be configured as a layer name).
Paths that match no named-layer glob are still indexed and only appear under
layer=all. Omit layers (or set "layers": {}) for flat repos — use
layer=all.
Cache layout:
- Repos (git URL):
~/.cache/mcp-docs-ask/repos/<docs-id>/ - Indexes:
~/.cache/mcp-docs-ask/indexes/<docs-id>/
Tools
list_docs returns a default block with the same keys as the config default
block (docs, embedding_model, top_k, chunk_max_chars,
max_context_chars), plus a docs list where each entry carries its resolved
values, a default flag, and an index block (null when the collection has
never been indexed). Valid layer values are all plus the named layer ids —
see Layers above.
Index block
list_docs and reindex return the same index keys: origin, root, rev,
files, chunks, layers.
origin mirrors the configured source: file for a filesystem path, git for
a URL the server clones into ~/.cache/mcp-docs-ask/repos/<docs-id>/ and
fetches on reindex. root is where the files actually are — null only when
a built index outlived its source directory. rev is the checkout HEAD when
there is one, so a file source that is itself a git clone still reports one;
its working tree may hold uncommitted edits, so rev labels the checkout, not
the exact indexed content.
ask_docs carries only the two answer-scoped keys, root and rev: the
checkout that produced the passages, and the revision they came from.
Passages
ask_docs retrieves up to top_k chunks, then assembles them into passages:
- Each passage is the full chunk text, with line breaks kept, labeled with its
heading path (
Guide > Configuration > Layers). - Retrieved parts of one oversized section are joined back in file order;
…marks parts in between that did not rank. - Passages fill
max_context_charsbest-first. The one that overflows is trimmed at a line break and ends with…; the first passage is always kept.
So citations can hold fewer entries than top_k.
Reading a full source file
citations[].path is repo-relative and stable; answer_context holds the
passage text once, keyed by the [n] markers that match citations[].n. To read
a whole source file, join index.root from the same ask_docs response with a
citation path:
Take root from the response that produced the citations rather than an earlier
reindex — ask_docs rebuilds a stale index itself, so its rev is the one
that matches the passages in hand.
MCP host examples
The examples below launch the server with uvx, which installs the package on first
use. Run it once in a terminal beforehand so your host does not block on that install:
The server then starts on stdio and waits for input — press Ctrl-C once you see the
install line. Embedding model weights are fetched separately, on the first ask_docs
or reindex call. uvx mcp-docs-ask --version prints the build uvx resolved.
Linux (including WSL, containers, and CI): the PyPI
torchwheel for Linux is the CUDA build. It pulls ~15nvidia-*packages whether or not the machine has an NVIDIA GPU — about 2.7 GB of wheels and ~4 GB on disk. Windows and macOS resolve to a CPU-only wheel (~1 GB) and never download CUDA. Pre-warming matters most here: expect the firstuvxrun to take minutes, not milliseconds.
Cursor
Add to .cursor/mcp.json:
Claude Code
Add to your Claude Code MCP config:
Codex
OpenCode
GitHub Copilot
Development
Notes
- Local path:
ask_docsrebuilds the index automatically when file mtimes/sizes change (fingerprint check). You do not needreindexafter editing local docs. - Git URL:
ask_docsnever fetches. Callreindextogit fetchthe configuredrefand rebuild. - The fingerprint also covers
embedding_model,chunk_max_chars, layer globs, and the on-disk index format, so changing any of them rebuilds on the next call.
Source: README.md at commit 379ea60
Tools
0Version history
2- v0.4.0LatestOct 13, 2026
- v0.3.0Sep 16, 2026
Score
50% of the applicable checks met
How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.
- Reached in the last 30 days25 pts
Keep the endpoint answering the MCP handshake; SourceWeft probes it every 30 days.
- Auth declared10 pts
Declare the credential headers in the registry entry, or keep the endpoint answering the probe so its auth can be classified.
- Tools listed15 pts
Answer tools/list without a credential, or ship a package that starts in a sandbox without one.
- DescriptionRequired15 pts
- Logo10 pts
- Documentation15 pts
- License10 pts