Catalog Systems Claude Code memory mechanisms local-memory-mcp

local-memory-mcp

https://github.com/studiomeyer-io/local-memory-mcp

SQLite + FTS5 + BM25 ranking. Stores learnings, decisions with reasoning and alternatives , entities, observations. Loads context from last 3 sessions. Only server that captures why a decision was made + alternatives considered.

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

At a glance

Type
SQLite + FTS5 with decision-tracking repo fix
Tier
T2
Section
Claude Code memory mechanisms
Created
2026-04 repo fix
Latest release
v2.4.3 (2026-08-19) repo fix
License
MIT repo fix
GitHub
studiomeyer-io/local-memory-mcp — ~13 stars, 86 commits repo fix
Pricing
free / open source (MIT); no paid tier repo fix
Funding
not applicable — not commercial fix
Freshness
2026-10-22 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
Protocols
mcp-server repo fix

Memory taxonomy

storage
relational
retrieval
exact-match
persistence
long-term
update
overwrite
unit
fact
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

Local-only MCP memory server — no cloud round-trip; fastest possible memory ops.

Cons

Local-only; no cross-device sync; smaller community.

Claims & capabilities

Zero config, no cloud, no API keys. npx @studiomeyer/local-memory-mcp .

Technical surface

API surface
searched not found
Backend storage
searched not found
Deployment
local — SQLite + FTS5; zero cloud dependency; no API keys required
Embedding model
searched not found
Multi-tenancy
searched not found
MCP
native (first-party)
A2A
not supported
OpenTelemetry
no

Alternatives to local-memory-mcp → live options ranked by shared design, licence, hosting and MCP support

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-brain T2

    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.

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

Sources (42 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-04-21” → “v2.4.3 (2026-08-19)” source
    #195

Related systems

References (2)