Persistent long-term memory for Claude Code via MCP — captures coding decisions, bugfixes, and context across session...
Copy the install, test the workflow, then decide if it earns a permanent slot.
Still active enough to matter. Good candidate for a fast stack test instead of a long evaluation loop.
Copy the install, test the workflow, then decide if it earns a permanent slot.
You can test this quickly and remove it cleanly if it misses.
GitHub health 42/100. no security policy. 0 open issues make this testable, but not something to trust blind.
AI Agent
Claude Code
Model
Claude
Fastest way to find out if claude-mem-lite belongs in your setup.
Copy the install command, run a real test, and back it out cleanly if it slows you down.
claude mcp add claude-mem-lite -- npx claude-mem-liteRun this first. You will know quickly if the workflow earns a permanent slot.
claude mcp remove claude-mem-liteNo messy cleanup loop. If it misses, remove it and keep moving.
Install Location
~/ └─ .claude.json └─ mcp_servers/ └─ claude-mem-lite ← registers here
Persistent long-term memory for Claude Code via MCP — captures coding decisions, bugfixes, and context across sessions. Hybrid FTS5 + TF-IDF search with episode batching. Single SQLite DB, no external services. Alternative to claude-mem with 600x lower cost.
Source: GitHub repository
Source check: July 23, 2026
Upstream commit: July 20, 2026
Repository state: Not marked archived
Honeystax upvotes are community interest signals, not star ratings. GitHub stars and repository health are source measurements; editorial risk and trial-cost notes are Honeystax analysis.