Mmcp.market

LoreDocs MCP server

by labyrinth-analytics·io.github.labyrinth-analytics/loredocs·v0.1.28
No reviews yet

Local-first knowledge vaults for project docs and specs. Tagged, versioned, full-text searchable.

B80/100grade B
Write a reviewInstall
What users say
No reviews yet
Be the first
Safety scan
B80/100

full report

Adoption
Growing

4 stars41 downloads/wk

Reviews

Write one

Nobody has reviewed LoreDocs yet.

If you have run it, two minutes of your experience saves the next person an afternoon.

LoreDocs tools (51, 7 write)

write = sends, deletes, buys or posts

Read from the package source without running it. The installed server may list more.

  • get_license_tier

    Return the current LoreDocs license tier and status.

  • get_server_info

    Return MCP compatibility status for this LoreDocs server.

  • loredocs_onboard

    Set up or update your LoreDocs workspace configuration.

  • vault_add_doc

    Add a text document to a vault with metadata (tags, category, priority, notes).

  • vault_add_note

    Attach a contextual note to a document.

  • vault_archive

    Archive a vault (soft delete). Archived vaults are hidden from vault_list by default but can be restored.

  • vault_bulk_tag

    Apply tag changes to multiple documents at once.

  • vault_categorize

    Set a document's category (general, reference, config, report, template, archive, imported).

  • vault_copy_doc

    Copy a document from one vault to another, including all metadata.

  • vault_createwrite action

    Create a new knowledge vault for organizing project documents.

  • vault_deletewrite action

    Permanently delete a vault and ALL its documents. This cannot be undone.

  • vault_doc_history

    View the version history for a document.

  • vault_doc_restore

    Restore a document to a previous version.

  • vault_estimate_tokens

    Preview the token count of a vault injection without injecting documents.

  • vault_export

    Export all documents from a vault to a local directory.

  • vault_export_manifest

    Export a complete manifest of a vault's contents.

  • vault_find_related

    Find all documents linked to a given document. Pro only.

  • vault_get_doc

    Retrieve a document's metadata and optionally its text content.

  • vault_get_injection_cap

    Return the stored per-vault injection token cap (or 'not set' if none).

  • vault_get_linked_sessions

    Return LoreDocs documents linked to a given LoreConvo session.

  • vault_get_server_capabilities

    Return a summary of this LoreDocs server's injection capabilities and token estimation settings.

  • vault_get_session_links

    Return cross-product LoreConvo sessions linked to a LoreDocs document.

  • vault_get_session_token

    Generate a fresh session token (UUID4) for use with vault_inject / vault_prime.

  • vault_import_dir

    Bulk import all supported files from a directory into a vault.

  • vault_import_notion

    Import Notion pages and databases into a LoreDocs vault.

  • vault_import_notion_setup

    Report Notion import readiness and how to enable it. Read-only. Does not install or modify any packages.

  • vault_info

    Get detailed information about a vault, including its full document manifest.

  • vault_inject

    Load ranked vault documents into conversation context with token-budget enforcement.

  • vault_inject_by_tag

    Load all documents matching any of the given tags into the current conversation context.

  • vault_inject_summary

    Generate a summary overview of a vault's contents for conversation orientation.

  • vault_link_docwrite action

    Create a link between two documents across any vault.

  • vault_link_project

    Associate a Claude Project name with a vault.

  • vault_link_sessionwrite action

    Create a manual cross-product link from a LoreConvo session to a LoreDocs doc.

  • vault_list

    List all knowledge vaults with summary stats (document count, total size, last modified).

  • vault_list_docs

    List documents in a vault with sorting and filtering options.

  • vault_move_doc

    Move a document to a different vault. Removes it from the source vault.

  • vault_open_workspace

    Open (or create) a vault scoped to a workspace directory.

  • vault_prime

    Pre-load all vault documents into the current session by priority order.

  • vault_rebuild_index

    Rebuild the LanceDB semantic search index from all stored documents. Pro only.

  • vault_remove_docwrite action

    Soft-delete a document. The document is hidden but can be recovered.

  • vault_search

    Full-text or semantic search across document contents.

  • vault_search_by_tag

    Find all documents with a specific tag, across one vault or all vaults.

  • vault_set_injection_cap

    Set the per-vault injection token cap (admin-only).

  • vault_set_priority

    Mark a document's priority/status: authoritative, normal, draft, or outdated.

  • vault_set_tier

    Activate a tier (free or pro) for LoreDocs.

  • vault_suggest

    Get suggestions for documents that may need attention.

  • vault_tag_doc

    Add or remove tags on a document.

  • vault_tier_status

    Show current tier (Free or Pro) and usage vs. limits.

  • vault_unlink_docwrite action

    Remove a link between two documents (both directions).

  • vault_update_docwrite action

    Update a document's content or metadata.

  • vault_verify

    Verify version-storage integrity for a vault or specific document.

