Ragionex Memory MCP
OfficialRelated Servers
Alternatives to Ragionex Memory MCP
No user-submitted related servers found.
Related Servers
- AlicenseNot gradedqualityDmaintenanceProvides intelligent, persistent memory for AI assistants with semantic search, natural language queries, and OAuth-based team collaboration, enabling context-aware conversations across multiple clients.10Apache 2.0
- FlicenseAqualityNot gradedmaintenanceProvides long-term memory storage for AI assistants with semantic search, enabling persistent storage of preferences, decisions, and context with relationship tracking between memories.19-
- AlicenseNot gradedqualityDmaintenanceGives AI assistants persistent, queryable project memory for decisions, patterns, and rules, reducing the need to re-explain context in every prompt.11Apache 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 gradedqualityDmaintenanceProvides persistent memory and semantic file discovery for AI coding agents, enabling them to remember changes and find relevant files across sessions.5MIT
- AlicenseCqualityCmaintenancePersistent semantic memory for MCP-compatible agents, enabling them to remember and recall text, audio, and documents across sessions.1055 npmMIT
TDQS
Scored across 11 tools
Each tool targets a distinct operation and the descriptions explicitly draw the boundaries that would otherwise be ambiguous: recall (topical search) vs list_memories (browse/paginate) vs view_memory (read by ID), status (record processing) vs connection (vault/permission/pending-save state), and versions (history) vs list_trash (deleted items). Cross-references like 'for a locally queued operation ID, use ragionex_memory_connection' actively steer the agent to the right tool.
Most names follow a predictable ragionex_verb_noun pattern (view_memory, save_memory, recall_memory, update_memory, delete_memory, list_trash, restore_memory), giving a readable surface. Minor deviations exist: memory_status, memory_connection and memory_versions are noun-first rather than verb-first, and the memory/memories pluralization is inconsistent (view_memory vs list_memories).
Eleven tools sit comfortably in the well-scoped range, and every one maps to a real lifecycle step (create, search, browse, read, update, trash, restore, version history, status, connection context). Nothing appears redundant or like padding.
The memory record lifecycle is essentially fully covered: create, multi-path read, update with revision control, soft delete, trash listing, version history and restore, plus status and vault/permission context. Gaps are minor and partly deliberate (permanent deletion only in the dashboard, no vault creation/administration, no tag or metadata management), which agents can work around.