Alternatives
Products that do what OpenContext does
Persistent, project-local memory for AI coding agent via MCP
- 1
- 2
- 3
- 4
- 5
- 6
- 7
- 8
- 9
- 10
- 11
- 12
- 13
- 14
- 15
- 16
- 17
- 18
The memory layer that decides what's worth remembering
13d ago · skynetlab-cortex.com
- 19
- 20PM
I built an MCP server that gives Claude Code long-term memory across sessions, backed by infrastructure you control. Every Claude Code session starts from zero, no memory of previous sessions. This server uses mem0ai as a library and exposes 11 MCP tools for storing, searching, and managing memories. Qdrant handles vector storage, Ollama runs embeddings locally (bge-m3), and Neo4j optionally builds a knowledge graph. Some engineering details HN might find interesting: - Zero-config auth: auto-reads Claude Code's OAT token from ~/.claude/.credentials.json, detects token type (OAT vs…
Feb 2026 · github.com
- 21PL
How it works: - Storage uses one SQLite database file, plus a local LanceDB index of vectors. No need for a server, cloud services, or any API keys. - Retrieval is a hybrid approach using BM25 (rank-bm25) and vector-based search (sentence-transformers) combined with a co-occurrence graph of entities, using reciprocal rank fusion. The idea is to find the right memory, not the closest one. - It plugs into the agent's lifecycle via MCP: before the agent responds, relevant memories are added to its input; after each turn, decisions and new learnings are automatically recorded. No need to…
Jun 2026 · github.com
- 22CM
I built an MCP server that connects coding agents (Claude Code, Cursor, OpenCode, Codex) to a collaborative workspace where your team and other AI models can review what the agent is planning. The problem: When Claude Code creates an implementation plan, it lives in your terminal session. Nobody else sees it until it becomes a PR. If you want GPT to check the architecture or a teammate to flag issues, you're copy-pasting between windows. This MCP server fixes that. When your agent creates a plan, it gets shared as a collaborative thread in CoChat. Engineers comment on it, other AI models…
Feb 2026 · github.com
- 23CO
So I've been building ClawMem, an open-source context engine that gives AI coding agents persistent memory across sessions. It works with Claude Code (hooks + MCP) and OpenClaw (ContextEngine plugin + REST API), and both can share the same SQLite vault, so your CLI agent and your voice/chat agent build on the same memory without syncing anything. The retrieval architecture is a Frankenstein, which is pretty much always my process. I pulled the best parts from recent projects and research and stitched them together: [QMD](https://github.com/tobi/qmd) for the…
Mar 2026 · github.com
- 24PM
This is my attempt in building a memory that evolves and persist for claude code. My approach is inspired from Zettelkasten method, memories are atomic, connected and dynamic. Existing memories can evolve based on newer memories. In the background it uses LLM to handle linking and evolution. I have only used it with claude code so far, it works well with me but still early stage, so rough edges likely. I'm planning to extend it to other coding agents as I use several different agents during development. Looking for feedbacks!
Jan 2026 · github.com
Ranked by how close each launch is in meaning, then by votes. Refine with a description →