pūrmemo
OfficialRelated Servers
Alternatives to pūrmemo
No user-submitted related servers found.
Related Servers
- AlicenseNot gradedqualityAmaintenanceEnables Claude and other AI agents to store and retrieve persistent cross-session memories, preserving decisions, patterns, and knowledge across restarts and context limits.24 npmMIT
- AlicenseNot gradedqualityAmaintenanceProvides persistent cross-session memory for Claude and other AI agents, letting users store decisions, patterns, and knowledge once and retrieve them automatically across future conversations while surviving context limits and session restarts.24 npmMIT

SAE4U Memoryofficial
AlicenseAqualityCmaintenanceProvides persistent memory for Claude with hierarchical categorization, cross-corpus recall, session journals, and customizable persona, enabling memory continuity across sessions.7MIT- -licenseNot gradedqualityDmaintenanceProvides persistent memory for AI assistants like Claude, storing and retrieving information across conversations using a local SQLite database.-
- AlicenseNot gradedqualityDmaintenanceProvides persistent cross-session memory for Claude Code, enabling it to remember user preferences, decisions, and project context across new sessions.Apache 2.0
- FlicenseNot gradedqualityCmaintenanceEnables AI tools like Claude and Cursor to share persistent memory across sessions.5-
TDQS
Scored across 29 tools
Descriptions are detailed and give WHEN TO USE guidance, but the set contains several overlapping clusters: a five-tool snapshot family (get_snapshot, snapshot, snapshot_sources, save_snapshot, accept_snapshot) and a save family (save_conversation, save_artifact, save_snapshot, save_test_result, commit). An agent must read carefully to pick the right one, and 'snapshot' vs 'get_snapshot' are easy to confuse.
Mostly snake_case, but the verb conventions are mixed: most tools use verb_noun (get_snapshot, save_conversation, list_workflows), while several are bare nouns/verbs (snapshot, commit, what_changed). The inconsistency within the snapshot family itself weakens predictability.
29 tools is well above the 3-15 well-scoped range and on the high end even for the broad memory domain. Several families could be consolidated (e.g. the five snapshot-related tools), suggesting bloat rather than each tool clearly earning its place.
The surface covers a lot: conversation/artifact capture, snapshots, commitments, recall with filters, timeline, clusters, user context, workflows, public sharing, and test/task tracking. Minor gaps remain (no explicit update/delete for individual memories) but core workflows are covered.