Documentation Search
概览
作者提供的说明(英文原文)
Local RAG MCP for markdown documentation. Retrieval only; host synthesizes answers.
PopNx MCP 的三大支柱
这三项永远不会合并成一个分数:意见、测量和人气是不同的东西。
- 用户评价i暂无评价评价功能将在后续阶段与账户功能一起开放
- 我们的基础检查i1 项中通过 1 项依据公开信息检查;尚未扫描代码
- 使用情况i非常新↓ 129/周 · ★ –
它能帮你做什么
我们还没有为它写通俗的介绍。下面是我们从注册中心读取到的事实。
- 连接方式: 在你的电脑上运行
- 传输方式: stdio
- 分类: 搜索与 AI 记忆
安装
选择你使用的 AI 应用,然后复制设置。
安装之前
- 基础检查:1 项中通过 1 项
- 在你的电脑上运行,拥有你的用户账户的权限(文件、网络、应用)。
- 注册中心没有列出需要填写的密钥。
你需要
- PyPI已安装 Python 的 uv(用于 uvx 命令)
你用的是哪个应用?
在上方选择你的应用。我们会记住它,下次按钮会显示“安装到 …”。
打开 Claude Desktop → Settings → Developer → Edit Config,把下面的内容粘贴到 claude_desktop_config.json
{
"mcpServers": {
"docs-ask": {
"command": "uvx",
"args": [
"mcp-docs-ask"
]
}
}
}在终端中运行这条命令
claude mcp add docs-ask -- uvx mcp-docs-ask或者自己复制设置
粘贴到项目中的 .cursor/mcp.json,或 ~/.cursor/mcp.json
{
"mcpServers": {
"docs-ask": {
"command": "uvx",
"args": [
"mcp-docs-ask"
]
}
}
}浏览器会先询问是否打开应用,然后应用会显示设置并请你确认。密钥的值会留空,由你自己填写。
或者自己复制设置
粘贴到项目中的 .vscode/mcp.json
{
"servers": {
"docs-ask": {
"type": "stdio",
"command": "uvx",
"args": [
"mcp-docs-ask"
]
}
}
}浏览器会先询问是否打开应用,然后应用会显示设置并请你确认。密钥的值会留空,由你自己填写。
这个服务器在你的电脑上运行,而 ChatGPT 只能连接互联网上的服务器。请选择其他应用。
你的选择通过 Cookie 保存在这台设备上,无需账户。
这些设置是根据作者在注册中心的条目生成的。如果 README 的写法不同,请以 README 为准。
它能做什么
它在你的电脑上运行;安装后,工具列表会显示在你的 AI 应用中。
基础检查i
我们检查的是任何人都能看到的信息;我们没有阅读代码。不适用的检查项不计入总数。 · 检查于 2026年11月8日
- ✓ 通过
作者与仓库一致
注册名称已通过 GitHub 账户 alyiox 验证,该账户拥有此仓库
- … 尚未检查
仍在维护
我们还没有从 GitHub 读取这个仓库
- … 尚未检查
有许可证
我们还没有从 GitHub 读取这个仓库
- – 不适用
端点有响应
它在你的电脑上运行,没有互联网端点
- – 不适用
使用 OAuth 登录
在你的电脑上运行,改用本地设置
- … 尚未检查
工具描述中没有隐藏指令
它在你的电脑上运行;我们只能读取互联网端点的工具列表
与“搜索与 AI 记忆”中的其他服务器比较i
- 星标数多于此分类中其他 5696 个服务器的 0%
- 发布到注册中心的时间比此分类中其他 5696 个服务器的 60% 更新
- 基础检查结果等于或优于此分类中其他 5696 个服务器的 100%
与注册中心里这个分类中所有活跃的服务器比较。只有当发布者拥有该仓库时,星标数才计入。
常见问题
Documentation Search 安全吗?
它在 1 项适用的基础检查中通过了 1 项。我们没有阅读代码。在添加密钥或令牌之前,请先看看这个服务器要求哪些权限,并使用只具备所需权限的密钥。
它需要哪些密钥或代码?
注册中心没有列出必需的密钥,不过有些服务器会在首次使用时要求你登录。
它在我的电脑上运行还是在云端?
它在你的电脑上运行。你的 AI 应用会在需要时启动它,数据不会经过作者的服务器(除非它自己调用在线服务)。
它还在维护吗?
GitHub 仓库最后更新于–,最新版本(0.4.0)于26天前进入注册中心。
哪些应用可以使用它?
支持 MCP 的应用,例如 Claude Desktop、Claude Code、Cursor 和 VS Code。你的电脑上还需要有 Python (uv)。
有什么可以替代它?
同一分类中有:Context7, Codebase Memory, Exa
替代选择
同一分类中其他作者的服务器,按星标数排序。
如何看卡片:↓ 每周下载量i★ GitHub 星标i三大支柱:评价 · 检查 · 使用情况i更新 = 最新版本发布到注册中心的时间i
Codebase Memory
Codebase knowledge graph for AI agents — 162 languages, sub-ms queries, 99% fewer tokens.
Exa
Connect AI agents to Exa for web search, content fetching, and multi-step research.
作者的 README
打开 README
按原文从作者的仓库复制。PopNx MCP 没有审查或背书其内容。HTML、图片和脚本已被移除。链接会离开本站。
mcp-docs-ask
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
git clone git@github.com:alyiox/mcp-docs-ask.git
cd mcp-docs-ask uv sync mkdir -p ~/.config/mcp-docs-ask cp config.example.json ~/.config/mcp-docs-ask/config.json
Prefer a local checkout while developing:
set docs. .source to your docs repo path
npx -y @modelcontextprotocol/inspector@latest uv run mcp-docs-ask
Configuration
Config path: ~/.config/mcp-docs-ask/config.json
Windows:
%USERPROFILE%\.config\mcp-docs-ask\config.json
{
"docs": { "product": { "source": "https://github.com/example/docs.git", "desc": "Product guides and API reference", "ref": "main", "include": ["**/*.md"], "exclude": ["archive/"], "layers": { "guides": { "desc": "How-to and onboarding guides", "include": ["docs/guides/"] }, "api": { "desc": "HTTP API reference", "include": ["docs/api/"] } }, "embedding_model": "sentence-transformers/all-MiniLM-L6-v2" }, "team-notes": { "source": "/path/to/docs", "desc": "Internal team notes (local path; ref unused)", "include": ["/*.md"], "exclude": ["archive/**"] } }, "default": { "docs": "product", "embedding_model": "sentence-transformers/paraphrase-multilingual-MiniLM-L12-v2", "top_k": 8, "chunk_max_chars": 1500, "max_context_chars": 8000 } }
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. .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:
| Docs / queries | Recommended embedding_model |
|---|---|
| English-only (built-in when omitted) | sentence-transformers/all-MiniLM-L6-v2 |
| Chinese-only | BAAI/bge-small-zh-v1.5 |
| Multilingual (~50 langs) | sentence-transformers/paraphrase-multilingual-MiniLM-L12-v2 |
Changing embedding_model rebuilds the index on the next call; no reindex needed.
| Field | Description |
|---|---|
docs. .source | Docs repo root: local path or git URL |
docs. .desc | Short description for discovery (list_docs) |
docs. .ref | Branch / tag / SHA for git URL sources only (default main; ignored for local paths) |
docs. .include | Globs relative to repo root (default **/*.md) |
docs. .exclude | Globs to skip |
docs. .layers. .include | Path globs for that layer (first match wins) |
docs. .layers. .desc | Short layer description for discovery |
docs. .embedding_model | Optional override (see recommendation above) |
docs. .top_k | Optional override for default retrieval count |
docs. .chunk_max_chars | Optional override for max body chars per heading chunk |
docs. .max_context_chars | Optional override for the answer_context passage budget |
default.docs | Default docs collection id |
default.embedding_model | Default sentence-transformers model id |
default.top_k | Default retrieval count |
default.chunk_max_chars | Default max body chars per heading chunk |
default.max_context_chars | Default total passage chars in answer_context (min 500) |
Layers partition indexed files by path glob. First match wins. Names are case-insensitive; all is reserved (cannot be configured as a layer name).
ask_docs layer | Meaning |
|---|---|
all (default) | Every indexed chunk (named layers and paths outside them) |
| Only chunks whose path matched that named layer’s include globs |
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/ / - Indexes:
~/.cache/mcp-docs-ask/indexes/ /
Tools
| Tool | Description |
|---|---|
list_docs | List configured docs collections, layer filters, and index state |
ask_docs | Retrieve grounded passages + citations (layer: all or a named layer) |
reindex | Sync git source (if URL) and rebuild the vector index |
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/ / 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:
/home/you/docs-repo + product/features/budget.md
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:
$ uvx mcp-docs-ask
Installed 84 packages in 275ms
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 ~15
nvidia-*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 first
uvxrun to take minutes, not milliseconds.
Cursor
Add to .cursor/mcp.json:
{
"mcpServers": { "docs-ask": { "command": "uvx", "args": ["mcp-docs-ask"] } } }
Claude Code
Add to your Claude Code MCP config:
{
"mcpServers": { "docs-ask": { "command": "uvx", "args": ["mcp-docs-ask"] } } }
Codex
[mcp_servers.docs-ask]
command = "uvx" args = ["mcp-docs-ask"]
OpenCode
{
"$schema": "https://opencode.ai/config.json", "mcp": { "docs-ask": { "type": "local", "enabled": true, "command": ["uvx", "mcp-docs-ask"] } } }
GitHub Copilot
{
"inputs": [], "servers": { "docs-ask": { "type": "stdio", "command": "uvx", "args": ["mcp-docs-ask"] } } }
Development
uv sync
uv run ruff check src/ tests/ uv run ruff format --check src/ tests/ uv run pyright uv run pytest
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.