ContextForge – Persistent memory MCP server for Claude
Claude memory is solved—Pinecone, LLamaIndex, and Continue already do this.
Development memory that flows between sessions. An MCP server that gives Claude persistent memory about your projects.
Local-first dev memory with Git sync beats hosted alternatives for privacy-conscious teams.
Developers using Claude Desktop who want persistent project context
Bossa · Mem0 · Recall
Claude memory is solved—Pinecone, LLamaIndex, and Continue already do this.
MCP-native persistent memory prevents re-explaining projects to Claude every session.
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.
Cross-project memory for AI agents when single-project solutions already exist.
Hierarchical memory that persists across Claude Code, Cursor, and Windsurf—solve context amnesia.
SQLite-backed MCP server gives local agents shared memory without vector DB overhead.