MCP Memory Service
Related Servers
Alternatives to MCP Memory Service
No user-submitted related servers found.
Related Servers
- AlicenseNot gradedqualityDmaintenanceProvides Claude AI with persistent, searchable memory management across sessions using SQL database, semantic analysis with multi-provider LLM support (Anthropic/Ollama), vector search via ChromaDB, and graph-based knowledge relationships through Neo4j integration.1MIT
- AlicenseNot gradedqualityBmaintenanceProvides persistent long-term memory for Claude Code by enabling semantic save, search, and context retrieval across sessions.1MIT
- FlicenseAqualityDmaintenanceSupercharges Claude Desktop with persistent semantic memory, sandboxed file I/O, live web search, and local emotional intelligence using a local ChromaDB and Hugging Face model.6-
- AlicenseNot gradedqualityDmaintenanceProvides local-first, cross-session memory for Claude Code, enabling semantic search across past sessions to retrieve procedures, decisions, or answers without exposing secrets.Apache 2.0
- AlicenseNot gradedqualityFmaintenanceProvides Claude with long-term memory by indexing conversation history, enabling semantic search, decision tracking, and cross-project search.18 npm29MIT
- AlicenseNot gradedqualityDmaintenanceProvides persistent, searchable memory for Claude Code using local SQLite, semantic embeddings, and full-text search, enabling Claude to recall and retrieve context across sessions and projects without external services.23 npm4MIT
TDQS
Scored across 28 tools
Core memory CRUD and search are distinguishable, but several families overlap: store/extract variants (memory_store, memory_store_session, memory_ingest, memory_harvest, commit_session_legacy, memory_distill) and retrieval variants (memory_search, memory_list, memory_explore, memory_detail, memory_graph) require careful description reading. Multi-action tools such as memory_quality, memory_consolidate, and memory_graph bundle unrelated operations, raising misselection risk.
Almost all names use snake_case with readable domain prefixes (memory_*, mistake_note_*), giving a mostly predictable pattern. Minor inconsistency comes from bare get_* tools (get_quarantined_memories, get_bootstrap_profile, get_onboarding_guide) and commit_session_legacy mixed into the memory_* action pattern.
28 tools is heavy for a memory service and exceeds the typical well-scoped 3-15 range. Several tools are multi-action containers that add capability but also cognitive load, making the surface feel overgrown rather than tightly scoped.
The surface covers the full memory lifecycle: store, retrieve, list, update, delete, cleanup, consolidation, import, session capture, quality, graph exploration, conflicts, quarantine, and mistake notes. Retrieval by hash is available through memory_search, and no major CRUD or lifecycle gaps are apparent.