MemoVault
Related Servers
Alternatives to MemoVault
No user-submitted related servers found.
Related Servers
- AlicenseAqualityCmaintenanceA full-featured long-term memory system for Claude Code that persistently stores and retrieves preferences, decisions, and project context across sessions using hybrid search and LLM-powered extraction.147 npmMIT
- AlicenseNot gradedqualityFmaintenanceA persistent memory server for Claude Code that captures session context and tool outputs to inject relevant history into future sessions. It enables long-term recall through semantic search and automatic context management, allowing for more consistent and context-aware coding interactions.10 npm253ISC
- AlicenseAqualityDmaintenanceA persistent semantic memory system for Claude Code that provides a structured, versioned document store with semantic search and graph visualization. It acts as a memoization layer to store and retrieve research, design decisions, and codebase insights across different work sessions.10Apache 2.0
- AlicenseNot gradedqualityBmaintenancePersistent memory for AI coding agents that stores and recalls preferences, decisions, and conventions via semantic similarity, with zero cloud dependencies and plug-and-play MCP integration for Claude Code.Apache 2.0
- AlicenseAqualityDmaintenanceEnables AI coding assistants to store and retrieve persistent long-term memory across sessions, remembering project preferences, build steps, and architecture decisions.4MIT
- AlicenseBqualityDmaintenanceThe Cursor10x Memory System creates a persistent memory layer for AI assistants (specifically Claude), enabling them to retain and recall short-term, long-term and episodic memory on autonomously.1811 npm80MIT
TDQS
Scored across 8 tools
Each tool has a clearly distinct purpose with no overlap. For example, add_memory stores new information, get_memory retrieves a specific memory by ID, search_memories finds relevant memories by query, and chat_with_memory uses memories to enhance responses. The descriptions reinforce these distinct roles, making tool selection unambiguous.
All tool names follow a consistent verb_noun pattern with snake_case (e.g., add_memory, delete_memory, list_memories). The naming is predictable and readable throughout the set, with no deviations in style or convention.
With 8 tools, the count is well-scoped for a memory management server. It covers core operations like CRUD (add, get, delete, list), search, chat integration, status checks, and clearing, with each tool earning its place without feeling excessive or insufficient.
The tool set provides complete coverage for memory management, including CRUD operations (add_memory, get_memory, delete_memory, list_memories), search capabilities (search_memories), integration (chat_with_memory), system management (clear_memories, memory_status). There are no obvious gaps, and agents can handle full memory lifecycles without dead ends.