genesys-memory
Related Servers
Alternatives to genesys-memory
No user-submitted related servers found.
Related Servers
- FlicenseNot gradedqualityDmaintenanceProvides persistent, causal memory for AI agents with semantic recall, causal tracking, and importance-based forgetting through MCP tools.-
- AlicenseNot gradedqualityDmaintenanceLong-term memory for AI agents over MCP — episodic + semantic memory, a temporal knowledge graph, and a dialectic user model, exposed as 32 tools (recall, remember, context, graph, dreaming, peers). Zero dependencies, runs fully offline; leads the LoCoMo benchmark at ~35x fewer LLM calls.2Apache 2.0
- AlicenseAqualityBmaintenanceA long-horizon memory architecture for AI agents, providing a scalable, graph-based memory with causal typing and an MCP interface.72Apache 2.0

Mandrelofficial
AlicenseNot gradedqualityBmaintenanceEnables AI coding agents to maintain structured, persistent memory as a typed-edge knowledge graph over contexts, decisions, and tasks, with deterministic auto-threading, trust signals, and replayable story recall. It also exposes a token-lean MCP gateway for on-demand tool discovery, helping agents preserve causal project context across sessions.4,741 npm5MIT- FlicenseNot gradedqualityFmaintenanceCognitive memory system for AI agents with 129 MCP tools. Persistent 6-tier hierarchical memory (working→short-term→long-term→semantic), Ebbinghaus forgetting curves, dream consolidation, hybrid retrieval (BM25+RRF), goal tracking, emotional recall, knowledge graphs, and a 26-job consciousness daemon. Works with Claude Code, Cursor, and any MCP client.1-

kairnofficial
AlicenseNot gradedqualityBmaintenanceProvides AI assistants with a persistent knowledge graph and experience memory, featuring context-aware routing, progressive disclosure, decay-based forgetting, and automatic promotion of important knowledge. It offers 22 MCP tools for storing, recalling, connecting, and querying knowledge, experiences, preferences, and ideas.13MIT
TDQS
Scored across 13 tools
Each tool targets a distinct operation: store, amend, recall, filtered search, graph traversal, explanation, pinning, unpinning, deletion, stats, preferences, and visibility promotion. memory_recall and memory_search are clearly differentiated as hybrid retrieval versus structured filtering/enumeration.
The memory_* prefix is used consistently for several core operations, but other tools switch to verb_memory forms (pin_memory, delete_memory), noun-like names (memory_stats), or unrelated forms (list_core_memories, set_core_preferences, promote_to_org). The naming is readable but not a uniform verb_noun pattern.
Thirteen tools is well within the ideal range for a memory graph server. Each tool covers a meaningful lifecycle or administrative function without unnecessary redundancy.
The tool set covers the full memory lifecycle: create, read via multiple retrieval modes, amend/supersede, pin/unpin, delete, and administrative operations like stats and preferences. Graph traversal and explanation tools add strong domain coverage with no obvious dead ends.