Prototype · Preview: every server in the official registry, synced every 30 minutes. Sign in with Google to write reviews.Prototype · updated every 30 min
PopNx MCPMCP servers for people who use AI · explained in plain words

quillrag

Registry nameio.github.Ayush-yadav11/quillrag

How to install

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 Search & AI memory

Use together with

Skills that teach the AI this kind of work; they work alongside this one

timesfm

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

by google-research★ 35,6291 skills

Skill · How-to guide

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…

by BigBodyCobain★ 11,6021 skills

Skill · How-to guide

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

by gosom★ 8,2091 skills

Skill · How-to guide

Why it ranks here

Lists are ordered by a usage score (out of 100) built from these parts

Popularity7/80GitHub stars or weekly downloads: the larger counts 60, the smaller 20
Freshness7/12Full marks for a release or code change within 30 days
Still answering0/8The cloud endpoint answered at the last check
Usage score14/100

Quality: Passed 3/3 basic checks (shown, not used for ordering) · Momentum: No data yet (Used only on the Trending tab)

Install

Pick the AI app you use, then copy the settings.

Passed 3/3 checks · Runs on your computer

First: which AI do you use?

Pick your app and the steps appear below.

Claude cannot connect quillrag yet

The maker has not listed install details in the MCP Registry yet

ChatGPT cannot connect quillrag yet

The maker has not listed install details in the MCP Registry yet

What you can do instead

B · Others in Search & AI memory that work with ChatGPT

Picked from the most used in the same category, only ones that connect by address with no key

Claude Code cannot connect quillrag yet

The maker has not listed install details in the MCP Registry yet

Cursor cannot connect quillrag yet

The maker has not listed install details in the MCP Registry yet

VS Code cannot connect quillrag yet

The maker has not listed install details in the MCP Registry yet

Other apps that use MCP, such as Windsurf, Zed or Gemini CLI, each add servers differently. See how in the app list.

See every app that uses MCP →

JSON settings are under “For developers” below

Stuck? Ask people who use quillrag💬 Discussion →

At a glance

Downloads per weeki
Not on npm/PyPI
Connection
–
Latest versioni
0.1.3
Published to registryi
Aug 27, 2026
Code last changedi
Sep 28, 2026
Maker
Ayush-yadav11
Registry status
Active

Related guides

What it can do

Runs on your computer; the tool list appears in your AI app after you install it.

Basic checksi

We check information anyone can see; we have not read the code. Checks that do not apply are left out of the count. · Checked Nov 19, 2026

  • ✓ Pass

    Maker matches the repo

    The registry name was verified with the GitHub account Ayush-yadav11, which owns the repo

  • ✓ Pass

    Still maintained

    Code last changed 2 months ago

  • ✓ Pass

    Has a licence

    Uses MIT

  • – Not applicable

    Endpoint responds

    This one runs on your computer; there is no internet endpoint

  • – Not applicable

    Sign-in with OAuth

    Runs on your computer and uses local settings instead

  • … Not checked yet

    No hidden instructions in tool descriptions

    Runs on your computer; we can only read tool lists from internet endpoints

What we check → · JSON

Makers: ask for a re-check or report wrong info
For makers: add a badge to your README

If you made this, paste this code into your README. The badge links back to this page.

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

Discussion

Ask, share a tip or report that it does not work. Sorted by what people marked helpful.

No posts yet. Be the first to ask or share.

Posts here are written by users, not the PopNx team.

Sign in to post

User reviews

No reviews yet

Sign in to write a review

Compared with others in Search & AI memoryi

  • More stars than 86% of the other 6384 servers in this category
  • Published to the registry more recently than 30% of the other 6384 servers in this category
  • Basic checks equal to or better than 99% of the other 6384 servers in this category

Compared with every active server in this category in the registry. Stars count only when the publisher owns the repo.

Common questions

Is quillrag safe?

It passed 3 of 3 applicable basic checks. We have not read the code. Before adding a key or token, see what access the server asks for and use a key with only the permissions you need.

What keys or codes does it need?

The registry does not list a required key, though some servers ask you to sign in on first use.

Does it run on my computer or in the cloud?

It runs on your computer. Your AI app starts it when needed, and data does not pass through the maker’s servers (unless it calls an online service itself).

Is it still maintained?

The GitHub repo last changed 2 months ago, and the latest version (0.1.3) reached the registry 3 months ago.

Which apps can use it?

Apps that support MCP, such as Claude Desktop, Claude Code, Cursor and VS Code.

What can I use instead?

In the same category: OpenSEO, Exa, Microsoft Learn MCP, Docs, COTAL actions (cotal.ai)

Similar alternatives

Same category, other makers, commands already checked. Official ones first, then by stars.

Reading a card:↓ Downloads per weeki★ GitHub starsiThree pillars: reviews · checks · usageiUpdated = latest version published to the registryi

OpenSEO

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

by every-appWidely used★ 28.2KUpdated 5 days ago

Runs in the cloud✓ everyapp.com

Exa

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

by exa-labsWidely used★ 5.2KUpdated 2 months ago

Runs in the cloud✓ service owner · exa.aiTried by the PopNx team

Microsoft Learn MCP

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

by MicrosoftDocsWidely used★ 2KUpdated 12 months ago

Runs in the cloud✓ service owner · microsoft.comTried by the PopNx team

Docs

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

by proxysoulGrowing★ 1.6KUpdated 2 months ago

Runs in the cloud✓ empryo.com
Compared with similar ones
This one
quillrag
OpenSEOExaMicrosoft Learn MCPDocsCOTAL actions (cotal.ai)
Runs whereInstalls on your computerRuns in the cloud, nothing to installRuns in the cloud, nothing to installRuns in the cloud, nothing to installRuns in the cloud, nothing to installRuns in the cloud, nothing to install
Needs a keyNoNoNoNoNoNo
Add with + in ClaudeNoYesYesYesNoNo
Basic checks3/35/52/44/44/44/4
LicenseMITMITMITCC-BY-4.0NOASSERTIONApache-2.0
PriceNo cost listed in the registryNo cost listed in the registryNo cost listed in the registryNo cost listed in the registryNo cost listed in the registryNo cost listed in the registry

README from the maker

Open the README

Copied from the maker’s repo as written. PopNx MCP has not reviewed or endorsed it. HTML, images and scripts are removed. Links lead off this site.

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

Only the beginning is shown; read the rest in the repo