Score breakdown
Popularity is tracked separately. Support, ads, sponsorships, and tips never affect these signals.
Why it matters
Useful for teams building long-running agents that need cross-session memory (Claude Code / Codex / Cursor / OpenCode / Gemini CLI agents that survive restarts), for researchers reproducing or extending the SimpleMem arXiv paper's text/multimodal compression + retrieval claims, for RAG teams exploring semantic-lossless memory compression as an alternative to sliding-window context, for teams that
Who should use it
Who should skip it
Consider aiming-lab/SimpleMem lower priority if you already have a working solution in this category.
About this signal
aiming-lab/SimpleMem is tracked by RepoRadar as a library in the Radar section. First seen 2026-08-10; the source record was last checked on 2026-08-10. The current verdict is 'try now' with a Silver tier and moderate setup difficulty. The standout signals for aiming-lab/SimpleMem are workflow potential (8.9) and open-source/build quality (8.4), while maturity (5.7) trails — that balance shapes where it fits best. This page summarizes the public evidence on the linked source page and states where additional review is still needed.
How this item is evaluated
The aiming-lab/SimpleMem record combines a 7.8/10 composite score with separate popularity (3.7), risk (none), and setup (moderate) signals. See the scoring methodology for the current weights and evidence definitions.
Putting this into practice? Read How to evaluate an AI tool before you adopt it for the checklist behind this score.
Risk explanation
Hosted MCP backend (mcp.simplemem.cloud) is a third-party SaaS; connecting production agents means routing memory queries through the vendor's infrastructure. Review the privacy / data-retention policy and prefer the self-hosted `pip install simplemem` path for regulated data; SOTA claims are author-reported from the arXiv paper; the README's headline numbers (LoCoMo F1=0.613 +47%, Mem-Gallery F1=0.810 +51%) are reproducible from the paper's benchmarks but the hosted MCP server's production quality depends on the underlying vector backend (the recent dense-vector-backend-interface refactor #76 is the active change). Treat the SOTA numbers as research evidence, not as a quality SLA for the hosted endpoint.