mcp-hyperspace-memory
OfficialRelated Servers
Alternatives to mcp-hyperspace-memory
No user-submitted related servers found.
Related Servers
- AlicenseAqualityDmaintenanceEnables AI agents with persistent semantic memory, including semantic recall, knowledge graphs, and instant domain expertise via pre-built Intelligence Packs.1052 npmMIT

Memsolus MCP Serverofficial
AlicenseAqualityDmaintenanceProvides persistent long-term memory for AI agents through semantic search and automated knowledge graph extraction. It enables agents to store, recall, and reason over facts, preferences, and relationships across multiple conversations and sessions.146 npmMIT- FlicenseNot gradedqualityDmaintenanceProvides AI agents with persistent, searchable memory that survives across conversations using semantic search, temporal versioning, and smart organization. Enables long-term context retention and cross-session continuity for AI assistants.14-
- FlicenseBqualityDmaintenanceEnables persistent memory for AI systems by providing tools for episodic, semantic, and procedural data storage through a vector-and-graph-enhanced database. It allows models to maintain long-term continuity using similarity search, thematic clustering, and identity tracking.241-
- AlicenseNot gradedqualityAmaintenanceEnables AI agents to persistently store and retrieve memories across sessions, workspaces, and context limits so prior decisions, patterns, and knowledge remain available in future conversations.17 npmMIT
- AlicenseNot gradedqualityDmaintenanceEnables AI agents to store, search, and recall semantic memories with three memory types (semantic, episodic, procedural) and auto-consolidation, compounding intelligence over time.21 npmMIT
TDQS
Scored across 16 tools
Core memory CRUD tools are clearly distinct, but memory_query_planner is an exact alias of hyperspace_query_planner, creating direct confusion. Several advanced operations also overlap in concept (memory_link/memory_link_batch/memory_induce_edges, and memory_verify_claim/memory_verify_generation), though their descriptions help differentiate them.
Most tools follow a predictable memory_verb_noun snake_case pattern, such as memory_remember, memory_recall, and memory_forget. The main deviations are hyperspace_query_planner and its duplicate alias memory_query_planner, which break the memory_ prefix convention.
At 16 tools, the surface is slightly above the ideal 3-15 range but still reasonable for a feature-rich memory system with graph, hierarchy, consolidation, and verification capabilities. The only clear redundancy is the duplicated query planner alias.
The server covers the core memory lifecycle well: create, recall, update, delete, list sessions, stats, hierarchy exploration, consolidation, graph linking, and verification. Minor gaps remain around bulk memory operations and explicit session lifecycle management, but no major dead ends are obvious.