tdai-memory-mcp
# tdai-memory-mcp → remem-mcp
**This package has been renamed to `remem-mcp`.**
## Migrate
```bash
npx remem-mcp setup
```
Your existing `memory.db` is preserved — same SQLite file, same path (`~/.local/share/remem-mcp/memory.db`).
## What changed
- Package name: `tdai-memory-mcp` → `remem-mcp`
- Env vars: `TDAI_*` → `REMEM_*`
- Everything else stays the same: same tools, same DB, same hooks
## Links
- New repo: [github.com/tinhien11/remem-mcp](https://github.com/tinhien11/remem-mcp)
- npm: [npmjs.com/package/remem-mcp](https://www.npmjs.com/package/remem-mcp)
TDQS
Scored across 7 tools
Most tools have clearly distinct purposes: recall for broad context, search for specific facts, capture for saving, resolve for conflicts, forget for deletion, handoff for session transfer, and adr for architecture decisions. The main overlap is between recall and search, but their descriptions clarify the difference (broad versus specific).
Tool names are mostly single-word lowercase verbs (recall, capture, search, resolve, forget), which forms a predictable pattern. However, 'handoff' is a noun/phrasal verb and 'adr' is an acronym, creating minor deviations from the otherwise consistent verb style.
With 7 tools, the set is well-scoped for a memory-management server. Each tool serves a distinct memory lifecycle function without unnecessary bloat or overlap.
The tool surface covers core memory operations: store (capture), retrieve (recall/search), delete (forget), conflict handling (resolve), plus specialized features (handoff, adr). A missing explicit 'update memory' tool is a minor gap, but capture can serve that role implicitly.