brain-core
Related Servers
Alternatives to brain-core
- AlicenseAqualityAmaintenanceLocal-first AI PKM memory server for coding conversations. Imports Claude Code, Cursor, Codex CLI, Trae, and GitHub Copilot chats into notes, semantic search, tag graphs, Markdown exports, and MCP memory tools.7121 npm61Apache 2.0
- AlicenseAqualityAmaintenanceIndexes the session histories Claude Code, Codex CLI and opencode already write into a local searchable memory. MCP recall tools, session-start auto-recall, secret redaction at index time, cross-machine sync over SSH.12,379 npm1,367MIT
Related Servers
- AlicenseBqualityBmaintenancePersistent memory for AI agents built on the LLM Wiki pattern: a plain-Markdown brain (also a valid Obsidian vault) with SQLite metadata, local semantic search via fastembed (no API keys), one-call session context with project auto-detection, and a decision log with rationale. Works with Claude Code, Claude Desktop, Cursor, and any MCP client.31MIT
- AlicenseAqualityAmaintenancePersistent memory for AI coding agents, storing decisions, bug fixes, conventions, and discoveries in a local SQLite database and automatically recalling them when relevant. Works with Claude Code, Codex, Cursor, Gemini CLI, and other MCP-compatible agents.224MIT
- AlicenseAqualityCmaintenanceEnables coding agents to keep durable long-term memory in a folder of human-readable Markdown notes: search and read notes by ranked recall, encode new ones, link related ideas, retire contradicted notes in favor of replacements, and re-validate them — all backed by a disposable SQLite index. Plugs into Claude Code, Claude Desktop, Cursor, or any MCP client.7MIT
- AlicenseAqualityBmaintenanceA local-first shared memory layer for MCP-aware agents like Claude, Codex, and Hermes, enabling persistent memory across chats and clients via Markdown files and SQLite FTS.62MIT
- AlicenseAqualityCmaintenancePersistent memory + FTS5 full-text search for Claude Code conversation history. Indexes ~/.claude/projects/ JSONL into SQLite, exposes 10 MCP tools (store/recall/search memories, browse sessions, get summaries) plus prompts. Includes a web UI for visual exploration1046 npm97MIT
- AlicenseAqualityCmaintenanceLocal-first memory for Claude Code and any MCP client: hybrid vector + keyword search and a bi-temporal knowledge graph in one SQLite file. Local embeddings, no API key, $0/token.51249 npm2PolyForm Noncommercial 1.0.0
TDQS
Scored across 5 tools
Each tool occupies a distinct slot: search (brain_recall), ingest (brain_distill), write a fact (brain_remember), session lifecycle (brain_session), and health/diagnostics (brain_status). Every description ends with an explicit 'Not for X (brain_Y)' boundary statement, so an agent has no path to confuse one with another.
All five tools share a strict `brain_` prefix followed by a single lowercase token, which reads as a coherent namespace. Minor deviation: recall/remember/distill are verbs while session/status are nouns, so the pattern is prefix-consistent but not uniformly verb_noun.
Five tools is tight and each earns its place: with the memory domain you need read, write, ingest, session boundary, and diagnostics, and nothing is redundant. brain_session reasonably bundles start/end into one phase-parameterised tool rather than splitting into two.
The read/write/ingest/lifecycle/diagnostic loop is fully closed, including partial-failure reporting and duplicate/contradiction handling. The gap is that memory is strictly append-only: there is no forget/prune/retract or explicit edit path, so a user cannot remove an obsolete item, and brain_status hints at 'maintenance' for which no tool exists.