mcp server
io.github.0Mattias/bettermemory
Memory for coding agents, checked against the filesystem and git before it is believed.
Description as published by the maintainer. Source
- version 3.41.0
- active
- memory and context
active — Most recent push to the repository was 2026-08-06. Dashed tags are derived by ZBS Index from the published description, not stated by the maintainer.
Signals
These are separate measurements of different things. They are deliberately not combined into one score, because a popularity number that mixes website traffic with saves and stars cannot be checked or acted on.
| Signal | Value | What it measures | Window | Observed | Source |
|---|---|---|---|---|---|
| GitHub stars | 0 | Number of GitHub accounts that bookmarked this repository since it was created. It is a bookmark count, not installs, not active users and not quality. | cumulative, all time | GitHub | |
| Last commit | 2026-08-06 | Date of the most recent push to any branch. This is the strongest cheap indicator of whether the project is still maintained. | point in time | GitHub | |
| Open issues | 0 | Open issues plus open pull requests, as GitHub counts them together. A high number can mean an active project or an abandoned one. | as of fetch | GitHub | |
| Latest published version | 3.41.0 | Latest version string the maintainer published to the registry. | as of fetch | Model Context Protocol | |
| Registry record last updated | 2026-08-06 | When the registry record was last updated by its maintainer. | point in time | Model Context Protocol | |
| License | MIT | Licence GitHub detected in the repository. Detection can be wrong; the LICENSE file is authoritative. | as of fetch | GitHub | |
| First listed in the MCP Registry | 2026-08-06 | Date this server was first published to the official MCP Registry. Not a usage or quality measure. | point in time | Model Context Protocol | |
| repository status | active | The repository exists on GitHub and is not archived. This says nothing about how recently it was worked on. | as of fetch | GitHub |
Where to get it
Related, by what their authors tagged them
-
ai.atlaso/mcp
— last commit 2026-07-27, shares memory
AI memory layer — one shared, persistent memory across every AI tool you connect.
-
Synap Memory
— last commit 2026-08-06, shares memory
Persistent memory for AI agents — log and recall conversation context over MCP.
-
Threadminder
— last commit 2026-06-05, shares memory
Persistent context for Claude. Your AI always knows your projects and next actions across sessions.
-
bayramannakov-claude-reflect-claude-reflect
— last commit 2026-03-16, shares memory
Self-learning system that captures corrections during sessions and reminds users to run /reflect to update CLAUDE.md. U…
-
Amber
— last commit 2026-06-15, shares memory
Long-term memory for AI assistants. Hybrid retrieval, query expansion, auto-topics.
-
com.clauxel.agentmemorymcp/agentmemorymcp-mcp
— last commit 2026-05-21, shares memory
A paid remote MCP for agent memory MCP, built to return verdicts, receipts, usage logs, and audit-re
-
com.memxus/memxus
— last commit 2026-07-30, shares memory
Persistent memory layer that saves and recalls your project context and preferences.
-
com.ruddia/being-mcp-server
— last commit 2026-05-28, shares memory
Personality Runtime for AI agents — persistent memory, personality, and relationships via MCP
-
com.runmemento/memento
— last commit 2026-05-17, shares memory
Local-first, LLM-agnostic memory layer for AI assistants.
-
GrantAi Memory
— last commit 2026-03-16, shares memory
Persistent memory for AI agents. Infinite context with sub-millisecond recall.
These share tags the maintainers applied themselves, such as memory. Common tags like "mcp" or "ai" are ignored for this: agreeing with six hundred other projects is not a similarity.
This is not a recommendation and not a test result. It is a map of what the authors said their work is about.
How the author describes it
Topics the maintainer set on GitHub: claude, claude-code, mcp, mcp-server, memory.
Bring your own setup
We take apart real AI setups every week and show what broke, what cost too much, and what the trace actually said. If you run agents on real work, that is where the useful conversation is.
Join ZBS AI Practice Lab