rlm-claude
Provides an MCP server for Claude Code that persists “infinite memory” across sessions by saving conversation chunks and extracting/saving reusable “insights”. It auto-snapshots before Claude Code’s /compact and supports search (regex, BM25, optional semantic embeddings), retention/archiving, and multi-project organization.
Score Breakdown
⚙ Agent Friendliness
🔒 Security
Likely self-hosted/local MCP process with file-based storage. TLS/auth are not documented; if run remotely, transport security should be handled externally. No mention of encryption-at-rest for stored memory. The project claims safe I/O (atomic writes, path validation, locking) and uses structured local context directories, which is a positive sign for minimizing data corruption risks, but explicit secrecy handling and network exposure controls are not documented in the provided content.
⚡ Reliability
Best When
You run Claude Code locally and want durable, searchable context using MCP tools with local persistence in ~/.claude/rlm/context/.
Avoid When
You cannot ensure local file permissions are safe, or you need strong documented guarantees around encryption-at-rest, auth, and operational recovery.
Use Cases
- • Persistent team/project memory for Claude Code across sessions
- • Searching prior decisions, preferences, and conversation context
- • Auto-saving relevant history before context compaction
- • Archiving/purging old conversation chunks with restore capability
- • Organization and retrieval of information by project/domain and chunk metadata
Not For
- • Security-sensitive data sharing over an untrusted network without transport/auth review
- • Fully managed/hosted memory services (this is self-hosted local storage)
- • Use cases requiring strict enterprise compliance guarantees that aren’t documented
- • High-concurrency workloads needing a hosted database backend instead of local files/vector storage
Interface
Authentication
No explicit authentication mechanism is described in the provided README/manifest. Authentication expectations (e.g., local-only vs network-exposed MCP) are not documented.
Pricing
Software is distributed under MIT; no subscription pricing is indicated.
Agent Metadata
Known Gotchas
- ⚠ Because authentication is not described, if the MCP server is reachable over a network, agents may need additional operational safeguards outside the package.
- ⚠ Retention/archiving/purge behavior affects recall results; agents should be careful to use restore/preview tools appropriately before relying on older context.
- ⚠ Semantic search depends on optional embedding dependencies/providers; results may degrade or differ when semantic deps are missing.
- ⚠ Hooks modify Claude Code configuration; ensure the user’s ~/.claude/settings.json merge/backup approach is appropriate for your environment.
Alternatives
Full Evaluation Report
Comprehensive deep-dive: security analysis, reliability audit, agent experience review, cost modeling, competitive positioning, and improvement roadmap for rlm-claude.
AI-powered analysis · PDF + markdown · Delivered within 30 minutes
Package Brief
Quick verdict, integration guide, cost projections, gotchas with workarounds, and alternatives comparison.
Delivered within 10 minutes
Score Monitoring
Get alerted when this package's AF, security, or reliability scores change significantly. Stay ahead of regressions.
Continuous monitoring
Scores are editorial opinions as of 2026-03-30.