RememberMe
Related Servers
Alternatives to RememberMe
No user-submitted related servers found.
Related Servers
- FlicenseNot gradedqualityAmaintenanceEnables Claude Code to maintain cross-session memory by adding, searching, updating, and deleting stored information through MCP tools, backed by self-hosted Qdrant and optional Neo4j knowledge graphs with Ollama or Anthropic as the LLM.-
- FlicenseNot gradedqualityDmaintenanceProvides persistent semantic memory for Claude Code via local embeddings and six MCP tools, enabling context storage and retrieval across sessions without cloud dependencies.-
- FlicenseNot gradedqualityAmaintenanceEnables Claude Code to store, search, update, and delete persistent memories across sessions, backed by self-hosted Qdrant vector storage, an optional Neo4j knowledge graph, and Ollama embeddings, with Anthropic or Ollama as the main LLM. Exposes 11 MCP tools plus session hooks and a CLAUDE.md guide so context is injected at startup and saved automatically at session end.-
- FlicenseNot gradedqualityAmaintenanceEnables Claude Code to maintain persistent cross-session memory backed by self-hosted Qdrant, Neo4j, and Ollama, including semantic search, memory CRUD, and knowledge-graph entity exploration. It supports both Anthropic/Claude and fully local Ollama LLM configurations through MCP tools and session hooks.-
- FlicenseNot gradedqualityAmaintenanceEnables Claude Code to maintain cross-session memory using self-hosted Qdrant vector storage, optional Neo4j knowledge graphs, and Ollama embeddings, with Anthropic or Ollama as the main LLM. It exposes MCP tools for adding, searching, updating, deleting, and graphing memories, plus hooks for automatic context injection and session summarization.-
- FlicenseNot gradedqualityAmaintenanceEnables Claude Code to persistently store, search, update, and delete memories backed by self-hosted Qdrant, Neo4j, and Ollama, using Anthropic or a fully local LLM. Exposes 11 MCP tools plus session hooks that automatically inject relevant context on startup and save session summaries on exit.-
TDQS
Scored across 6 tools
Each tool has a clearly distinct purpose: add, delete individual, bulk delete, get by ID, search, and update. There is no overlap or confusion between them.
All tool names follow a consistent verb_noun pattern in snake_case, e.g., add_memory, delete_all_memories, delete_memory, get_memory, search_memories, update_memory. The pattern is predictable and clear.
With 6 tools, the server is well-scoped for memory management. Each tool earns its place, covering essential operations without unnecessary bloat or sparseness.
The tool surface covers all fundamental memory operations: create, read, update, delete (individual and bulk), and search. There are no obvious gaps for typical memory management tasks.