persistent-memory-mcp
Related Servers
Alternatives to persistent-memory-mcp
- AlicenseAqualityAmaintenancePersistent AI memory with SQLite hybrid search (FTS5 + semantic), built-in Qwen3 embedding, and rclone sync across machines.15307 PyPI13Apache 2.0
Related Servers

Particlesofficial
AlicenseAqualityBmaintenanceMemory for AI agents that keeps every claim with the source it came from, the date it was asserted, and a confidence you can re-weight per source, so your agent can say where a fact came from. Updates supersede or retract instead of overwriting, so you can replay what the store believed on any past date and review contradictions as lint findings.16125 PyPI4Apache 2.0- AlicenseNot gradedqualityCmaintenanceLocal-first, source-grounded memory for AI agents, with citations, bitemporal history, review-gated corrections, and MCP tools for search and recall.4Apache 2.0
- AlicenseNot gradedqualityBmaintenanceEnables agents to record facts with declared sources, search or list current and superseded memories, and correct entries while preserving version history and rejecting stale writes.MIT
- AlicenseNot gradedqualityBmaintenanceEnables AI agents to maintain persistent memory across sessions with verifiable source receipts, supporting explicit remember, recall, inspect, correct, and forget operations.52Apache 2.0
- AlicenseNot gradedqualityBmaintenanceProvides AI agents a shared long-term memory layer with evidence-backed, auditable claims, enabling persistent, explainable, and conflict-aware recall across sessions.8MIT
- AlicenseNot gradedqualityBmaintenanceProvides a local-first, source-cited memory layer for AI agents, with MCP tools to search, read, explain sources, and propose/apply memory updates.84 npm13Apache 2.0
TDQS
Scored across 10 tools
Each tool has a sharply distinct role, and the descriptions explicitly route the agent between them (remember vs derive vs learn, search vs read, correct vs withdraw vs plan_withdrawal). The overlap-prone pairs (search/read, explain/plan_withdrawal) are separated by clear read-only vs mutating and metadata vs preview boundaries. No two tools appear to do the same thing.
All names share a consistent memory_ prefix with mostly verb second elements (search, read, remember, correct, explain, derive, learn, withdraw). Minor deviations: memory_notices is a noun rather than a verb, and memory_plan_withdrawal is a verb_noun compound while others are single verbs. Still highly predictable overall.
Ten tools is well within the sweet spot and each one earns its place: three write paths, two read paths, a correction path, a withdrawal path with a safe preview, plus explain and notices for lineage/notification. Nothing feels redundant or padding.
The lifecycle is well covered: create (remember/derive/learn), read (search/read), update (correct), soft-delete (plan_withdrawal/withdraw), and introspection (explain/notices). Minor gaps: no enumeration/list tool to browse artifacts without keywords, and no restore/undo path for a withdrawal (by design, since text is retained, but there is no way to re-serve it).