Best Agent memory MCP servers
Agent memory MCP servers give a model somewhere to keep what it learns between sessions, and a way to pull the right part of it back into the context window when a task needs it. They are the cross-session layer of context engineering: the window holds one session, and memory decides what the next session starts with.
The servers here split on three questions. Who writes the memory: the agent, by deciding to call an add or save tool, or a recorder that captures every session without anyone choosing to. Who can read it: one user on one machine, one app's end users, or a whole team with permissions per fact. And what comes back: raw matching chunks for the model to sort through, or an answer with sources. Local servers such as the Memory reference server, Basic Memory and claude-mem keep files or a database on your machine. Memory APIs such as Mem0, Supermemory and Zep's Graphiti store what your agent or app sends them. Glen records a team's agent sessions, Slack, GitHub and tickets into one org-wide memory and returns a cited answer, with newer decisions superseding older ones.
14 servers
Glen
Glen
Shared memory for a team's coding agents: recorded sessions, Slack, GitHub and tickets, recalled with a source on every claim.
claude-mem
Alex Newman (thedotmack)
claude-mem's MCP server searches the observations its hooks record from your agent sessions, stored locally in SQLite with FTS5 and a Chroma index.
Memory
Anthropic (reference)
Reference MCP server giving an agent a persistent local knowledge graph of entities, relations, and observations.
Mem0
Mem0
Mem0's hosted MCP server: add, search, update, and delete long-term memories in your Mem0 Platform account, scoped by user, agent, app, or run.
MemPalace
MemPalace
Local MCP server that files conversation history and project files verbatim into wings, rooms and drawers, then searches them semantically.
Cognee
Topoteretes (Cognee)
Cognee's MCP server: remember, recall and forget over a knowledge graph built from text, files and code, plus a code-graph search tool.
Zep Graphiti
Zep
Zep's self-hosted Graphiti MCP server: turn episodes into a temporal knowledge graph of entities and facts, then search it from any MCP client.
Supermemory
Supermemory
Supermemory's hosted MCP server: save documents, search extracted memories, and read a profile per space, over OAuth at mcp.supermemory.ai.
ByteRover
ByteRover
ByteRover's brv mcp server: query and curate a project's context tree, versioned topic files in .brv/context-tree/, with no LLM call in either tool.
LongMemory (formerly OpenMemory)
CaviraOSS
CaviraOSS's self-hosted memory engine, formerly OpenMemory: sector-classified memories with decay, plus a temporal fact graph, over stdio or HTTP MCP.
Basic Memory
Basic Machines
An MCP server over a folder of Markdown notes that you and the agent both edit, indexed in SQLite for hybrid full-text and vector search.
MCP Memory Service
doobidoo (Henry Krupp)
Self-hosted Python memory server with hybrid vector and BM25 search, an entity graph, scheduled consolidation, and an OAuth-protected remote mode.
Letta
Oculair Media (community)
Community MCP server for Letta: manage stateful Letta agents, their memory blocks, archival passages, tools, and sources from any MCP client.
Pieces
Pieces
Local MCP endpoint in PiecesOS that lets an agent query Pieces Long-Term Memory: captured screen, clipboard and audio activity on one machine.