| FMRS | 57 / 100 · C | 79 / 100 · B |
|---|
| Reliability | 9 / 20 | 12 / 20 |
|---|
| Security and permissions | 11 / 20 | 16 / 20 |
|---|
| Maintenance | 12 / 20 | 18 / 20 |
|---|
| Documentation | 13 / 20 | 18 / 20 |
|---|
| Setup experience | 12 / 20 | 15 / 20 |
|---|
| Best for | - Coding agents and CLI workflows that need persistent memory across sessions and machines (Claude Code, Codex, Cursor)
- Developers building autonomous agents that need semantic, episodic, and evolving procedural memory
- Teams using LangChain, CrewAI, or OpenClaw who want a ready memory backend
- Apps that need multi-user data isolation under a single API key
- Teams wanting an account-free, folder-based memory that uses their own model provider (Anthropic, OpenAI, or Ollama)
| - Developers auditing NPM dependencies within AI workflows
- Teams performing supply chain security assessments
- Users of Claude Desktop, Cursor, or VS Code
|
|---|
| Not for | - Single-turn chats or scenarios with no need for cross-session state
- Environments requiring a fully local setup with no SDK or CLI installed (local mode still needs pip install mengram-ai and your own model key)
- High-concurrency writes demanding whole-folder crash-atomic transactions (the folder is not a single crash-atomic transaction and external editors do not participate in the lock)
- Self-hosters expecting good extraction from models under 8B parameters or with less than an 8K context window
| - Projects outside the NPM ecosystem (e.g., pure Python/Go)
- Environments without network access to deps.dev, OSV.dev, and the npm registry
- Scenarios requiring maintenance by an official upstream vendor
|
|---|
| Required permissions | - A Mengram API key sent as an Authorization: Bearer header for cloud memory reads and writes
- In cloud mode, conversations are sent to mengram.io for extraction, embedding, and retrieval
- Claude Code hooks can read session history and working state and re-inject context before and after compaction
- `mengram import claude-code` reads local Claude Code session history (the README states secrets are redacted on your machine before upload)
- The policy gate looks up learned workflows before workflow-shaped Bash commands and can be pointed at a local memory folder via MENGRAM_MEMORY_DIR
| - Network access to the NPM registry and external services (deps.dev, OSV.dev, OpenSSF, npms.io, GitHub)
- Read access to workspace lockfiles (pnpm-lock.yaml, package-lock., yarn.lock) for cache invalidation
|
|---|
| Risks and side effects | - Cloud mode uploads conversations and file content to a third-party service, which may include sensitive data; local mode avoids this but needs your own model key
- Auto-save and auto-recall hooks read and write memory in the background, which can introduce unwanted context
- Incorrect memories get re-recalled and injected into system prompts, with a persistent effect
- Procedures evolve automatically and the policy gate can prompt before command execution, so misconfiguration may cause false alarms
- In folder mode concurrent external edits are not lock-protected and can be overwritten; local search matches words and does not use embeddings or translation
| - Third-party READMEs and changelogs are untrusted external content; they are wrapped in tags with _meta flags but should still be handled cautiously
- Depends on availability and accuracy of external services
- Batch requests are capped at 25 packages to prevent registry enumeration; larger sets require batching
- Third-party open source project, not officially maintained by NPM or Anthropic
|
|---|
| Supported clients | Claude Desktop, Cursor, Codex, Windsurf, Cline, Claude Code, OpenClaw, LangChain, CrewAI | Claude Desktop, VS Code, Cursor |
|---|
| Tools | 0 | 19 |
|---|