a-mem-mcp vs code-session-memory
Memory tools for coding agents compared
a-mem-mcp and code-session-memory help coding agents retrieve context from earlier work. a-mem-mcp builds and updates a connected graph of manually added project memories, while code-session-memory automatically indexes conversations from several coding tools for semantic search.

a-mem-mcp: Evolving Memory for Coding Agents
A-MEM MCP brings the A-MEM self-evolving memory approach to coding agents, organizing project knowledge as a connected graph stored in ChromaDB. It is currently tested with Claude Code and suits agents that need to recall and connect past project decisions.

code-session-memory: Search AI Coding Sessions with OpenAI Embeddings
code-session-memory indexes sessions from OpenCode, Claude Code, Cursor, VS Code, Codex, and Gemini CLI into shared, searchable memory using OpenAI embeddings. It stores data locally with SQLite and sqlite-vec by default, with PostgreSQL and pgvector as an optional shared backend.
| a-mem-mcp | code-session-memory | |
|---|---|---|
| Language | Python | TypeScript |
| License | MIT | — |
| Stars | 35 | 20 |
| Forks | 3 | 2 |
| Last analyzed | Oct 28, 2026 | Oct 30, 2026 |
Key differences
- a-mem-mcp focuses on adding and connecting project notes; code-session-memory indexes coding-agent session messages automatically.
- a-mem-mcp is tested with Claude Code, with support for other MCP-compatible agents planned; code-session-memory supports OpenCode, Claude Code, Cursor, VS Code, Codex, and Gemini CLI.
- a-mem-mcp is written in Python and offers a Python API; code-session-memory is written in TypeScript and requires Node.js 22 or later.
- a-mem-mcp stores memories in ChromaDB; code-session-memory uses SQLite with sqlite-vec by default and offers PostgreSQL with pgvector for shared storage.
- a-mem-mcp is MIT-licensed; code-session-memory's README says MIT, and its license file should be verified before relying on those terms.
- a-mem-mcp has had no commits in the last 90 days; code-session-memory has recent commits, with development concentrated mostly in one contributor.
Choose a-mem-mcp if you…
- want to build a connected, evolving record of project decisions and implementation details.
- prefer to add and manage memories through MCP tools or a Python API.
- need an approach tested with Claude Code and backed by ChromaDB.
Choose code-session-memory if you…
- want to search sessions across several supported coding agents in one database.
- need automatic indexing, session browsing, or restart summaries.
- want local SQLite storage by default or an optional PostgreSQL backend for multiple machines.
Compare the numbers side by side, or add more projects
This comparison is generated with AI from the OSRepos analyses of both projects. Always check each project's repository and documentation before choosing.