PseudoLife-MCP
OfficialRelated Servers
Alternatives to PseudoLife-MCP
No user-submitted related servers found.
Related Servers
- AlicenseNot gradedqualityBmaintenanceProvides persistent long-term memory for Claude Code by enabling semantic save, search, and context retrieval across sessions.1MIT
- AlicenseNot gradedqualityAmaintenanceEnables Claude Code to remember facts, decisions, and lessons across sessions through semantic and keyword memory search, and to track user corrections as behavioral patterns that evolve over time. It also exposes tools for loading identity and frameworks, recording signals, and triggering reflection cycles so the assistant's judgment improves with use.6 npmMIT
- AlicenseNot gradedqualityAmaintenanceEnables Claude Code to retain persistent identity, cross-session memory with semantic search, and behavioral pattern tracking across sessions. It lets the agent save and recall facts, decisions, and lessons locally, record interaction signals, run reflection cycles, and evolve frameworks based on accumulated evidence.6 npmMIT
- 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.9 npm1MIT
- AlicenseNot gradedqualityAmaintenanceGives Claude Code a persistent identity and cross-session memory with semantic search over saved facts, decisions, and journals. It also detects and classifies user corrections into behavioral patterns with lifecycle trends, reflecting periodically to promote or retire working frameworks.6 npmMIT
- AlicenseAqualityDmaintenanceEnables persistent memory for Claude Code sessions by recording observations and building knowledge graphs for cross-session learning and domain knowledge management.11MIT
TDQS
Scored across 38 tools
The set covers many memory concepts, but several tools overlap in purpose: memory_search vs memory_recall vs lesson/world/document searches; memory_store vs fact_set/world_set/set_add; memory_supersede vs fact_set/forget; memory_consolidate vs dream/consolidation_candidates. Detailed descriptions guide selection, but the boundaries require significant domain knowledge.
All names use snake_case and most memory tools share the memory_ prefix; document_ingest/document_search are the main deviation. However, the names are not uniformly verb_noun: many are noun-only (memory_agents, memory_message, memory_stats, memory_graph), so the pattern is mostly consistent but not perfectly predictable.
38 tools is well over the 3-15 sweet spot; even with memory_toolset tiers, the full surface is heavy and forces agents to navigate many related operations. The breadth is justified by the feature-rich memory model, but as presented it is too large.
Core memory lifecycle is comprehensively covered: store/search/get/reinforce/supersede/forget, canonical facts, world facts, lessons, graph, episodes, agents/messages, and dream admin. Minor gaps remain around document lifecycle (only ingest/search exposed; no clear document delete/list) and some admin operations, but no major workflow dead ends.