原型 · 预览版:收录官方注册中心里的全部服务器,每 30 分钟同步一次。使用 Google 登录即可撰写评价。原型 · 每 30 分钟更新
PopNx MCP为使用 AI 的人准备的 MCP 服务器 · 用大白话讲清楚

quillrag

注册名称io.github.Ayush-yadav11/quillrag

安装方法

What it does

Single-binary local RAG MCP server in Rust. MiniLM compiled in, hybrid search, zero deps.

  • Connects –
  • Account or key No key needed
  • Category 搜索与 AI 记忆

可搭配使用

教 AI 做这类工作的 Skill,可与本项一起使用

timesfm

TimesFM (Time Series Foundation Model) is a pretrained time-series foundation model developed by Google Research for time-series forecasting.

作者:google-research★ 35,6291 个 skill

Skill · 操作手册

Shadowbroker

Open-source intelligence for the global theater. Track everything from the corporate/private jets of the wealthy, and spy satellites, to seismic events in one unified interface. Hook an AI agent up to have it parse through data and find previously unseen correlations. The knowledge is available to…

作者:BigBodyCobain★ 11,6021 个 skill

Skill · 操作手册

google-maps-scraper

scrape data from Google Maps. Extracts data such as the name, address, phone number, website URL, rating, reviews number, latitude and longitude, reviews,email and more for each place

作者:gosom★ 8,2091 个 skill

Skill · 操作手册

为什么排在这里

列表按使用分(满分 100)排序,由以下部分组成

热度7/80GitHub 星标或每周下载量:较大的计 60,较小的计 20
新鲜度7/1230 天内有发布或代码更新得满分
仍在响应0/8上次检查时云端端点有响应
使用分14/100

质量: 基础检查通过 3/3 项(仅展示,不用于排序) · 上升势头: 暂无数据 (只用于“上升中”标签)

安装

选择你使用的 AI 应用,然后复制设置。

通过 3/3 项检查 · 在你的电脑上运行

第一步:你用哪个 AI?

选择你用的应用,步骤会显示在下方。

Claude 暂时无法连接 quillrag

开发者尚未在 MCP 注册表中填写安装方式

ChatGPT 暂时无法连接 quillrag

开发者尚未在 MCP 注册表中填写安装方式

你可以改用这些方式

B · 搜索与 AI 记忆 类中能连接 ChatGPT 的其他服务器

从同类中使用较多的里挑选,仅限用地址即可连接、无需密钥的

Claude Code 暂时无法连接 quillrag

开发者尚未在 MCP 注册表中填写安装方式

Cursor 暂时无法连接 quillrag

开发者尚未在 MCP 注册表中填写安装方式

VS Code 暂时无法连接 quillrag

开发者尚未在 MCP 注册表中填写安装方式

其他支持 MCP 的应用(如 Windsurf、Zed、Gemini CLI)添加方式各不相同,请在应用列表中查看

查看所有支持 MCP 的应用 →

JSON 设置在下方“开发者专用”中

卡住了?问问正在用 quillrag 的人💬 讨论 →

一览

每周下载量i
不在 npm/PyPI 上
连接方式
–
最新版本i
0.1.3
发布到注册中心i
2026年8月27日
代码最后更新i
2026年9月28日
作者
Ayush-yadav11
注册状态
活跃

它能做什么

它在你的电脑上运行;安装后,工具列表会显示在你的 AI 应用中。

基础检查i

我们检查的是任何人都能看到的信息;我们没有阅读代码。不适用的检查项不计入总数。 · 检查于 2026年11月19日

  • ✓ 通过

    作者与仓库一致

    注册名称已通过 GitHub 账户 Ayush-yadav11 验证,该账户拥有此仓库

  • ✓ 通过

    仍在维护

    代码最后更新于2个月前

  • ✓ 通过

    有许可证

    使用 MIT

  • – 不适用

    端点有响应

    它在你的电脑上运行,没有互联网端点

  • – 不适用

    使用 OAuth 登录

    在你的电脑上运行,改用本地设置

  • … 尚未检查

    工具描述中没有隐藏指令

    它在你的电脑上运行;我们只能读取互联网端点的工具列表

我们检查什么 → · JSON

作者:申请重新检查或报告信息错误
给作者:在 README 中加徽章

如果你是作者,可把这段代码贴到 README。徽章会链接回本页。

