mcp-memory-service
MCP Memory Service gives AI assistants memory that survives new chat sessions. The README's pitch is that you stop re-explaining your project: it captures project context, architecture decisions and code patterns, and a fresh session can recall them. It works with any MCP-compatible client, and the README names Claude Code, Claude Desktop, Cursor, VS Code, Windsurf, Aider, Zed, Continue and many others. The feature list covers OAuth and team collaboration, a document ingestion system, memory consolidation, a memory type ontology and a dashboard.
Install with `pip install mcp-memory-service`, then either run the quick installer (`python -m mcp_memory_service.scripts.installation.install --quick`) to configure Claude Desktop with a SQLite backend, or add a `memory server` entry to your MCP config by hand. For production or team use you can clone the repo and run the installer to pick SQLite (local, single user), Cloudflare (cloud, multi-device sync) or a hybrid of the two. The README also says it is compatible with the SHODH unified memory API specification and carries notes on Python 3.13 and macOS SQLite extension support. It is Apache licensed.
Features
Why choose it
Trade-offs
Maintenance check
- Last commit
- 2026-10-25
- Commits, last 90 days
- 100+
- Releases, last 90 days
- 30
- Latest release
- v12.3.1 (2026-10-23)
- Open issues
- 28
- Recent issues with at least one comment
- 9/12
Oldest week on the left; the latest four weeks are orange. Source: GitHub commit activity.
Status rule: archived on GitHub = Archived; last commit within 90 days = Active; 91 to 365 days = Slowing; older = Stale. All figures come from the GitHub API on the date shown.
Most discussed open issues
- #1146 logging: 573 unsanitised f-string logger calls remain outside the three files #1119 cleared51 comments · 2026-09-06
- #1359 Maintainer triage digest28 comments · 2026-09-28
- #1346 RFC: harvest design-extraction — capturing long-form reasoning and tool-results the pipeline drops6 comments · 2026-09-27
- #1181 [First-time contributor] Looking for beginner-friendly issues to contribute6 comments · 2026-09-08
- #1526 hooks: inbox for inter-agent messages (sentinel tags since the last check)5 comments · 2026-10-14
Issue titles are quoted from GitHub. Open the link to check whether a problem still applies to the version you use.
Who it fits
- You use Claude Code, Claude Desktop, Cursor, VS Code or another MCP client and want chat sessions to stop starting from zero.
- You want a choice of storage: local SQLite, Cloudflare for multi-device sync, or a hybrid.
- You need team features: the README lists OAuth, a dashboard and document ingestion.
- Your problem is codebase navigation rather than conversation memory; a code-graph tool or a project scaffold fits better.
- You handle sensitive material and cannot put it in a persistent store, especially with cloud sync.
- You want a short README to start from: it mixes release notes with documentation.
How it differs
vs letta★ 25.3kLetta replaces your assistant with its own long-lived agent. MCP Memory Service keeps your assistant and adds memory behind MCP.
vs mex★ 1.8kmex stores memory as plain markdown files in your repo, so it is reviewable and diffable. MCP Memory Service stores it in a database that survives across projects and sessions.
Compatibility
Quick start
Use cases
Alternatives
Featured in these lists
Comments
No comments yet. Be the first!