memora
Related Servers
Alternatives to memora
No user-submitted related servers found.
Related Servers
- AlicenseNot gradedqualityCmaintenanceProvides persistent memory for AI tools by building a local knowledge graph from conversations, enabling cross-session recall and context awareness without cloud dependencies.9MIT

Mnemo MCPofficial
AlicenseNot gradedqualityCmaintenancePersistent AI memory server with hybrid search and embedded sync. Enables AI agents to store, retrieve, and manage information across sessions with temporal knowledge graph support.MIT- FlicenseNot gradedqualityCmaintenanceProvides AI agents with persistent, local cross-session shared memory by combining vector semantic retrieval with knowledge graph relationships, and supports short/long-term memory management and local backups.-
- AlicenseNot gradedqualityDmaintenanceEnables AI agents to maintain persistent, local memory with retrieval-augmented search, knowledge graphs, and context surfacing, without any cloud dependencies.1,027 npmMIT
- AlicenseNot gradedqualityDmaintenancePersistent memory and knowledge graph server that fuses keyword, vector, and graph search into a single query, enabling AI assistants to recall typed entities and relationships across sessions.MIT
- AlicenseNot gradedqualityCmaintenanceProvides persistent, semantic memory storage for LLMs across sessions using vector embeddings and FAISS search. Features bio-inspired memory consolidation, intelligent forgetting, and semantic retrieval without API costs.MIT
TDQS
Scored across 44 tools
Most tools have clearly distinct purposes: specialized create variants for issues, todos, sections, and documents, plus separate search modes. A few clusters overlap (memory_list vs memory_list_compact vs semantic/hybrid search; memory_create vs absorb vs create_batch), but the descriptions clarify their intents well enough.
The memory_ prefix and snake_case are used consistently throughout, and mutations mostly follow verb_noun (create_issue, delete_document, rebuild_crossrefs). Some informational tools use bare nouns (memory_stats, memory_insights, memory_clusters) and a few deprecated/legacy names (memory_list_compact, top_k alias) break the pattern slightly, but the overall scheme remains predictable.
44 tools is well above the 25+ threshold, making the selection surface very heavy for an agent even though the domain is broad. Many maintenance, admin, and analytics tools could be consolidated or hidden behind fewer entry points.
The tool surface is remarkably complete: full CRUD for memories and documents, specialized issue/todo types, multiple search modes, deduplication, merging, supersession detection, tags, hierarchy, stats, import/export, image handling, and events. Minor gaps like the lack of dedicated todo/issue update tools are covered by generic memory_update, so there are no real dead ends.