ContextForge – Persistent memory MCP server for Claude
Claude memory is solved—Pinecone, LLamaIndex, and Continue already do this.

Persistent memory for Cursor and Claude when every chat resets to zero.
Developers using Cursor IDE or Claude for coding
Continue.dev · Cursor built-in context · Mem0
Claude memory is solved—Pinecone, LLamaIndex, and Continue already do this.
Hierarchical memory that persists across Claude Code, Cursor, and Windsurf—solve context amnesia.
Consolidates scattered AI memory from Claude, ChatGPT, and MCP into one searchable space.
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.
Finally, shared memory across Claude Desktop and Cursor without cloud accounts.
Claude memory without token costs, but requires running five services for one feature.