PseudoLife-MCP
OfficialRelated Servers
Alternatives to PseudoLife-MCP
No user-submitted related servers found.
Related Servers
- 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.5 npm1MIT
- AlicenseAqualityDmaintenanceEnables persistent memory for Claude Code sessions by recording observations and building knowledge graphs for cross-session learning and domain knowledge management.11MIT
- AlicenseNot gradedqualityCmaintenancePersistent memory management for Claude Code, allowing agents to store and retrieve user preferences, environment notes, and skills across sessions.05MIT
- 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
- AlicenseNot gradedqualityCmaintenanceEnables Claude Code with persistent memory that learns from past sessions, capturing coding episodes and surfacing relevant memories to improve over time.6Apache 2.0
- FlicenseCqualityDmaintenanceProvides long-term memory and lossless context management for Claude Code, enabling automatic context compression, cross-session memory sharing, and semantic search across all history.10-
TDQS
Scored across 35 tools
Every tool targets a distinct store, lifecycle action, or retrieval mode, and the descriptions aggressively cross-reference the right tool for each case (e.g. memory_store points to memory_fact_set for canonical facts; memory_recall falls back to memory_search). Even the many search and consolidation tools are clearly separated by store type or workflow stage.
The memory_ prefix is used almost everywhere and the snake_case naming is predictable, with clear subfamilies like memory_fact_*, memory_world_*, memory_episode_*, and memory_graph_*. The main deviation is that action position varies (memory_search vs memory_fact_get) and the document_* tools break the memory_ prefix, but this is still easy to navigate.
35 tools is above the 25+ threshold and feels heavy even for a broad memory server. Many consolidation, review, and graph-admin tools could be grouped or hidden behind sub-actions, so the surface is larger than an agent likely needs for day-to-day memory work.
The domain is covered remarkably thoroughly: memories, canonical facts, world facts, lessons, episodes, graph relations, consolidation, and documents all have create/read/update/delete or equivalent lifecycle operations. Minor gaps remain, such as no document delete/update and no obvious episode-list tool, but these are workable rather than blocking.