claude-brain

https://github.com/memvid/claude-brain

Claude Code plugin packaging of Memvid (see Dedicated memory layers). Wraps the Memvid .mv2 single-file store as a slash-command-installable plugin so per-project memory becomes a git-committable file inside the repo.

Active · Verified 2026-10-23 · fresh as of 2026-10-23 · 44 cited facts, 0 with a third-party source · 1 recorded change · Suggest a correction

At a glance

Tier
T2
Created
2025-12 repo fix
Latest release
v1.0.7 (2026-01-05) repo fix
License
MIT repo fix
Pricing
free / open source repo fix
Funding
not applicable — not commercial fix
Freshness
2026-10-23 fix
Layer
agent-infra repo fix
Licensing
open-source repo fix
Deployment locus
local repo fix
Platform vs product
product repo fix
SDK languages
typescript repo fix

Memory taxonomy

storage
file
retrieval
similarity
persistence
long-term
update
append-only
unit
chunk
governance
inspectable
conflict
append

When to use

Optimised for: Claude-Code-native + MCP-portable memory

Anti-fit: not for non-Claude-Code clients (some are MCP-portable)

Pros & cons

Pros

Claude Code plugin that bundles Memvid as the per-project memory store; git-committable single-file.

Cons

Plugin layer on top of Memvid — adds another moving part for the same underlying engine.

Claims & capabilities

Plugin distribution of an existing engine — claims inherit from Memvid (sub-ms reads, single-file portability).

Technical surface

API surface
searched not found
Backend storage
searched not found
Deployment
local
Embedding model
searched not found
Multi-tenancy
searched not found
MCP
native (first-party)
A2A
not supported
OpenTelemetry
no

Similar systems

Other claude code memory mechanisms in the catalog, ranked by inbound references.

  • Official MCP Memory server T1

    Knowledge-graph-based persistent memory MCP server — the canonical reference implementation. npx -y @modelcontextprotocol/server-memory ; configurable via MEMORY_FILE_PATH .

  • Claude Code auto-memory T1

    Persistent file-based memory at ~/.claude/projects/<project>/memory/ with a MEMORY.md index plus typed memory files (user / feedback / project / reference). Loaded into context across sessions.

  • Claude-CursorMemoryMCP T2

    FastAPI server. RBAC + API-key auth, encryption, backup/recovery, embedding pipeline with deduplication. Only server in this list with role-based access control over pgvector.

  • claude-mem T1

    Hooks into Claude Code's session lifecycle; compresses tool outputs into ~500-token observations via Claude's agent SDK. SQLite + FTS5 with optional Chroma vector. "Endless Mode" compresses in-flight to extend session length. Captures what the agent did , not just what the user typed.

  • claude-supermemory T2

    Wraps Supermemory cloud API. Team memory shared across project members, separate from personal memories. Auto-capture on session end; per-repo config.

  • codebase-memory-mcp (DeusData) T1

    High-performance MCP server building persistent code knowledge graphs via AST. 155 languages via vendored tree-sitter; SQLite + WAL; single static binary; zero runtime deps. Knowledge graph: Project/Package/File/Module/Class/Function/Method/Interface/Enum/Type/Route/Resource nodes; CALLS/IMPORTS/DEFINES/IMPLEMENTS/INHERITS/HTTP_CALLS/ASYNC_CALLS/EMITS/LISTENS_ON/DATA_FLOWS/SIMILAR_TO/SEMANTICALLY_RELATED edges. 14 MCP tools incl. Cypher-like query.

Sources (43 cited facts, 0 third-party)

Each fact links to the page it came from; the badge says who published it (how to read sources).

What changed

Changes to this record's lifecycle, licence, release, pricing and hosting facts, from the catalog's git history. Subscribe (Atom)

  1. 2026-10-22
    • Latest release “v1.0.7 2026-01-05” → “v1.0.7 (2026-01-05)” source
    #195

Related systems

References (3)

  • Anthropic Claude (foundation models) depends on at runtime — adjacent-infrastructure cell: requires Claude Code or MCP client; BYO storage
  • Memvid builds on · same team as — claude-brain packages memvid (same GitHub org memvid/) as a Claude Code plugin; cross-listings note flagged this pair.
  • Model Context Protocol (MCP spec) depends on at runtime — adjacent-infrastructure cell: requires Claude Code or MCP client; BYO storage