nMEMORY
Related Servers
Alternatives to nMEMORY
No user-submitted related servers found.
Related Servers
- AlicenseBqualityAmaintenanceLocal long-term memory for AI assistants, written in Rust: hybrid search with reranking over a local Qdrant, a fact store that resolves contradictions, and a hash-chained audit log. Runs fully offline, no API keys.4410Apache 2.0
- FlicenseNot gradedqualityAmaintenanceLocal-first memory for AI agents with evidence-backed recall, deterministic trust verdicts, self-inspection, and a tamper-evident audit history.3-
- FlicenseCqualityAmaintenanceMemory for LLM agents: a local graph where the agent keeps decisions, tasks, hypotheses and reasoning between sessions, and gets a summary of what is open and overdue on every return to a project. Works with Claude Code, Codex, Cursor and opencode. Single Rust binary, no embedding model or LLM calls. Source-available (BSL 1.1), commercial use permitted.3553-
- AlicenseAqualityCmaintenanceEmbedded, local-first agent memory: facts extracted into a per-namespace SQLite file (vec0 + FTS5) with hybrid retrieval and point-in-time (time-travel) queries. ADD-only history over stdio — no server process, no cloud dependency.743Apache 2.0
- AlicenseAqualityDmaintenanceLocal-first memory for AI agents. On-device hybrid retrieval over a single SQLite file.164Apache 2.0
- AlicenseAqualityCmaintenanceLocal-first, source-traceable memory for AI agents — no LLM at ingest, $0 per message, zero data egress. Gives Claude Code, Cursor, and any MCP client one shared persistent memory with semantic recall, belief revision, selective forgetting, and a provenance guard that blocks acting on stale or unconfirmed memories.2314MIT
TDQS
Scored across 22 tools
Tools have distinct purposes, but memory_ingest and memory_classify both can persist classification sidecars, causing minor ambiguity. Overall, descriptions are thorough and roles are clear.
All tools use 'memory_' prefix with snake_case. While not strictly verb_noun (e.g., outcome, vector, visual are nouns/adjectives), the pattern is consistent and predictable.
22 tools cover a comprehensive memory management lifecycle including CRUD, import/export, session management, relations, and advisory features. Each tool earns its place without bloat.
Covers most operations but lacks a direct content-update tool; modification requires forget+re-ingest. Metadata updates exist via classify, pin, etc. Minor gap for full CRUD parity.