mcp-memory-rs MCP server
Local-first agent memory: versioned JSON categories, BM25 search, per-device ACL, fleet sync.
2 stars
Reviews
Write oneNobody has reviewed mcp-memory-rs yet.
If you have run it, two minutes of your experience saves the next person an afternoon.
mcp-memory-rs tools
No tool declarations could be read from the package source. They show once the server is installed.
Public scan report
scanner v0.1.9 · 2026-09-27 · same rubric, same numbers if you re-run it
- –Code scanremote-only server, no package to scann/a
- –Live reliabilityno gateway calls yet and no remote to proben/a
- –Tool poisoningtools not inspected (local package is not executed); not countedn/a
- Auth qualityno auth information5/15
- Maintenancelast push 12 days ago15/15
- Maintainer identityregistry namespace matches repository owner; GitHub account older than a year8/10
How mcp-memory-rs compares
Against every graded AI and agents MCP server, from our own scans and uptime checks. Updated after each scan run.
- Safety score
- 70/100
- higher than 37% of 4,460 AI and agents servers
- GitHub stars
- 2
- more than 65% of 2,711 AI and agents servers
Install mcp-memory-rs in Claude Code, Cursor or VS Code
The registry entry has no remote endpoint or installable package.
What the publisher says
From the mcp-memory-rs repository's README, as published. We do not edit it. Read it on GitHub
mcp-memory-rs
Local-first MCP memory server in pure Rust. Persistent, versioned, queryable memory for AI agents — owned by the user, not by a platform.
State lives on your disk as plain JSON categories backed by SQLite (FTS5). Every write is versioned and backed up. A fleet of devices syncs through an optional HTTP endpoint with merkle manifests and optimistic concurrency. No cloud account, no embedding service, no network dependency in the default mode.
Why
Agent memory tied to a vendor dies with the vendor session. This server keeps the agent's long-lived state — identity, projects, infrastructure notes, per-device workflows — in files you can read, grep, diff, and back up yourself. Any MCP client (Claude Code, Codex, or anything speaking MCP stdio) gets the same memory; swapping the model does not lose the state.
Design choices that follow from that:
Sync is a separate, explicit step — never a hidden dependency.
- Local-first: the stdio server works fully offline against local storage.
database can be rebuilt from the files; the files are the truth.
- Plain storage: one JSON file per category plus a SQLite index. The
backup first. memoryhistory and memorycompact manage the tail.
- Versioning by default: every write keeps history; deletes create a
concurrent agents into explicit conflicts.
- Concurrency-safe writes: expected_hash turns clobbering races between
memorysearchsemantic adds an optional TF-IDF hybrid. No model downloads.
- Zero ML in the core: full-text search is SQLite FTS5 with BM25;
The pair: for corpus recall (chunked documents, BM25 retrieval,
original-text injection) see the companion server
mcp-vl-msa-rs. This server holds
the curated agent state; that one holds the queryable corpus.
flowchart LR
A["AI agent<br/>(any MCP client)"]
A -->|"curated state<br/>read / write / sync"| M["mcp-memory-rs<br/><i>the notebook</i>"]
A -->|"corpus recall<br/>index / search / fetch"| V["mcp-vl-msa-rs<br/><i>the library</i>"]
M --- D1[("JSON categories<br/>SQLite FTS5")]
V --- D2[("tantivy BM25<br/>collections")]Install
Prebuilt binary (recommended) — download the archive for your platform from the latest release, extract, and point your MCP client at the binary:
tar xzf mcp-memory-rs-x86_64-unknown-linux-gnu.tar.gz
install -m755 mcp-memory-rs-*/mcp-memory-rs ~/.local/bin/Prebuilt targets (Linux + Android): x8664-unknown-linux-gnu, x8664-unknown-linux-musl, aarch64-unknown-linux-gnu, aarch64-unknown-linux-musl (edge / ARM / Termux), aarch64-linux-android.
macOS: no prebuilt binary is shipped (it would need Apple code-signing). Install from source instead — cargo install compiles it on your Mac in one command, no signing needed:
cargo install --git https://github.com/DioNanos/mcp-memory-rs --locked--locked uses the committed Cargo.lock (reproducible build).
Quick start
cargo build --release
# stdio MCP server, offline mode (default)
./target/release/mcp-memory-rsClaude Code (~/.claude.json) or any MCP client:
Shortened. The full README is on GitHub.
Nothing above is checked by us. What we check is on the safety report.
mcp-memory-rs: common questions
- Is mcp-memory-rs MCP server safe?
- Mostly: it is graded B (70/100). Read the mcp-memory-rs safety report
- Does mcp-memory-rs need an API key?
- Not as far as the registry entry and our scan can tell: no credentials are declared or required.
- Is mcp-memory-rs maintained?
- The last commit was 50 days ago (2026-09-15). The latest release is v0.2.1.
- What can I use instead of mcp-memory-rs?
- Servers from other publishers that do the same job: Basic Memory MCP server, Agent Recall MCP server and agent-device MCP server.
- How does mcp-memory-rs compare with other AI and agents MCP servers?
- safety score 70/100 (higher than 37% of 4,460 AI and agents servers); github stars 2 (more than 65% of 2,711 AI and agents servers). Full comparison.
Alternatives to mcp-memory-rs
Same job from other publishers: the closest match first, then the best rated.
- Basic MemoryLocal-first knowledge management with bi-directional LLM sync via Markdown files.not reviewedWidely usedB
- Agent RecallCorrection-first agent memory. Precision KPI tracks if agents heed warnings. 5 layers, local-only.not reviewedEstablishedA
- agent-deviceLet AI agents inspect, control, and debug real iOS, Android, desktop, and TV appsnot reviewedWidely usedA
- agent-deviceOpen source device layer for AI agents: control mobile, web, TV, and desktop apps over MCPnot reviewedWidely usedA
- HOL GuardLocal-first AI agent security evidence and approval workflows through HOL Guard's stdio MCP server.not reviewedEstablishedA