pūrmemo
OfficialRelated Servers
Alternatives to pūrmemo
No user-submitted related servers found.
Related Servers
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-
- AlicenseNot gradedqualityDmaintenanceProvides long-term memory capabilities for Claude through persistent storage and full-text search of context across conversations. Enables storing, searching, and managing memories organized by categories like facts, preferences, projects, and goals.8 npm1MIT

BaseGrid MCP Serverofficial
FlicenseNot gradedqualityDmaintenanceGives Claude Desktop, Cursor, Cline, and other MCP-compatible AI tools persistent memory, enabling them to store and recall information seamlessly across sessions.9 npm1-
TDQS
Scored across 29 tools
Each tool has a clearly distinct purpose, from saving conversations to recalling memories, managing tasks, handling errors, and sharing public content. Even similar-sounding tools like get_investigations vs get_acknowledged_errors are precisely scoped (investigation results vs errors to investigate). The snapshot workflow tools (snapshot, snapshot_sources, save_snapshot, accept_snapshot) follow a clear pipeline with distinct roles.
All tools use consistent snake_case with a verb_noun pattern (e.g., get_next_task, save_artifact, recall_public). Even standalone verbs like 'snapshot' and 'commit' fit the imperative style. There are no mixed conventions or unpredictable patterns.
29 tools is above the typical well-scoped range and feels heavy, but it's justified by the breadth of the server's domain (memory, tasks, snapshots, workflows, errors, public sharing). Still, the sheer number may overwhelm agents and increase misselection risk.
The tool surface covers core CRUD-like operations for memories (save, recall, get details, share), artifacts (save, list), snapshots (generate, save, accept, get), tasks (get next, complete), and errors (fetch, save investigation). Minor gaps exist like no explicit delete for memories or artifacts, but these are likely intentional (insert-only design) and agents can work around them.