Public scan report

scanner v0.1.9 · 2026-09-25 · same rubric, same numbers if you re-run it

no findings
  • Code scan17 source files scanned25/25
  • –Live reliabilityno gateway calls yet and no remote to proben/a
  • –Tool poisoningtools not inspected (local package is not executed); not countedn/a
  • Auth qualitystatic API keys via environment variables6/15
  • Maintenancelast push 0 days ago15/15
  • Maintainer identityregistry namespace matches repository owner6/10
Overall 80/100. Components that don't apply are left out of the denominator. Any critical finding is an F.RubricAppeal a findingJSON

What the publisher says

From the LoreDocs repository's README, as published. We do not edit it. Read it on GitHub

LoreDocs v0.1.28

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).

# Install uv (one time)
curl -LsSf https://astral.sh/uv/install.sh | sh

# 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)

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"

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          <-- SQLite database (metadata, search index)
~/.loredocs/vaults/<vault-id>/   <-- Document files on disk

Key concepts:

  • Vaults group related docs by project or topic
  • Documents are text files with metadata (tags, categories, priority, notes)
  • Version history tracks every change to every document
  • Full-text search via SQLite FTS5 finds anything instantly
  • Injection loads vault content into Claude's context on demand

Your Data is Always Available

LoreDocs works through MCP tools when they are available and falls back to bundled scripts automatically when they are not. Your vault documents are safe regardless of MCP status -- the same add, search, and retrieve operations work either way. You do not need to configure anything; the plugin skill handles the switch silently.

Verify Installation

After installing, verify LoreDocs is working by asking Claude:

"Run vault_list 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 (persistent project knowledge)

At session start:
1. Call `vault_list` to see available knowledge vaults.
2. Call `vault_inject_summary` for any vaults relevant to the current project.
3. Use this context to understand project architecture, decisions, and reference docs.

During the session:
- If you create significant documentation, add it to LoreDocs with `vault_add_doc`.
- Tag documents for easy cross-vault discovery with `vault_tag_doc`.

At session end:
- If new docs were created or updated, ensure they are stored in LoreDocs for future sessions.

Shortened. The full README is on GitHub.

Nothing above is checked by us. What we check is on the safety report.

Install directly

claude mcp add loredocs -- uvx loredocs
Add to Cursor

LoreDocs: common questions

Is LoreDocs MCP server safe?
Mostly: it is graded B (80/100). Read the LoreDocs safety report
How do I install LoreDocs?
It runs on your machine. Copy the Claude Code, Claude Desktop or Cursor config from the install section.
Does LoreDocs need an API key?
Yes. The registry entry asks for LOREDOCS_PRO.
Is LoreDocs maintained?
The last commit was in the last day (2026-09-25). The latest release is v0.1.28.
What can I use instead of LoreDocs?
Servers from other publishers that do the same job: MCP server, Obsidian Hybrid Search MCP server and loci MCP server. Compare all LoreDocs alternatives.

Alternatives to LoreDocs

Same job from other publishers: the closest match first, then the best rated.

All LoreDocs alternatives →
  • MCP
    Manage Appwrite projects, databases, auth, storage, functions, and messaging; search Appwrite docs
    A
  • Obsidian Hybrid Search
    Search Obsidian vaults with hybrid full-text, fuzzy, semantic, and graph retrieval.
    B
  • loci
    Cross-session memory and hybrid RAG over your notes and docs. Local-first, with cited answers.
    A
  • OrchestKit Docs MCP
    Read-only MCP server for the OrchestKit docs: full-text search + Markdown fetch. No auth.
    A
  • AI Context
    Local-first MCP server: version-correct library docs, code map, and offline drift for your repo.
    B
LoreDocs vs MCPLoreDocs vs Obsidian Hybrid SearchLoreDocs vs loci

More from labyrinth-analytics →