Skip to main content
Glama
Astrix-Labs

genesys-memory

by Astrix-Labs
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

Related Servers

Alternatives to genesys-memory

No user-submitted related servers found.

    Related Servers

    • Logica Mind

      Rovemark
      A
      license
      Not graded
      quality
      D
      maintenance
      Long-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.
      2
      Apache 2.0

    • Echo Memory

      echo-mem
      A
      license
      A
      quality
      B
      maintenance
      A long-horizon memory architecture for AI agents, providing a scalable, graph-based memory with causal typing and an MCP interface.
      4
      2
      Business Source 1.1

    • emms-mcp

      supermaxlol
      F
      license
      Not graded
      quality
      F
      maintenance
      Cognitive 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.
      -
    • kairn by primeline-ai

      kairnofficial

      primeline-ai
      A
      license
      Not graded
      quality
      A
      maintenance
      Provides 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.
      13
      MIT
    Deploy Server
    One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

    TDQS

    B3.4/5.0

    Scored across 13 tools

    Disambiguation5/5

    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.

    Naming Consistency3/5

    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.

    Tool Count5/5

    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.

    Completeness5/5

    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.

    Maintenance

    ActivityMaintained
    ResponsivenessNo issues

    Resources