claude-mem MCP alternatives
claude-mem is the most popular session-recording memory for coding agents. Hooks in Claude Code, Codex, Cursor, OpenCode and others capture each session, an observer model compresses tool use into typed observations, and relevant context is injected when the next session starts. Everything is stored in SQLite on your machine, with Chroma for search by meaning, and the MCP server adds a three-step search, timeline and fetch flow.
It gets the hard part right: memory is recorded, not saved by hand. What it doesn't do is leave your machine. If the context your agent needs was worked out in a teammate's session, claude-mem never sees it. That is the gap Glen fills, so it comes first.
The 9 best alternatives
- GlenOur pick
The same automatic recording, shared across your whole team
claude-mem records sessions the way Glen does, then keeps them on one developer's machine. Glen records every teammate's sessions plus Slack, GitHub and tickets into one memory, so your agent gets what the rest of the team worked out.
Recorded automaticallyClaude CodeCodexCursorSlackGitHubLinearNotionCall transcriptsOne memory for your orgSourced, permissioned per fact, newer decisions winEvery teammate's agentClaude CodeCodexCursorGets one cited answer, injected into the session before it goes looking.29%fewer tokens across 100 replayed PRs21%faster, measured end to endParity+quality on withheld testsclaude-memGlenWho writes memoryRecorded by hooksRecorded from every session and toolWho can read itOne machineYour whole org, permissions per factWhat the agent getsAn index, then records to fetchOne cited answer, injected in-sessionWhen a decision changesOlder observations still surfaceThe newer decision replaces the older Mem0 runs an LLM over whatever the agent passes to add_memory, extracts discrete memories, and returns them through semantic search from a hosted endpoint at mcp.mem0.ai. It is built for per-user memory inside an application: every memory hangs off a user_id, agent_id or run_id, nothing is written unless the agent decides to call add_memory, and search hands back matching memories rather than an answer with sources. The self-run mem0-mcp package is archived and Mem0's OpenMemory was sunset in July 2026, so the hosted server is the only maintained route.
Set up Mem0 →MemPalace keeps conversations and files verbatim, without summarizing, and files each piece into wings and rooms so a search can be scoped to one person or project; ChromaDB with local embeddings does retrieval, and a SQLite graph tracks facts with validity windows. Hooks for Claude Code, Codex and Cursor save sessions automatically. A palace lives on one machine unless you run your own HTTP hub, search returns raw drawers for the agent to read rather than an answer, and its 47 tool definitions sit in every session's context window.
Set up MemPalace →Cognee runs an LLM pipeline over what it is given, extracting entities and relationships into a knowledge graph beside vector embeddings, and recall picks among graph, RAG, temporal and Cypher strategies. It runs locally on SQLite, LanceDB and an embedded graph and needs your own LLM key. Each MCP client writes to its own dataset by default, so Claude Code and Cursor on one machine don't share memory unless you change COGNEE_MCP_AGENT_SCOPED, and nothing is stored until the agent calls remember.
Set up Cognee →Graphiti, the open-source library under Zep's commercial product, is the most careful about time of anything on this list: facts are graph edges with validity timestamps, and a newer episode that contradicts an older fact invalidates it. You run it yourself on FalkorDB or Neo4j with your own LLM and embedding keys, and the README calls the MCP server a reference implementation with no authentication, so anyone who reaches the port can read or clear the whole graph. Episodes still arrive only when the agent calls add_memory.
Set up Zep Graphiti →Supermemory's hosted server turns content the agent saves into documents, extracts memories from them asynchronously, and returns matches with a similarity score and the source document's ID. Spaces partition memory per project or user, and clients with MCP Apps support get a space picker and an interactive memory graph. Through this server, memory enters when the agent or the user calls a save tool, so what a space holds is whatever someone remembered to store.
Set up Supermemory →ByteRover keeps project knowledge as topic files in a .brv/context-tree directory inside the repository, with git-style branches and merges and optional cloud sync for a team. Its MCP server is deliberately small: brv-query runs BM25 over the tree and brv-curate saves a topic the agent wrote. Knowledge enters only when an agent or a person curates it, so the tree holds what someone chose to document, which is the AGENTS.md problem with better tooling.
Set up ByteRover →LongMemory, the CaviraOSS project published until recently as OpenMemory and unrelated to Mem0's product of that name, sorts memories into five sectors that decay at different rates and links them through a waypoint graph. It is six tools over a local SQLite file, with a user_id on each call to keep users apart. It records only what the agent chooses to store, and the team-aware rewrite on its main branch was not on npm when we checked.
Set up LongMemory (formerly OpenMemory) →Basic Memory writes memory as plain Markdown in a folder you choose, parses observations and wiki-link relations into a graph, and indexes it in SQLite for hybrid search. The files open in Obsidian and diff cleanly in git, and Basic Memory Cloud serves the same 17 tools over OAuth with shared workspaces. A note exists only when the agent calls bm_write or bm_edit, so the memory is exactly as complete as the agent's judgment about what was worth writing down.
Set up Basic Memory →
How to choose
If you work alone and want automatic, local session memory, claude-mem is the strongest free option. If your agents need what your teammates worked out, Glen records the same kind of sessions for the whole organization, adds your team's tools, and returns cited, reconciled answers. MemPalace is the other automatic, local recorder; Mem0 and Supermemory are hosted memory APIs; Basic Memory and ByteRover hold curated notes.
FAQ
- What is the best claude-mem alternative for teams?
- Glen. It records sessions through hooks the way claude-mem does, but stores them in one memory shared across your organization, with per-observation access control and Slack, GitHub, Linear and Notion alongside the sessions.
- Does claude-mem share memory between developers?
- By default no: memory is stored in SQLite on each machine. Its TeamBrain sharing feature was a pilot without public pricing when we checked.
- Can I move from claude-mem to Glen?
- Glen can import past Claude Code, Codex, Cursor and Pi transcripts from your machine with glen import, so the team memory starts with your history rather than empty.