Giving Claude Code persistent memory with a self-hosted MCP server
Claude memory without token costs, but requires running five services for one feature.

Another AI memory platform when Mem, Rewind, and Superhuman already own this space.
Teams and companies wanting AI assistants with full work context
Mem · Rewind AI · Superhuman AI
Claude memory without token costs, but requires running five services for one feature.
Runs extraction and search server-side so your local MCP is a tiny HTTP client — no local DBs, no giant RAM leaks, and an easy npx install and .mcp.json or global MCP registration. It exposes clear tools (save_memory, recall_memories, extract_memories, get_project_context) and adds project-scoped + global preferences — a pragmatic fix for Claude Code's tiny flat-file memory. The tradeoff is obvious: usefulness depends on the hosted API (privacy, uptime, cost), and the repo looks early-stage with minimal commits and docs beyond the quickstart.
Local RAG for Claude when Cursor and other editors already handle context.
Local RAG + MCP for Claude with zero external dependencies—elegant constraint execution.
Claude Code memory without Redis—138 lines of diskcache beats 'use a vector DB' conventional wisdom.
Hierarchical memory that persists across Claude Code, Cursor, and Windsurf—solve context amnesia.