J
jcode-works/ragmir
Cited retrieval for coding agents and the RAG systems you ship.
★ 6·更新 2026-11-16
在 GitHub 查看 ↗直链 · 无中转页
我们没有可直接复制的安装命令,也没有公开的远端端点,所以不出配置。上面那条命令仅供参考,不是我们能担保的可复制命令——编一条出来比不给更糟。 各客户端的接法 →
- ★ 数取值
- 6 ★ · jcode-works/ragmir · 取自 GitHub 搜索 API · (2026-11-19 20:00:48 核对)
- 来源明细
- 收录自 punkpeye/awesome-mcp-servers 榜单(我们从中收集的条目之一) · 条目类型:MCP 服务
- 收录与活跃
- 收录于 2026-11-18 · 最近见到 2026-11-20 · 共见到 3 次 · 被 3 个来源列出
- 评分构成
- 综合分 300 · 6 ★ · 3 个来源 · mcp
常见问题(答案都来自我们的记录)
它适合谁 / 用来做什么?
我们把它归在这些标签下: MCP 服务。标签来自条目自身,不是我们强加的分类。
谁维护它、还在更新吗?
仓库
jcode-works/ragmir;我们收录于 2026-11-18;最近见到 2026-11-20。这里没有"官方认证"或"质量评级"——我们只记录来源与时间。README 原文(英文,未翻译) · 在 GitHub 读完整 README →
Ragmir
以下摘录自该仓库的 README(片段)
Cited retrieval for coding agents and the RAG systems you ship. Local, fast, and offline by default.
94% of real developer questions find the right file in the top 10 · 36 ms median search on a
30,171-chunk monorepo · benchmarks
Quick start ·
What your agent sees ·
Benchmarks ·
Agents and MCP ·
Run on a server ·
Docker ·
Python ·
ragmir.com
Ragmir turns your code, specifications, and office documents into a local search index. Claude
Code, Codex, or your own application queries it through MCP, the rgr CLI, or a TypeScript API,
and every passage comes back with a citation the agent can open and check. Your agent plans,
reasons, and writes with the model you choose; Ragmir finds the evidence. The same index runs on a
laptop for the first demo, then on a VPS, an on-premise server, or a network without internet
access.
bash
npm install -D @jcode.labs/ragmir
npx rgr setup --agents claude,codex # connect your agents
npx rgr sources add "docs//.md" "src//.ts"
npx rgr ingest
npx rgr search "how are permissions checked?" --compact
| Without Ragmir | With Ragmir |
| Code search misses the specs, spreadsheets, and scanned PDFs around the code. | One local index for code and documents, with optional local OCR. |
| Whole files pasted into the prompt, then pasted again on the next question. | A few compact citations per question; passages already seen come back as one-line stubs. |
| Answers you cannot trace, from files that may have changed since. | Citations to lines, pages, slides, and cells, flagged when their file changed. |
| An agent in one repository reading another project's documents. | Each server names its base and warns or refuses unrelated workspaces. |
## Why Ragmir
Code and documents in one index. Hybrid BM25 and vector search understands paths and
camelCase identifiers and boosts the code that defines what you ask about, so "how are
permissions checked" reaches PermissionService.java, not only its tests and notes.
Fast on real repositories. Median search takes 36 ms on a 30,171-chunk Java and TypeScript
monorepo with Office files, and the right file reaches the top 10 for 94% of 101 real developer
questions. GPU ingestion rebuilds this repository's index twice as fast on Apple silicon.
Ahead of the usual RAG stacks. On this repository, the right file reaches the top 3 for 83%
of developer questions, against 63% for a LangChain.js pipeline and 79% for MiniSearch BM25 with
the same embedding model, and Ragmir refuses 24 of 30 off-topic questions, 28 without a model,
where they refuse at most 2.
Evidence you can verify. Citations point to source lines, PDF pages, slides, sheet cells, or
EPUB sections. Results say when their file changed after indexing (sourceStatus) and when
their support is thin (weakEvidence). Questions your sources cannot answer return nothing
instead of noise: 68 of 90 off-topic and 26 of 100 near-domain questions on three real bases, up
from 54 and 23 in 6.4, and 65 and 27 without any model, up from 12 and 1, with no correct answer
refused.
Always current. rgr doctor compares the files on disk with the index on every run, and
rgr hooks install refreshes it in the background after commits, merges, and checkouts.
94% of real developer questions find the right file in the top 10 · 36 ms median search on a
30,171-chunk monorepo · benchmarks
Quick start ·
What your agent sees ·
Benchmarks ·
Agents and MCP ·
Run on a server ·
Docker ·
Python ·
ragmir.com
Ragmir turns your code, specifications, and office documents into a local search index. Claude
Code, Codex, or your own application queries it through MCP, the rgr CLI, or a TypeScript API,
and every passage comes back with a citation the agent can open and check. Your agent plans,
reasons, and writes with the model you choose; Ragmir finds the evidence. The same index runs on a
laptop for the first demo, then on a VPS, an on-premise server, or a network without internet
access.
bash
npm install -D @jcode.labs/ragmir
npx rgr setup --agents claude,codex # connect your agents
npx rgr sources add "docs//.md" "src//.ts"
npx rgr ingest
npx rgr search "how are permissions checked?" --compact
| Without Ragmir | With Ragmir |
| Code search misses the specs, spreadsheets, and scanned PDFs around the code. | One local index for code and documents, with optional local OCR. |
| Whole files pasted into the prompt, then pasted again on the next question. | A few compact citations per question; passages already seen come back as one-line stubs. |
| Answers you cannot trace, from files that may have changed since. | Citations to lines, pages, slides, and cells, flagged when their file changed. |
| An agent in one repository reading another project's documents. | Each server names its base and warns or refuses unrelated workspaces. |
## Why Ragmir
Code and documents in one index. Hybrid BM25 and vector search understands paths and
camelCase identifiers and boosts the code that defines what you ask about, so "how are
permissions checked" reaches PermissionService.java, not only its tests and notes.
Fast on real repositories. Median search takes 36 ms on a 30,171-chunk Java and TypeScript
monorepo with Office files, and the right file reaches the top 10 for 94% of 101 real developer
questions. GPU ingestion rebuilds this repository's index twice as fast on Apple silicon.
Ahead of the usual RAG stacks. On this repository, the right file reaches the top 3 for 83%
of developer questions, against 63% for a LangChain.js pipeline and 79% for MiniSearch BM25 with
the same embedding model, and Ragmir refuses 24 of 30 off-topic questions, 28 without a model,
where they refuse at most 2.
Evidence you can verify. Citations point to source lines, PDF pages, slides, sheet cells, or
EPUB sections. Results say when their file changed after indexing (sourceStatus) and when
their support is thin (weakEvidence). Questions your sources cannot answer return nothing
instead of noise: 68 of 90 off-topic and 26 of 100 near-domain questions on three real bases, up
from 54 and 23 in 6.4, and 65 and 27 without any model, up from 12 and 1, with no correct answer
refused.
Always current. rgr doctor compares the files on disk with the index on every run, and
rgr hooks install refreshes it in the background after commits, merges, and checkouts.
收录徽章(可选)
想把收录标记放进 README 就复制这行,可选,不影响收录。
[](https://anclum.com/zh/s/jcode-works-ragmir/)
- 来源
- awesome · https://github.com/jcode-works/ragmir
- 按领域浏览
- MCP 服务
- Traction
- 6 ★
- 收录来源
- 3 个独立来源
- 收录于
- 今天
更多 MCP 服务器
所属领域与标签
每个标签都能点进去看同类的全部条目。数字是当前库里的真实条数。