Loreweave MCP server

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

• lore_aggregate_facts

  Deterministic aggregation over fact history \u2014 counts grouped by object/subject/predicate with date-range filters. Use for "how many X", "which Y most often" questions; similarity search cannot answer these reliably. Returns { groups, totalGroups, limit }: `groups` is the top `limit` (default 100), so read `totalGroups` for "how many distinct values are there" rather than counting `groups`, an

• lore_assert_fact

  Record an atomic fact (subject :: predicate :: object) with bitemporal validity. Contradicting facts in the same slot are superseded automatically (never deleted; history stays queryable). The fact is journalled to lore/journal/ in markdown, so the vault remains the source of truth. Use for durable knowledge: decisions, states, preferences, relationships.

• lore_capture

  Append a timestamped line to lore/inbox.md (or another vault note). Use for fleeting observations worth keeping that are not atomic facts. The captured text is searchable immediately. Never overwrites anything, and never writes outside the vault \u2014 a path that escapes it, including through a symlink, is refused.

• lore_context_pack

  Progressive-disclosure primer: vault stats, top entities, recently modified notes, currently-valid facts, and (if topic given) top search hits. Call once at session start to orient; then drill down with lore_search / lore_read_note. Every list here is a sample: when one is cut, a `truncated` field names it with { shown, of, rest } and the tool to call for the remainder \u2014 so treat a missing it

• lore_dream_reportwrite action

  Run the consolidation pass: duplicate passages, contradicting/recently-changed facts, stale knowledge needing review, suggested missing links, orphan notes. Leaves the vault untouched unless apply=true (which writes a digest + review queue under lore/); it does perform index maintenance either way, which changes no results. Findings are a summary \u2014 pass verbose:true for every one.

• lore_index

  Incrementally sync the markdown vault into the index. Call after writing files to the vault through anything OTHER than lore_* tools (an editor, another agent, plain fs writes) \u2014 the lore_* write tools index their own writes, so their content is searchable immediately without this.

• lore_invalidate_fact

  Close the currently-valid fact in a (subject, predicate) slot without asserting a replacement \u2014 e.g. "no longer true". Journalled; history preserved.

• lore_mark_used

  Reinforce passages that actually contributed to your answer (spaced-repetition signal: used memories decay slower). Call after citing a note.

• lore_propose_facts

  Returns candidate facts mined from a note's structure that are NOT yet in the fact store, for you to adjudicate. The engine only auto-accepts unambiguous field syntax (frontmatter, `key:: value`, `- [key] value`); prose formatting like `- **Owner:** Priya` is precise on entity notes and noisy on report notes, so it is surfaced here instead of assumed. Review these and call lore_assert_fact for the

• lore_query_facts

  Query the bitemporal fact store. Default: currently-valid facts. asOf answers "what was true on DATE", asKnownAt answers "what did we know on DATE"; includeHistory shows the full supersession chain. Prefer this over lore_search for factual slots (status, location, role, preference). Returns { facts } and, when the result is a sample, a `truncated` field with { shown, of, rest } \u2014 narrow by su

• lore_read_note

  Read the raw markdown of a note by vault-relative path (as returned in search results). Never reads outside the vault \u2014 a path that escapes it, including through a symlink whose target lives elsewhere, is refused, and such a file is not indexed or searchable either. After reading a note that answered the question, call lore_mark_used to reinforce it.

• lore_resume

  What changed since this tool was last called: notes edited, facts asserted, and knowledge updates (slot: old \u2192 new). Call once at session start to continue where the previous session left off \u2014 the delta is computed from record time, so the same watermark always yields the same answer. Calling with no `since` consumes the delta (advances the watermark); pass an explicit `since` for a pur

• lore_review

  Important-but-fading knowledge: blocks whose retrievability has decayed below the threshold despite mattering, plus long-untouched open facts. This is the spaced-repetition loop made operable: review the list, then call lore_mark_used on anything still relevant \u2014 use is what reinforces stability. Deterministic, computed from the vault's own fitted forgetting curve.

• lore_search

  Hybrid retrieval over the markdown vault: BM25 + knowledge-graph spreading activation (+ dense embeddings when configured). Returns one passage per note \u2014 the section that best covers your query \u2014 with the file it came from, how much of your query it matched, and any entity that linked it in. Use for any "what do my notes say about X" question, including multi-hop associations where the

• lore_timeline

  Chronological history of an entity in one call: every value change from the bitemporal fact store (with what each value replaced and when it stopped holding) merged with content-dated passages mentioning the entity. Use for "what happened to X", "what was X before it changed", "history of X" \u2014 instead of sampling repeated as-of fact queries and windowed searches.

• Code scan5 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 qualitylocal package, no credentials required12/15
• Maintenancelast push 22 days ago15/15
• Maintainer identityregistry namespace matches repository owner; GitHub account older than a year8/10

Safety score

92/100

higher than 90% of 4,460 AI and agents servers

Tools

15

the typical AI and agents server has 6

Tools that change things

7%

typical: 0%. Fewer write tools means less an agent can break

Downloads a week

167

more than 72% of 1,538 AI and agents servers with a package

Loreweave: common questions

Is Loreweave MCP server safe?

Yes, by our scan: it is graded A (92/100). Read the Loreweave safety report

How do I install Loreweave?

It runs on your machine. Copy the Claude Code, Cursor, VS Code or Claude Desktop config from the install section.

Does Loreweave need an API key?

Not as far as the registry entry and our scan can tell: no credentials are declared or required.

Is Loreweave maintained?

The last commit was 26 days ago (2026-10-09). The latest release is v0.39.0.

What can I use instead of Loreweave?

Servers from other publishers that do the same job: Basic Memory MCP server, IWE (iwe.md) MCP server and PDF MCP server. Compare all Loreweave alternatives.

How does Loreweave compare with other AI and agents MCP servers?

safety score 92/100 (higher than 90% of 4,460 AI and agents servers); tools 15 (the typical AI and agents server has 6); tools that change things 7% (typical: 0%. Fewer write tools means less an agent can break). Full comparison.