L
labyrinth-analytics/loredocs
Searchable knowledge base for your AI projects
无 SECURITY.md
在 GitHub 查看 ↗链接已于 2026-11-12 核查 · HTTP 200 · 打开的是厂商自己的官网
安装与配置
- 复制上面的命令
- 粘成
claude_desktop_config.json里mcpServers的一项（本地服务器用 command + args，示例见 客户端接法） - 重启客户端
客户端配置（取自该仓库的安装命令）
{
"mcpServers": {
"labyrinth-analytics-loredocs": {
"command": "uvx",
"args": ["loredocs"]
}
}
}解析自我们于 2026-10-26 抓取的该仓库 README；我们未执行过。
command/args 来自仓库写明的安装命令；不确定时请以该项目 README 为准。
VS Code（.vscode/mcp.json —— 键名是 servers）
{
"servers": {
"labyrinth-analytics-loredocs": {
"command": "uvx",
"args": ["loredocs"]
}
}
}VS Code 顶层键是 <code>servers</code>，其余与上面那份相同。
Claude Code（命令行）
claude mcp add --transport stdio labyrinth-analytics-loredocs -- uvx loredocs
Claude Code 不收 JSON 文件，用这条命令直接加。
配置项的键名以你的客户端为准：客户端与 CLI
- ★ 数取值
- 4 ★ · labyrinth-analytics/loredocs · 取自 GitHub 搜索 API · （2026-11-13 20:00:50 核对）
- 来源明细
- 收录自 punkpeye/awesome-mcp-servers 榜单（我们从中收集的条目之一） · 条目类型：MCP 服务
- 收录与活跃
- 收录于 2026-10-23 · 最近见到 2026-11-14 · 共见到 26 次 · 被 23 个来源列出
- 评分构成
- 综合分 2,300 · 4 ★ · 23 个来源 · mcp
- 安装
uvx loredocs
常见问题（答案都来自我们的记录）
怎么安装？
该仓库给出的安装命令是
uvx loredocs。我们的记录里它是仓库自己提供的；不保证在你的客户端上直接可用。它适合谁 / 用来做什么？
我们把它归在这些标签下: MCP 服务。标签来自条目自身，不是我们强加的分类。
谁维护它、还在更新吗？
仓库
labyrinth-analytics/loredocs；我们收录于 2026-10-23；最近见到 2026-11-14。这里没有"官方认证"或"质量评级"——我们只记录来源与时间。# LoreDocs v0.1.31
以下摘录自该仓库的 README（片段） · 在 GitHub 读完整 README →
Your AI project's knowledge base. Organized, searchable, version-tracked.
LoreDocs gives Claude persistent access to your project documentation -- specs, guides, architecture decisions, reference docs -- so it never loses context between sessions. Works with Claude Code, Cowork, Cursor, OpenAI Codex, and Hermes Agent.
> Install directly from Claude Code's plugin marketplace, or via PyPI: uvx loredocs
## Quick Start
Prerequisites: uv (fast Python package manager).
bash
# Install uv: https://docs.astral.sh/uv/getting-started/installation/
# Clone and install
cd /path/to/loredocs
uv sync
For detailed installation instructions, see INSTALL.md.
Using the Claude Agent SDK directly? git clone the public repo and point the SDK's local-directory plugin loader at it -- the repo root is a self-contained plugin directory (.claude-plugin/plugin.json + .mcp.json). No separate SDK-installable bundle exists or is needed.
## Using LoreDocs
### Claude Code (Terminal)
bash
claude --plugin-dir /path/to/loredocs
Or inside an existing session:
/plugin add /path/to/loredocs
Once loaded, Claude has access to all 48 LoreDocs MCP tools automatically. Ask Claude to "create a vault for this project" or "find the architecture doc" and it uses the tools on its own.
### Cowork (Desktop App)
1. Click + next to the prompt box
2. Select Plugins > Add plugin
3. Browse to the loredocs source folder
Shared Database Access: Cowork runs in a sandboxed VM. To access docs saved from Claude Code, ask Claude:
> "Mount my ~/.loredocs folder"
### Hermes Agent
For Hermes Agent users, add LoreDocs as an MCP server under mcpservers: in ~/.hermes/config.yaml (see INSTALL.md for the full entry), then restart Hermes.
All 48 LoreDocs MCP tools are then available in your Hermes sessions.
## Hermes Disclosures
When using LoreDocs with Hermes Agent:
Installation: First run downloads the loredocs version you pin from PyPI via uvx. There is no automatic self-update.
Data Storage: All vault data is stored locally at ~/.loredocs/ in SQLite format. No data is sent to cloud services or external servers.
Pro License Validation: Pro tier activation uses offline Ed25519 cryptography to validate your license key. No network request is made during validation.
Telemetry: LoreDocs does not collect or transmit telemetry or usage data.
Network calls: Pro semantic search downloads the BAAI/bge-small-en-v1.5 embedding model from Hugging Face once, on first use. The optional Notion import calls the Notion API with a token you provide. LoreDocs makes no other network calls.
## How It Works
LoreDocs organizes knowledge into vaults -- named containers for related documents. Each vault can hold specs, guides, decisions, checklists, or any text you want Claude to remember.
~/.loredocs/loredocs.db / "Run vaultlist and show me the results."
If you see a list of vaults (or an empty list if this is your first time), LoreDocs is connected. If you get an error about missing tools, re-run uv sync and reload the plugin.
## Recommended CLAUDE.md Setup
For the best experience, add the following snippet to your ~/.claude/CLAUDE.md (global) or your project's CLAUDE.md. This tells Claude how to use LoreDocs consistently across sessions.
LoreDocs gives Claude persistent access to your project documentation -- specs, guides, architecture decisions, reference docs -- so it never loses context between sessions. Works with Claude Code, Cowork, Cursor, OpenAI Codex, and Hermes Agent.
> Install directly from Claude Code's plugin marketplace, or via PyPI: uvx loredocs
## Quick Start
Prerequisites: uv (fast Python package manager).
bash
# Install uv: https://docs.astral.sh/uv/getting-started/installation/
# Clone and install
cd /path/to/loredocs
uv sync
For detailed installation instructions, see INSTALL.md.
Using the Claude Agent SDK directly? git clone the public repo and point the SDK's local-directory plugin loader at it -- the repo root is a self-contained plugin directory (.claude-plugin/plugin.json + .mcp.json). No separate SDK-installable bundle exists or is needed.
## Using LoreDocs
### Claude Code (Terminal)
bash
claude --plugin-dir /path/to/loredocs
Or inside an existing session:
/plugin add /path/to/loredocs
Once loaded, Claude has access to all 48 LoreDocs MCP tools automatically. Ask Claude to "create a vault for this project" or "find the architecture doc" and it uses the tools on its own.
### Cowork (Desktop App)
1. Click + next to the prompt box
2. Select Plugins > Add plugin
3. Browse to the loredocs source folder
Shared Database Access: Cowork runs in a sandboxed VM. To access docs saved from Claude Code, ask Claude:
> "Mount my ~/.loredocs folder"
### Hermes Agent
For Hermes Agent users, add LoreDocs as an MCP server under mcpservers: in ~/.hermes/config.yaml (see INSTALL.md for the full entry), then restart Hermes.
All 48 LoreDocs MCP tools are then available in your Hermes sessions.
## Hermes Disclosures
When using LoreDocs with Hermes Agent:
Installation: First run downloads the loredocs version you pin from PyPI via uvx. There is no automatic self-update.
Data Storage: All vault data is stored locally at ~/.loredocs/ in SQLite format. No data is sent to cloud services or external servers.
Pro License Validation: Pro tier activation uses offline Ed25519 cryptography to validate your license key. No network request is made during validation.
Telemetry: LoreDocs does not collect or transmit telemetry or usage data.
Network calls: Pro semantic search downloads the BAAI/bge-small-en-v1.5 embedding model from Hugging Face once, on first use. The optional Notion import calls the Notion API with a token you provide. LoreDocs makes no other network calls.
## How It Works
LoreDocs organizes knowledge into vaults -- named containers for related documents. Each vault can hold specs, guides, decisions, checklists, or any text you want Claude to remember.
~/.loredocs/loredocs.db / "Run vaultlist and show me the results."
If you see a list of vaults (or an empty list if this is your first time), LoreDocs is connected. If you get an error about missing tools, re-run uv sync and reload the plugin.
## Recommended CLAUDE.md Setup
For the best experience, add the following snippet to your ~/.claude/CLAUDE.md (global) or your project's CLAUDE.md. This tells Claude how to use LoreDocs consistently across sessions.
收录徽章（可选）
想把收录标记放进 README 就复制这行，可选，不影响收录。
[](https://anclum.com/zh/s/labyrinth-analytics-loredocs/)
- 来源
- awesome · https://github.com/labyrinth-analytics/loredocs
- 按领域浏览
- MCP 服务
- Traction
- 4 ★
- 收录来源
- 23 个独立来源
- 收录于
- 今天
- 安全策略
- 我们没在该仓库根目录找到
SECURITY.md（这不代表不安全）
同类推荐
所属领域与标签
每个标签都能点进去看同类的全部条目。数字是当前库里的真实条数。