mcp-ariel-memory
Related Servers
Alternatives to mcp-ariel-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.1029 npmMIT

RushDB MCP Serverofficial
AlicenseAqualityAmaintenanceEnables AI agents to gain persistent, structured memory that is semantically searchable and graph-traversable, allowing them to store and query records and relationships without managing embeddings or schemas.4340 npmApache 2.0- 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-
- AlicenseNot gradedqualityDmaintenanceEnables AI agents to store, recall, update, delete, and analyze persistent memories with semantic search, decay, and anomaly retrieval across hosted, self-hosted, or fully local storage modes.31 npm22MIT
- AlicenseCqualityAmaintenanceProvides AI assistants with persistent memory and code intelligence across all tools and conversations. Features semantic search, knowledge graphs, decision tracking, and impact analysis with 60+ tools for universal context preservation.362,301 npm44MIT
- AlicenseNot gradedqualityAmaintenanceEnables AI agents to capture, classify, synthesize, and retrieve persistent knowledge through MCP and REST APIs, so multiple agents can share memory and improve across sessions. It provides full-text, semantic, and hybrid search with token-optimized context retrieval from sources like Obsidian, code, transcripts, and terminal sessions.14 npmMIT
TDQS
Scored across 7 tools
The metaphorical names (dream=search, think=routing/store, evolve=personality, forget=delete) obscure the underlying actions, so an agent wanting to store or retrieve could plausibly misselect between think and dream. Descriptions disambiguate reasonably well once read, but the boundaries are not self-evident from the names.
Most tools are single imperative verbs (evolve, think, dream, forget, project, wake_up), which is fairly consistent, but memory_hook breaks the pattern with a noun_noun form and several names are metaphorical rather than descriptive. It reads cleanly but the convention is not uniform.
Seven tools is well-scoped for a memory server covering store, search, forget, lifecycle, session lift, projects, and evolution. Each tool has a distinct role and none feels redundant.
The surface covers a full memory lifecycle: ingest (think), retrieval (dream, wake_up), deletion/undo (forget), lifecycle events (memory_hook), project context (project), and personality (evolve). Only minor gaps remain, such as no explicit standalone get/recall beyond the search-oriented tools.