MinerU
Transforms complex documents like PDFs and Office docs into LLM-ready markdown/JSON for your Agentic workflows.
Long-term memory as a Markdown wiki: recall with cited notes, remember, file your documents.
教 AI 做这类工作的 Skill,可与本项一起使用
Transforms complex documents like PDFs and Office docs into LLM-ready markdown/JSON for your Agentic workflows.
Agent skills for Obsidian. Teach your agent to use Obsidian CLI and open formats including Markdown, Bases, JSON Canvas.
列表按使用分(满分 100)排序,由以下部分组成
| 热度 | 35/80 | GitHub 星标或每周下载量:较大的计 60,较小的计 20 |
|---|---|---|
| 新鲜度 | 12/12 | 30 天内有发布或代码更新得满分 |
| 仍在响应 | 0/8 | 上次检查时云端端点有响应 |
| 使用分 | 47/100 |
质量: 基础检查通过 3/3 项(仅展示,不用于排序) · 上升势头: 19 (只用于“上升中”标签)
选择你使用的 AI 应用,然后复制设置。
用一句话让 AI 帮你安装
请帮我安装 CROW: LLM Wiki。按照 https://mcp.popnx.com/i/crow-hq-llm-wiki-v2.md 操作,先把命令给我看,等我同意后再运行。粘贴到能在你电脑上工作的 AI(如 Claude Code、Cursor)。它会读取我们的步骤,先给你看命令,等你同意。无需密钥,无需注册。 · 查看 AI 会读取的全文
通过 3/3 项检查 · 在你的电脑上运行 · ✓ 命令已检查 2026年11月17日
第一步:你用哪个 AI?
选择你用的应用,步骤会显示在下方。
可连接 Claude,但需要先准备
需要先在电脑上安装 Python (uv)(只需一次) · 仅限电脑上的 Claude 应用(Windows 或 Mac),网页和手机不可用
把这段话复制到 Claude 的对话里。AI 会先检查电脑,告诉你要改哪个文件,并且每次都等你同意。
请在这台电脑上为 Claude 安装 MCP server CROW: LLM Wiki,按顺序:1) 用 uv --version 检查是否有 uv。没有的话,请让我从 https://docs.astral.sh/uv/getting-started/installation/ 安装,不要自己安装。2) 只使用这份配置(已通过 PopNx MCP 检查):{ "mcpServers": { "llm-wiki-v2": { "command": "uvx", "args": [ "llmwiki2", "mcp" ] } } } 3) 告诉我要修改的文件完整路径或要运行的命令,等我同意。4) 不需要密钥。5) 按约定执行,然后确认 CROW: LLM Wiki 的工具真的出现了。这段话不包含你的密钥。如果需要密钥,AI 会请你自己粘贴到文件或应用的输入框里。
已经装好了吗?先检查 · 打开终端,输入这条命令后按 Enter
uv --versionMac:按 ⌘ + Space,输入 Terminal 后按 Enter
Windows:打开“开始”菜单,输入 Windows PowerShell,然后选“打开”
还没安装: uv 没有点选式安装程序。从 uv 官方页面复制适合你系统(macOS 或 Windows)的一行命令,粘贴到终端 · 不需要单独安装 Python,uv 会在需要时自动下载
装好后关掉终端再打开,重新运行同一条命令,应显示版本号: uv --version
安装一次,所有需要 uv 的工具都能用
SettingsDeveloperEdit Config
{
"mcpServers": {
"llm-wiki-v2": {
"command": "uvx",
"args": [
"llmwiki2",
"mcp"
]
}
}
}用 CROW: LLM Wiki 告诉我你能帮我做什么,然后做一件给我看✓ 如果 Claude 说正在使用 CROW: LLM Wiki,或回答中出现 CROW: LLM Wiki 的工具名称,就表示连接成功
上面的命令不填这些也能用。想调整时再按开发者的说明添加。
OKF_MCP_MODELS Whose models do the memory's work, over what llmwiki2 setup saved: client (the MCP client's, on its own plan, no key), hybrid (the client writes, the wiki's classifier files) or wiki (the providers i…OKF_BUNDLE wiki 文件夹(默认 /llm-wiki) 说明为自动翻译,变量名保持原样;不确定时请查看原文。
菜单名称已于 2026年11月11日 对照 Anthropic 帮助页面核实 · 你的界面可能因版本略有不同
ChatGPT 暂时无法连接 CROW: LLM Wiki
CROW: LLM Wiki 需要安装在你的电脑上,而 ChatGPT 只能连接在网上运行的服务器
可连接 Claude Code,但需要先准备
需要先在电脑上安装 Python (uv)(只需一次)
把这段话复制到 Claude Code 的对话里。AI 会先检查电脑,告诉你要改哪个文件,并且每次都等你同意。
请在这台电脑上为 Claude Code 安装 MCP server CROW: LLM Wiki,按顺序:1) 用 uv --version 检查是否有 uv。没有的话,请让我从 https://docs.astral.sh/uv/getting-started/installation/ 安装,不要自己安装。2) 只使用这份配置(已通过 PopNx MCP 检查):claude mcp add --scope user llm-wiki-v2 -- uvx llmwiki2 mcp 3) 告诉我要修改的文件完整路径或要运行的命令,等我同意。4) 不需要密钥。5) 按约定执行,然后确认 CROW: LLM Wiki 的工具真的出现了。这段话不包含你的密钥。如果需要密钥,AI 会请你自己粘贴到文件或应用的输入框里。
已经装好了吗?先检查 · 打开终端,输入这条命令后按 Enter
uv --versionMac:按 ⌘ + Space,输入 Terminal 后按 Enter
Windows:打开“开始”菜单,输入 Windows PowerShell,然后选“打开”
还没安装: uv 没有点选式安装程序。从 uv 官方页面复制适合你系统(macOS 或 Windows)的一行命令,粘贴到终端 · 不需要单独安装 Python,uv 会在需要时自动下载
装好后关掉终端再打开,重新运行同一条命令,应显示版本号: uv --version
安装一次,所有需要 uv 的工具都能用
Mac:按 Command+空格,输入 Terminal · Windows:打开 PowerShell
claude mcp add --scope user llm-wiki-v2 -- uvx llmwiki2 mcp应能看到 CROW: LLM Wiki 在列表中并显示已连接
用 CROW: LLM Wiki 告诉我你能帮我做什么,然后做一件给我看✓ 如果 Claude Code 说正在使用 CROW: LLM Wiki,或回答中出现 CROW: LLM Wiki 的工具名称,就表示连接成功
上面的命令不填这些也能用。想调整时再按开发者的说明添加。
OKF_MCP_MODELS Whose models do the memory's work, over what llmwiki2 setup saved: client (the MCP client's, on its own plan, no key), hybrid (the client writes, the wiki's classifier files) or wiki (the providers i…OKF_BUNDLE wiki 文件夹(默认 /llm-wiki) 说明为自动翻译,变量名保持原样;不确定时请查看原文。
菜单名称已于 2026年11月11日 对照 Anthropic 帮助页面核实 · 你的界面可能因版本略有不同
可连接 Cursor,但需要先准备
需要先在电脑上安装 Python (uv)(只需一次)
把这段话复制到 Cursor 的对话里。AI 会先检查电脑,告诉你要改哪个文件,并且每次都等你同意。
请在这台电脑上为 Cursor 安装 MCP server CROW: LLM Wiki,按顺序:1) 用 uv --version 检查是否有 uv。没有的话,请让我从 https://docs.astral.sh/uv/getting-started/installation/ 安装,不要自己安装。2) 只使用这份配置(已通过 PopNx MCP 检查):{ "mcpServers": { "llm-wiki-v2": { "command": "uvx", "args": [ "llmwiki2", "mcp" ] } } } 3) 告诉我要修改的文件完整路径或要运行的命令,等我同意。4) 不需要密钥。5) 按约定执行,然后确认 CROW: LLM Wiki 的工具真的出现了。这段话不包含你的密钥。如果需要密钥,AI 会请你自己粘贴到文件或应用的输入框里。
已经装好了吗?先检查 · 打开终端,输入这条命令后按 Enter
uv --versionMac:按 ⌘ + Space,输入 Terminal 后按 Enter
Windows:打开“开始”菜单,输入 Windows PowerShell,然后选“打开”
还没安装: uv 没有点选式安装程序。从 uv 官方页面复制适合你系统(macOS 或 Windows)的一行命令,粘贴到终端 · 不需要单独安装 Python,uv 会在需要时自动下载
装好后关掉终端再打开,重新运行同一条命令,应显示版本号: uv --version
安装一次,所有需要 uv 的工具都能用
用 CROW: LLM Wiki 告诉我你能帮我做什么,然后做一件给我看✓ 如果 Cursor 说正在使用 CROW: LLM Wiki,或回答中出现 CROW: LLM Wiki 的工具名称,就表示连接成功
上面的命令不填这些也能用。想调整时再按开发者的说明添加。
OKF_MCP_MODELS Whose models do the memory's work, over what llmwiki2 setup saved: client (the MCP client's, on its own plan, no key), hybrid (the client writes, the wiki's classifier files) or wiki (the providers i…OKF_BUNDLE wiki 文件夹(默认 /llm-wiki) 说明为自动翻译,变量名保持原样;不确定时请查看原文。
菜单名称已于 2026年11月11日 对照 Cursor 帮助页面核实 · 你的界面可能因版本略有不同
可连接 VS Code,但需要先准备
需要先在电脑上安装 Python (uv)(只需一次)
把这段话复制到 VS Code 的对话里。AI 会先检查电脑,告诉你要改哪个文件,并且每次都等你同意。
请在这台电脑上为 VS Code 安装 MCP server CROW: LLM Wiki,按顺序:1) 用 uv --version 检查是否有 uv。没有的话,请让我从 https://docs.astral.sh/uv/getting-started/installation/ 安装,不要自己安装。2) 只使用这份配置(已通过 PopNx MCP 检查):{ "servers": { "llm-wiki-v2": { "type": "stdio", "command": "uvx", "args": [ "llmwiki2", "mcp" ] } } } 3) 告诉我要修改的文件完整路径或要运行的命令,等我同意。4) 不需要密钥。5) 按约定执行,然后确认 CROW: LLM Wiki 的工具真的出现了。这段话不包含你的密钥。如果需要密钥,AI 会请你自己粘贴到文件或应用的输入框里。
已经装好了吗?先检查 · 打开终端,输入这条命令后按 Enter
uv --versionMac:按 ⌘ + Space,输入 Terminal 后按 Enter
Windows:打开“开始”菜单,输入 Windows PowerShell,然后选“打开”
还没安装: uv 没有点选式安装程序。从 uv 官方页面复制适合你系统(macOS 或 Windows)的一行命令,粘贴到终端 · 不需要单独安装 Python,uv 会在需要时自动下载
装好后关掉终端再打开,重新运行同一条命令,应显示版本号: uv --version
安装一次,所有需要 uv 的工具都能用
用 CROW: LLM Wiki 告诉我你能帮我做什么,然后做一件给我看✓ 如果 VS Code 说正在使用 CROW: LLM Wiki,或回答中出现 CROW: LLM Wiki 的工具名称,就表示连接成功
上面的命令不填这些也能用。想调整时再按开发者的说明添加。
OKF_MCP_MODELS Whose models do the memory's work, over what llmwiki2 setup saved: client (the MCP client's, on its own plan, no key), hybrid (the client writes, the wiki's classifier files) or wiki (the providers i…OKF_BUNDLE wiki 文件夹(默认 /llm-wiki) 说明为自动翻译,变量名保持原样;不确定时请查看原文。
菜单名称已于 2026年11月11日 对照 VS Code 帮助页面核实 · 你的界面可能因版本略有不同
Claude Code
claude mcp add --scope user llm-wiki-v2 -- uvx llmwiki2 mcpClaude Desktop (claude_desktop_config.json)
{
"mcpServers": {
"llm-wiki-v2": {
"command": "uvx",
"args": [
"llmwiki2",
"mcp"
]
}
}
}Cursor (~/.cursor/mcp.json)
{
"mcpServers": {
"llm-wiki-v2": {
"command": "uvx",
"args": [
"llmwiki2",
"mcp"
]
}
}
}VS Code (mcp.json)
{
"servers": {
"llm-wiki-v2": {
"type": "stdio",
"command": "uvx",
"args": [
"llmwiki2",
"mcp"
]
}
}
}OKF_MCP_MODELS envOKF_BUNDLE env说明为自动翻译,变量名保持原样;不确定时请查看原文。
这些设置是根据作者在注册中心的条目生成的。如果 README 的写法不同,请以 README 为准。
依据这个服务器的连接方式和各应用自己的文档,检查于 2026年11月10日。
在你的电脑上运行,适用于
ClaudeGooseLM StudioMsty StudioCherry StudioCursorVS Code + GitHub CopilotVisual StudioWindsurf (Devin Desktop)ZedKiroClineContinueJetBrains AI AssistantClaude CodeCodex CLIGemini CLIOpenCodenodecodeWarpLibreChatRaycast
它在你的电脑上运行;安装后,工具列表会显示在你的 AI 应用中。
我们检查的是任何人都能看到的信息;我们没有阅读代码。不适用的检查项不计入总数。 · 检查于 2026年11月19日
注册名称已通过 GitHub 账户 crow-hq 验证,该账户拥有此仓库
代码最后更新于前天
使用 AGPL-3.0
它在你的电脑上运行,没有互联网端点
在你的电脑上运行,改用本地设置
它在你的电脑上运行;我们只能读取互联网端点的工具列表
尚未检查
如果你是作者,可把这段代码贴到 README。徽章会链接回本页。
[](https://mcp.popnx.com/en/servers/crow-hq-llm-wiki-v2)提问、分享技巧或报告无法使用。按“有帮助”数量排序。
还没有评价
与注册中心里这个分类中所有活跃的服务器比较。只有当发布者拥有该仓库时,星标数才计入。
它在 3 项适用的基础检查中通过了 3 项。我们没有阅读代码。在添加密钥或令牌之前,请先看看这个服务器要求哪些权限,并使用只具备所需权限的密钥。
注册中心没有列出必需的密钥,不过有些服务器会在首次使用时要求你登录。
它在你的电脑上运行。你的 AI 应用会在需要时启动它,数据不会经过作者的服务器(除非它自己调用在线服务)。
GitHub 仓库最后更新于前天,最新版本(1.0.5)于前天进入注册中心。
支持 MCP 的应用,例如 Claude Desktop、Claude Code、Cursor 和 VS Code。你的电脑上还需要有 Python (uv)。
同一分类中有:Puter MCP, XcodeBuildMCP, Vexa, Atlassian Rovo MCP Server, Anki MCP Server
同一分类、其他作者、命令已通过检查。官方的排在前面,再按星标排序。
如何看卡片:↓ 每周下载量i★ GitHub 星标i三大支柱:评价 · 检查 · 使用情况i更新 = 最新版本发布到注册中心的时间i
Puter MCP enables AI tools to interact with Puter: manage files, websites, workers, and more
XcodeBuildMCP provides tools for Xcode project management, simulator management, and app utilities.
Meeting bot and transcripts for Google Meet, Teams and Zoom. Live or after, speakers labelled.
Connect to Atlassian Jira, Confluence, Loom, and more to search, create, and manage your work.
MCP server for Anki flashcards: adaptive review, notes, media, and deck management via AnkiConnect.
| 本项 CROW: LLM Wiki | Puter MCP | XcodeBuildMCP | Vexa | Atlassian Rovo MCP Server | Anki MCP Server | |
|---|---|---|---|---|---|---|
| 运行位置 | 需要安装在电脑上 | 在云端运行,无需安装 | 需要安装在电脑上 | 在云端运行,无需安装 | 在云端运行,无需安装 | 需要安装在电脑上 |
| 需要密钥 | 否 | 否 | 否 | 是 | 否 | 否 |
| 可在 Claude 中按 + 添加 | 否 | 否 | 否 | 否 | 是 | 否 |
| 基础检查 | 3/3 | 4/4 | 3/3 | 2/4 | 4/4 | 3/3 |
| 许可证 | AGPL-3.0 | AGPL-3.0 | MIT | Apache-2.0 | Apache-2.0 | MIT |
| 价格 | 登记中未列出费用 | 登记中未列出费用 | 登记中未列出费用 | 登记中未列出费用 | 登记中未列出费用 | 登记中未列出费用 |
按原文从作者的仓库复制。PopNx MCP 没有审查或背书其内容。HTML、图片和脚本已被移除。链接会离开本站。
Give it your documents. It files them into a tidy wiki of Markdown notes and answers your questions, citing the notes it used. It runs on your computer, with any AI provider: OpenRouter, OpenAI, Gemini, Ollama (free and local) or any OpenAI-compatible server. It works in CROW mode by default: a small classifier decides where things go, so the wiki stays fast and cheap as it grows.
Rather not use a terminal? Crow is this library as a desktop app, with downloads for macOS, Windows and Linux. The steps below install the library itself, with its web page and command line.
1. Install it with Python 3.11 or later (in a virtual environment, if your system asks for one):
pip install llmwiki2
No Python, or you'd rather keep it apart from your other packages? Use uv, which also fetches Python: uv tool install llmwiki2. The same install is the Python library too: from llmw2 import Wiki, see the library guide.
2. Start it:
llmwiki2
Your browser opens. Pick a provider, paste its key, press Test connection, then Save and start. That's it.
Just looking? llmwiki2 demo opens an example wiki, the notes of a fictional coffee roastery, with no key needed to browse it and its brain. It is copied to ~/llm-wiki-demo, so you can add to it or delete it. To try it without installing anything but uv: uvx llmwiki2 demo.
[!TIP]
No key? Pick Ollama: free, runs on your computer, no account
(download it, then
ollama pull gemma4).
Ollama runs the model locally; CROW's classifier is separate and remote by default.
It has its own provider (Settings → Advanced): OpenRouter, TypeSafe or a local
server. Without one the wiki uses classic mode, where the model decides by itself.
One OpenRouter key works for every model, and for CROW too.
| Add documents | Drop text, Markdown, PDF, Word, PowerPoint, Excel or OpenDocument files anywhere on the page. Each one lands in the right folder, merged with what the wiki already knows; a spreadsheet gives a note per sheet. |
| Ask questions | Type a question. The answer cites the notes it used: click one to read it. |
| Give Claude a memory | From the terminal only: llmwiki2 setup, then talk to Claude Code or Codex in plain words. With the page: Memory → Start, then paste the claude mcp add … or codex mcp add … line it shows. Either way they recall from your wiki and file what they learn in it (below). |
| See the brain | A live map of your folders, notes and links. |
| Delete | Hover a note or folder in the sidebar and press the bin, or Delete note at the foot of a note. Links to it go from the other notes. Empty the wiki on the home page starts over. |
| Move and describe | Move at the foot of a note files it in another folder; every link to and from it follows. The pencil beside a folder in the sidebar edits its description, the line the librarian routes by. |
| Areas | Areas at the top: create a top-level folder, confirm or dismiss the areas proposed to the wiki, rename one or merge it into another. The wiki never opens or proposes an area by itself. |
| Keep your files | Plain Markdown in ~/llm-wiki: open it in any editor, keep it in git. |
The wiki can be the long-term memory of Claude Code, Codex or any MCP client, documents already filed included. It comes with the mcp extra (the Docker image has it).
No page, no server to keep running: Claude Code starts the memory by itself.
1. Install it:
uv tool install 'llmwiki2[mcp]' # or: pip install 'llmwiki2[mcp]'
2. Set it up:
llmwiki2 setup
To the first question answer 2 (as the memory of an agentic CLI); after that, Enter takes the default every time:
| It asks | Pick |
|---|---|
| Which models do the work | 1 (the default): Claude Code or Codex do it, on their plan, no key. 2 (hybrid) is quicker and needs an OpenRouter key, or Ollama on your computer |
| Connect Claude Code? | Y. With several configurations (~/.claude, ~/.claude-work), it asks which: Enter for all |
| Add the lines to CLAUDE.md? | Y: they make Claude use the memory when you talk normally |
3. Talk to it, in any language, in Claude Code or Codex, anywhere:
ricorda che Rossi ci paga a 45 giorni · what did we decide about pricing? · add ~/Downloads/offer.pdf to the
wiki · move the pricing note to suppliers
The first time it uses each tool, Claude Code asks your permission: choose "don't ask again" for the ones you trust. To see the brain or browse the notes, run llmwiki2: the page opens on the same wiki, while Claude Code keeps using it. Run llmwiki2 setup again to change anything. Windows says it blocked llmwiki2.exe? See Something wrong?.
Open Memory, press Start, and connect a client:
claude mcp add --transport http --scope user llm-wiki http://127.0.0.1:8000/mcp
codex mcp add llm-wiki --url http://127.0.0.1:8000/mcp
The client gets its tools: recall answers from your notes and documents, citing them; remember files what it learns, in the right folder, merged and linked like any note (CROW); search finds notes by their words with no model call; read_note reads a note in full; folders, move_note, describe_folder, rename_area, merge_areas and delete_note reorganize the wiki (the last two only when you ask); rebuild (with confirm) files every note again on the same folders, from the memory's own raw copies. Started from the terminal (llmwiki2 mcp) it also files documents from your disk: remember_file and sync_folder. Which models do the work is a choice under Memory or in setup:
setup). The memory hands the client every model call it makes, while CROW runs as always. Claude Code decides with a Haiku subagent and writes with its own model; Codex uses its own. It runs on the client's plan, with no key in the wiki. The requests carry your documents' text to the client: it is told to read it as data and to answer without tools, but that is an instruction, not a sandbox (see Security in the memory guide).Docker, the tools and security: docs/wiki/memory.md.
Because a wiki stays readable. RAG keeps your documents as embeddings, an opaque vector index no one can read or fix. Here every document becomes a Markdown note, filed in a folder that says what it holds and linked to related notes: you can open it, correct it and keep it in git, and every answer cites the notes it used. And knowledge accumulates: a new source updates the note on its subject instead of being rediscovered at every question.
CROW keeps it that way as the wiki grows. In Karpathy's LLM Wiki the model finds pages by reading an index, which works at moderate scale (about a hundred sources); beyond that the gist suggests adding search, hybrid lexical and vector. In CROW a small classifier works with the folders instead: filing picks the folder among every folder of the wiki in one choice, and answering finds the notes by search and lets the classifier reorder them, so the wiki can grow without vectors and stay something a person can read. The LLM lays out the folders: in a batch, before its documents are filed, and for a document filed alone, by splitting a folder that has grown. In the paper, retrieval kept its accuracy across a twentyfold growth of the wiki. A separate test on a private wiki of about 500 notes pointed the same way: with CROW the right note was found nearly as often at the end as early on, while with the LLM taking the decisions it was found markedly less often as the wiki grew. On 1,000 Enron mails filed in their owners' folders, CROW read the right note for every question at each step of the growth while classic went from 76% to 60%. The classifier weighs at most 24 candidate notes per decision, so its tokens per document nearly stopped growing after the first few hundred documents; CROW's cost per document rose 1.4 times over the 1,000, classic's 1.6 times, and at 800 to 1,000 documents CROW cost 0.41 times classic's with the writer at its list price (benchmarks/README.md).
Does everything run on my computer? It can, with no key and nothing leaving it. Crow, the desktop app, does it out of the box. With the library, Ollama serves the writer and the classifier too: a typed classifier such as tev1 behind Ollama 0.35 or later, or Laya (see everything on your computer). The library's default classifier is remote: Jev, through OpenRouter or TypeSafe. Without a classifier the wiki runs in classic mode, where the LLM takes every decision.
What is Jev? A typed classifier by TypeSafe AI. Given a text, it answers typed questions (pick one of these options; is this statement true?) with probabilities instead of prose. CROW asks it every filing and retrieval decision and ke