[![Featured on PopNx MCP](https://mcp.popnx.com/badge/ayush-yadav11-quillrag.svg)](https://mcp.popnx.com/en/servers/ayush-yadav11-quillrag)

讨论

提问、分享技巧或报告无法使用。按“有帮助”数量排序。

还没有帖子,欢迎第一个提问或分享。

此处内容由用户撰写,不代表 PopNx 团队。

登录后发帖

用户评价

还没有评价

登录后写评价

与“搜索与 AI 记忆”中的其他服务器比较i

  • 星标数多于此分类中其他 6394 个服务器的 86%
  • 发布到注册中心的时间比此分类中其他 6394 个服务器的 30% 更新
  • 基础检查结果等于或优于此分类中其他 6394 个服务器的 99%

与注册中心里这个分类中所有活跃的服务器比较。只有当发布者拥有该仓库时,星标数才计入。

常见问题

quillrag 安全吗?

它在 3 项适用的基础检查中通过了 3 项。我们没有阅读代码。在添加密钥或令牌之前,请先看看这个服务器要求哪些权限,并使用只具备所需权限的密钥。

它需要哪些密钥或代码?

注册中心没有列出必需的密钥,不过有些服务器会在首次使用时要求你登录。

它在我的电脑上运行还是在云端?

它在你的电脑上运行。你的 AI 应用会在需要时启动它,数据不会经过作者的服务器(除非它自己调用在线服务)。

它还在维护吗?

GitHub 仓库最后更新于2个月前,最新版本(0.1.3)于3个月前进入注册中心。

哪些应用可以使用它?

支持 MCP 的应用,例如 Claude Desktop、Claude Code、Cursor 和 VS Code。

有什么可以替代它?

同一分类中有:OpenSEO, Exa, Microsoft Learn MCP, Docs, COTAL actions (cotal.ai)

功能相近的其他选择

同一分类、其他作者、命令已通过检查。官方的排在前面,再按星标排序。

如何看卡片:↓ 每周下载量i★ GitHub 星标i三大支柱:评价 · 检查 · 使用情况i更新 = 最新版本发布到注册中心的时间i

OpenSEO

Keyword research, site audits, rank tracking and AI visibility for your AI agent.

作者:every-app广泛使用★ 2.8万5天前更新

在云端运行✓ everyapp.com

Exa

Connect AI agents to Exa for web search, content fetching, and multi-step research.

作者:exa-labs广泛使用★ 52422个月前更新

在云端运行✓ 服务方 · exa.aiPopNx 团队已实际试用

Microsoft Learn MCP

Official Microsoft Learn MCP Server – real-time, trusted docs & code samples for AI and LLMs.

作者:MicrosoftDocs广泛使用★ 199712个月前更新

在云端运行✓ 服务方 · microsoft.comPopNx 团队已实际试用

Docs

Search and read Empryo's documentation. Read-only, no auth, no local access.

作者:proxysoul正在增长★ 16262个月前更新

在云端运行✓ empryo.com
与相似项目对比
本项
quillrag
OpenSEOExaMicrosoft Learn MCPDocsCOTAL actions (cotal.ai)
运行位置需要安装在电脑上在云端运行,无需安装在云端运行,无需安装在云端运行,无需安装在云端运行,无需安装在云端运行,无需安装
需要密钥否否否否否否
可在 Claude 中按 + 添加否是是是否否
基础检查3/35/52/44/44/44/4
许可证MITMITMITCC-BY-4.0NOASSERTIONApache-2.0
价格登记中未列出费用登记中未列出费用登记中未列出费用登记中未列出费用登记中未列出费用登记中未列出费用

作者的 README

打开 README

按原文从作者的仓库复制。PopNx MCP 没有审查或背书其内容。HTML、图片和脚本已被移除。链接会离开本站。

quillrag

One file. Zero dependencies. Ready before your editor finishes loading.

A local RAG engine in a single static binary — MiniLM embeddings compiled inside, hybrid dense + BM25 retrieval, MCP-native. No Node, no Python, no model download on first query.


Why quillrag

~20 ms to readyMCP handshake completes before the model even loads
Zero runtime depsno Node, no Python, no pip/npm, no model downloads — ever
Hybrid retrievaldense cosine ⊕ BM25 fused with Reciprocal Rank Fusion
Private by constructionno network code path after installation
One file, three OSes~105 MB (the model lives inside), CI-built for linux/macOS/Windows

Quick start

# 1. grab a prebuilt binary (or cargo install --path .)

gh release download --repo Ayush-yadav11/quillrag -p '*linux*' tar xzf quillrag-x86_64-linux.tar.gz && chmod +x quillrag

2. point it at any folder of notes/docs/code

./quillrag index ~/notes # incremental walk

3. ask it something

./quillrag search "how does backpropagation work"

Or wire it straight into Claude Desktop / Cursor and let the AI search your notes mid-conversation — config below.

$ ./quillrag serve --data-dir ~/.local/share/quillrag

2026-08-26 INFO quillrag 0.1.2 ready in 41ms <- handshake-ready before the model loads

Why it's fast

StageCost
Binary start + MCP initialize~20 ms (measured: store open + tool registration only)
First rag_search / rag_index call+~300 ms one-time (mmap safetensors, build BERT graph)
Subsequent searches~25 ms per query (2-core CPU, small corpus)
Re-indexing unchanged corpusnear-zero (FNV content hash skip)

The embedding model is *lazy*: the MCP handshake and rag_status never touch it, so editors see an instant server.

Install

Download a prebuilt archive from the latest release — Windows x86_64, macOS Apple Silicon, and Linux x86_64 are all built by CI on every version tag:

# linux/macOS example: fetch + extract the latest release

gh release download --repo Ayush-yadav11/quillrag -p '*linux*' | tar xz chmod +x quillrag && ./quillrag --version

Linux requirement: v0.1.6 binaries are built on Ubuntu 24.04 runners and

link glibc 2.39 (pidfd_spawnp/pidfd_getpid). On older distros (glibc

< 2.39, e.g. Ubuntu 22.04), build from source with your local toolchain

instead: cargo install --path ..

Or build from source:

cargo install --path .

Cross-compile targets used by CI: x86_64-unknown-linux-gnu, aarch64-apple-darwin, x86_64-pc-windows-msvc.

Wire it into your editor

Claude Desktop / Cursor / any MCP client:

{

"mcpServers": { "quillrag": { "command": "/usr/local/bin/quillrag", "args": ["serve"], "env": { "QUILLRAG_DATA": "~/.local/share/quillrag" } } } }

Or just run ./quillrag serve and point any stdio client at it.

Tools

ToolWhat it does
rag_indexIncrementally index a directory/file. Skips unchanged files, re-embeds only diffs. Pruning is scoped to the directory you pass: docs indexed from other roots are untouched. Symlinked files/dirs are followed.
rag_searchHybrid retrieval: dense MiniLM cosine + BM25 keyword, fused with Reciprocal Rank Fusion. Returns ranked chunks with source paths.
rag_statusDocument/chunk counts, bytes indexed, file-type breakdown.
rag_clearWipe everything.

CLI equivalents (same engine):

quillrag index ~/notes              # incremental walk

quillrag search "auth flow" -k 5 # one-shot search quillrag status # stats quillrag clear # wipe

Design

  • Embeddings: candle (pure Rust) running sentence-transformers/all-MiniLM-L6-v2 — masked mean pooling + L2 norm, numerically matching sentence-transformers on CPU. Weights are include_bytes!-ed into the binary and mmap'd from a materialized cache on first load.
  • Storage: single redb file — chunk text, raw f32 vectors, document metadata. Atomic commits; crash-safe.
  • Keywords: tantivy BM25 sidecar index rebuilt per indexing pass (cheap at pocket scale).
  • Fusion: Reciprocal Rank Fusion (Σ 1/(60+rank)) — no score-scale tuning, robust to heterogeneous rankings.
  • Chunking: paragraph-first with 1000-char cap and 120-char overlap; oversized paragraphs hard-split at sentence boundaries.
File types indexed by default

md markdown txt rst json yaml yml toml csv tsv html htm xml log rs py js jsx ts tsx go c h cpp hpp java rb sh bash zsh sql proto graphql dockerfile makefile ini cfg conf env — extend with -e ext1,ext2 / "extensions": [...].

Ignored dirs: every dot-directory (.git .obsidian .vscode …) plus node_modules target dist build venv __pycache__ vendor.

Optional formats (library features)

Applications embedding the engine (default-features = false) can index more through IndexHooks extractors:

FeatureAdds
pdfPdfExtractor: text-layer PDFs, one section per page; hits carry page.
ocrOcr, ImageExtractor (png/jpg/webp/bmp/gif) and OCR of scanned PDF pages via PdfExtractor::with_ocr. Bundles the ocrs models (~12 MB, CC BY-SA 4.0, see assets/ocr/NOTICE.md); English / basic Latin text only.

Files that are readable but contain no text are recorded as empty documents, so unchanged ones are not re-OCR'd on every pass (IndexOptions::retry_empty re-checks them).

Indexing behavior
quillrag index ~/notes              # incremental walk of one root

quillrag index ~/notes --no-prune # add/update without deleting anything quillrag index ~/notes --force # re-embed this root, preserve other roots

  • Pruning is scoped to the index root. Docs indexed from ~/work-docs survive a later quillrag index ~/personal-notes against the same data dir. Only files that lived under the directory being walked and have since disappeared get pruned. Existing files excluded by extensions or size stay indexed. --no-prune disables deletion, including through MCP's no_prune. --force re-embeds only the selected sources. Use clear explicitly to wipe a store. An empty successful scan warns and may prune that root's last file.
  • Symlinks are followed. Staging trees built from symlinked source dirs index normally. Cycles, broken links, and unreadable directories abort the walk before changing the store. Paths retain symlink aliases, so indexing both an alias and its target creates separate entries.
  • Progress is logged per 128-chunk embedding batch (stderr), so a long CPU indexing run is visibly alive.
Upgrading existing indexes

Older batched indexing could associate document paths with the wrong chunks. The fix cannot reconstruct those associations from the stored index alone. Build a fresh data directory from your source files, verify search results, then switch your client to it. Keep the old directory until verification passes. This also removes legacy relative-path keys, which the new indexer preserves rather than guessing their original working directory. New keys are absolute. Paths containing .. resolve through the filesystem; use a stable spelling for symlink-based roots. Re-indexing refreshes the BM25 sidecar as well.

Privacy & footprint

Everything runs locally: embeddings, storage, search. Nothing leaves the machine — there is no network code path at all after installation.

Binary ≈ 105 MB (the model lives inside). RAM ≈ 120 MB resident while idle, spiking to ~250 MB during batch embedding.

Scaling & limits

quillrag stores everything in a single redb file and runs dense retrieval as an exact, single-threaded linear scan over all vectors — no ANN index yet. That makes the relevant limit *query latency*, not storage. Storage scales to millions of chunks; retrieval speed is O(N) per query.

CorpusVectorsApprox. RAM (f32)Steady-state query
1K chunks1K~1.5 MB~25 ms (measured)
10K chunks10K~15 MB~250 ms (extrapolated)
100K chunks100K~154 MB~2–5 s (extrapolated)
1M chunks1M~1.5 GB20–60 s (extrapolated — not viable without ANN)

Verified on a corpus of 1K chunks (5/5 tests including real JSON-RPC-over-stdio e2e); figures above 1K are extrapolated from the O(N) dense-scan cost, not measured. A synthetic scale probe (src/bin/quillbench.rs) exists to measure the curve on your own hardware — run cargo build --release && ./target/release/quillbench.

What this means in practice:

  • Great fit: personal/local knowledge bases, project docs, notes, code — up to low-tens-of-thousands of chunks where sub-second-to-interactive latency holds.
  • Away from the sweet spot: corpora in the hundreds of thousands+ where you need interactive (<200 ms) retrieval — you'll want an ANN index (see Roadmap).

How it compares to common alternatives on the *relevance* axis:

  • Embedding-only (e.g. raw FAISS flat / simple vector store): same all-MiniLM-L6-v2 ceiling as quillrag's dense path, but quillrag adds BM25 + RRF fusion, which wins on keyword-heavy queries (error codes, IDs, exact tokens). quillrag has no reranker or metadata filtering, which llama-index offers on top.
  • llama-index local backends: functionally similar hybrid retrieval (BM25 + vector + RRF). quillrag trades llama-index's rich reranking/parent-child chunking/query-expansion for a zero-dependency single binary and instant startup. Relevance on a standard dataset (BEIR/MS MARCO) is not yet benchmarked — see the open issue tracking ANN + a relevance baseline.

Roadmap

quillrag is deliberately minimal today. The big unlock is an approximate nearest-neighbor index:

  • ANN (HNSW / IVF) over the dense vectors — turns O(N) scan into sub-millisecond ANN lookup, pushing the interactive ceiling from ~10K to millions of chunks on a single machine.
  • Quantization (PQ / SQ) — drops vector RAM from 4 bytes/dim to ~1 byte/dim, so 1M chunks ≈ 380 MB instead of 1.5 GB.
  • Multi-threaded scan — parallelize the current exact path as a stopgap.
  • Reranker hook — optional cross-encoder rerank of the fused top-k.
  • Relevance benchmark — BEIR / MS MARCO nDCG@10 vs. llama-index baselines.

Track the ANN work here: issue #1 — "ANN index for <1M chunks."

FAQ

Is it really one file? Yes. The MiniLM weights + tokenizer are compiled in via include_bytes!. No npm install, no Python, no model download on first query. The binary is ~105 MB because the model lives inside it.

Why is startup so fast? The embedding model is *lazy*. The MCP handshake and rag_status never touch it — editors see a ready server in ~20 ms. The model only loads on the first rag_search / rag_index (~300 ms one-time).

What's the largest corpus it handles? Verified at 1K chunks (~25 ms/query). The architecture scales to millions of stored chunks; interactive retrieval holds up to low-tens-of-thousands today, and an ANN index (Roadmap) extends that to 1M+.

How is this different from llama-index? Similar hybrid r

只显示了开头部分;其余内容请在仓库中阅读