Bettermemory MCP server
io.github.0Mattias/bettermemory·v8.0.0Memory for coding agents, checked against the filesystem and git before it is believed.
0 stars854 downloads/wk
Reviews
Write oneNobody has reviewed Bettermemory yet.
If you have run it, two minutes of your experience saves the next person an afternoon.
Bettermemory tools
No tool declarations could be read from the package source. They show once the server is installed.
Public scan report
scanner v0.1.10 · 2026-10-02 · same rubric, same numbers if you re-run it
- Code scan107 source files scanned25/25
- –Live reliabilityno gateway calls yet and no remote to proben/a
- –Tool poisoningtools not inspected (local package is not executed); not countedn/a
- Auth qualitylocal package, no credentials required12/15
- Maintenancelast push 3 days ago15/15
- Maintainer identityregistry namespace matches repository owner; GitHub account older than a year8/10
How Bettermemory compares
Against every graded Developer tools MCP server, from our own scans and uptime checks. Updated after each scan run.
- Safety score
- 92/100
- higher than 90% of 1,119 Developer tools servers
- Downloads a week
- 854
- more than 91% of 436 Developer tools servers with a package
Release history: 3 versions in the registry since 2026-09-17, latest 2026-09-24, typically one every 4 days.
Install Bettermemory in Claude Code, Cursor or VS Code
claude mcp add bettermemory -- uvx bettermemory
What the publisher says
From the Bettermemory repository's README, as published. We do not edit it. Read it on GitHub
<!-- mcp-name: io.github.0Mattias/bettermemory -->
An MCP memory server for coding agents. Stored facts get checked against the filesystem and git before the model relies on them, so a memory that has rotted is flagged instead of quoted back at you.
Install
Claude Code — two slash commands, zero config:
/plugin marketplace add 0Mattias/bettermemory
/plugin install bettermemory@bettermemoryAnything else that speaks MCP:
uv tool install bettermemory
bettermemory init --client claude-desktop # or cursor / cline / claude-code / hermesRestart the client. bettermemory doctor exits 0 when it's wired correctly and prints a one-line fix for anything that isn't.
Try it without installing: uvx bettermemory try writes a memory citing a file, deletes the file, and shows the next search flagging it. Offline, throwaway store.
What it does
verdict: calendar age, whether the paths it cites still exist, the commits landed since it was last confirmed, and how the record entered the store (written here, pulled, or placed by hand). Declared claims (path, path::symbol, path::NAME=literal) are re-checked against the working tree; a claim that stops being true blocks the stamp instead of riding along.
- Checks memory before believing it. Every hit carries a staleness
injection. Write gates bounce transient state, secret-shaped tokens and near-duplicates; claims about you stage for confirmation.
- Retrieval is deliberate. Memory is a tool call, not an
keyword + BM25, fused — over your own vocabulary. No embedding models, no downloads, nothing to warm up, same answer every time.
- The code is the model. Search is deterministic lexical ranking —
git-syncable, no cloud, no account. The SQLite index beside the files is a derived cache you can delete; bettermemory reindex rebuilds it.
- Plain files. One markdown file per memory. Greppable,
run-state without polluting durable search; health telemetry and curation tools surface what drifted, what went cold, and what contradicts what.
- Rot gets acted on, not accumulated. Episodes journal per-session
preregistered benchmarks whose frozen result artifacts — misses included — live in [bench/][bench] (results/*.json, each carrying the declared terms it was scored under), and bettermemory eval scores whether memory actually helped against your own log ([ours is published][eval-results]).
- Receipts, not adjectives. The claims above are measured by
For agents
You were likely handed this link with "set this up." On Claude Code, the two plugin commands above are the whole install — skip to step 3. Everywhere else, steps are idempotent and safe to re-run:
Shortened. The full README is on GitHub.
Nothing above is checked by us. What we check is on the safety report.
Bettermemory: common questions
- Is Bettermemory MCP server safe?
- Yes, by our scan: it is graded A (92/100). Read the Bettermemory safety report
- How do I install Bettermemory?
- It runs on your machine. Copy the Claude Code, Cursor, VS Code or Claude Desktop config from the install section.
- Does Bettermemory need an API key?
- Not as far as the registry entry and our scan can tell: no credentials are declared or required.
- Is Bettermemory maintained?
- The last commit was 35 days ago (2026-09-30). The latest release is v8.0.0.
- What can I use instead of Bettermemory?
- Servers from other publishers that do the same job: Nexusmem MCP server, Agent Memory MCP server and Repowise MCP server. Compare all Bettermemory alternatives.
- How does Bettermemory compare with other Developer tools MCP servers?
- safety score 92/100 (higher than 90% of 1,119 Developer tools servers); downloads a week 854 (more than 91% of 436 Developer tools servers with a package). Full comparison.
Alternatives to Bettermemory
Same job from other publishers: the closest match first, then the best rated.
- NexusmemLocal-first memory for AI coding agents: shell history with exit codes, git diffs, docs, MCP.not reviewedGrowingA
- Agent MemoryGit-native project memory for AI coding agents: Markdown source of truth, reviewable, secret-safe.not reviewedGrowingA
RepowiseCodebase intelligence for AI coding agents — graph, git history, docs, decisions, code health.not reviewedEstablishedB- PalinodeInspectable, correctable project memory in git-versioned Markdown for AI agents.not reviewedEstablishedC
- argotRead-only context and complete checks against patterns learned from git history. Local; no LLM.not reviewedEstablishedB