CROW: LLM Wiki
OfficialRelated Servers
Alternatives to CROW: LLM Wiki
- AlicenseAqualityBmaintenanceMemory manager for AI apps and Agents using various graph and vector stores and allowing ingestion from 30+ data sources633,348Apache 2.0
- AlicenseBqualityAmaintenanceProvides semantic memory and persistent storage for Claude, leveraging ChromaDB and sentence transformers for enhanced search and retrieval capabilities.10282,503 PyPI2,132Apache 2.0
- AlicenseAqualityBmaintenanceBasic Memory is a knowledge management system that allows you to build a persistent semantic graph from conversations with AI assistants. All knowledge is stored in standard Markdown files on your computer, giving you full control and ownership of your data. Integrates directly with Obsidan.md21210,764 PyPI4,603AGPL 3.0
- AlicenseNot gradedqualityBmaintenanceBuild Real-Time Knowledge Graphs for AI Agents32,863Apache 2.0
- AlicenseNot gradedqualityAmaintenanceiwec gives AI agents structured access to your Markdown notes as a knowledge graph instead of a pile of files. Agents search, retrieve, traverse, and refactor your notes by structure and links — not blind text similarity — working from the same plain .md files you edit by hand. No database, no cloud, no lock-in.1,824Apache 2.0
- AlicenseBqualityBmaintenanceMindBase implements Karpathy's "LLM wiki" pattern as an MCP server. Instead of retrieving chunks at query time (RAG), the LLM maintains a persistent wiki between your conversations: it reads every source you feed it, cross-references pages with [[wikilinks]], flags contradictions between sources, and keeps a context.md that reflects your current synthesized thinking.504 npm137MIT
Related Servers
- AlicenseNot gradedqualityAmaintenanceEnables AI agents to capture, structure, remember, and retrieve source-backed memory as local Markdown files, with reviewable writes and no cloud dependency.218MIT
- AlicenseAqualityBmaintenanceEnables LLMs to maintain persistent memory by reading and writing Markdown notes and sibling image assets in a user-selected local or sync folder, with no cloud service, account, or server to run.111,197 npmMIT
- AlicenseAqualityBmaintenanceEnd-to-end-encrypted markdown notes that double as agent memory: on-device semantic search (no API key), scoped and revocable agent keys, a hosted connector for Claude.ai and ChatGPT, and a self-hostable relay that stores ciphertext only.999 npmMIT
- AlicenseNot gradedqualityBmaintenanceGives AI agents a long-term memory layer over plain Markdown notes, letting them run ranked, citable searches, record new facts, and inspect conflicts and stale entries. Results carry freshness labels, supersession history, and audit fields like search timestamp and no-match status so agents can prove a search actually ran.MIT
- AlicenseNot gradedqualityCmaintenanceGives AI agents a durable, locally hosted temporal memory built from a markdown vault you own, exposing hybrid semantic/lexical/entity search over events, threads, transcripts, entity relationships with validity dates, and patterns with confidence decay. Writes are approval-gated, so agents can draft, commit, and sync new memories while keeping every index rebuildable and nothing leaving your machine.MIT
- AlicenseNot gradedqualityBmaintenanceEnables MCP clients such as Claude Desktop, Cursor, Zed, and Windsurf to recall associative context from a folder of markdown notes, combining vector search entry points with one-hop [[wikilink]] graph expansion and cross-encoder reranking over a single SQLite file. It also appends a zero-token per-turn ledger of asks, files, tools, and decisions that agents can consult across sessions.253 PyPI15MIT
TDQS
Scored across 18 tools
Each tool targets a distinct operation in the memory lifecycle: recall answers, search finds, read_note reads, and the area proposal tools (proposals, propose_area, confirm_area, create_area) are separate steps with explicit cross-references. No two tools appear to do the same job.
All names use lowercase snake_case, and most follow verb_noun (create_area, move_note, sync_folder, remember_file). The plural-noun list tools (proposals, folders) and bare verbs (recall, search) are minor deviations but remain readable and predictable.
18 tools for a full memory system with notes, areas, import, jobs, and rebuild is slightly above the ideal 3–15 range. However, each tool covers a distinct operation, so the surface feels rich rather than redundant.
The set covers note create/read/delete/move, area create/list/rename/describe/merge, file and folder import, and rebuild. Notable gaps remain: no explicit note update/edit tool and no way to list notes within a folder; deleting an empty area is only possible through a merge workaround.