L
labyrinth-analytics/loredocs
Searchable knowledge base for your AI projects
no SECURITY.md
View on GitHub ↗Link checked 2026-11-12 · HTTP 200 · opens the vendor's own site
Install & config
- Copy the command above
- Paste it as one entry under
mcpServersinclaude_desktop_config.json— local servers take command + args (example: clients) - Restart your client
Client config (built from the install command this repo gives)
{
"mcpServers": {
"labyrinth-analytics-loredocs": {
"command": "uvx",
"args": ["loredocs"]
}
}
}Parsed from the README we fetched on 2026-10-26; we have not executed it.
command/args come from the install command the repository states. When it is ambiguous, the project README wins.
VS Code (.vscode/mcp.json - the key is servers)
{
"servers": {
"labyrinth-analytics-loredocs": {
"command": "uvx",
"args": ["loredocs"]
}
}
}Same server, but VS Code keeps it under <code>servers</code>.
Claude Code (command line)
claude mcp add --transport stdio labyrinth-analytics-loredocs -- uvx loredocs
Claude Code does not read a config file; add the server with this command.
Key names differ by client: Clients & CLI
- Star count
- 4 ★ · labyrinth-analytics/loredocs · read from the GitHub search API · (checked 2026-11-13 20:00:50)
- Source
- collected from the punkpeye/awesome-mcp-servers list · type: MCP server
- Harvest history
- first seen 2026-10-23 · last seen 2026-11-14 · seen 26× · listed by 23 sources
- Score
- score 2,300 · 4 ★ · 23 sources · mcp
- Install
uvx loredocs
FAQ (answers come from our records)
How do I install it?
The repository provides this install command:
uvx loredocs. It comes from the repository itself; we cannot guarantee it runs as-is in your client.Who is it for?
We filed it under these tags: MCP 服务. The tags come from the entry itself, not a taxonomy we imposed.
Who maintains it?
repository
labyrinth-analytics/loredocs；first catalogued 2026-10-23；last seen 2026-11-14。There is no official certification or quality rating here — we record sources and dates only.# 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.
Listed badge (optional)
Copy this line into the README if you want the listing mark. Optional, and it does not affect being listed.
[](https://anclum.com/en/s/labyrinth-analytics-loredocs/)
- Source
- awesome · https://github.com/labyrinth-analytics/loredocs
- Browse by field
- MCP servers
- Traction
- 4 ★
- Listed by
- 23 independent sources
- added
- today
- Security policy
- no
SECURITY.mdat the repository root (which does not mean it is unsafe)
More like this
Filed under
Every tag opens the full list for that filter. Counts are the live catalogue figures.