Skip to main content
Glama

Related Servers

Alternatives to kaeru memory

No user-submitted related servers found.

    Related Servers

    • F
      license
      Not graded
      quality
      B
      maintenance
      Gives AI agents their own long-term memory on the local machine: a graph of corrections, decisions, and behavioral experience that persists across sessions and is recalled by association rather than keyword. Runs fully offline in Rust, with background sleep consolidation, explanation of search results, and optional encryption — no cloud or LLM required.
      2
      -
    • F
      license
      Not graded
      quality
      B
      maintenance
      Long-term memory for AI agents: a local-first knowledge graph (entities, observations, relations) with hybrid semantic + full-text search, sessions, tasks/bugs with status, and a live dashboard with a physics-based memory map. Self-hosted, installs with one command, no Docker required. Works with Claude Code, Cursor, VS Code, and any MCP or REST client.
      3
      -
    • A
      license
      A
      quality
      B
      maintenance
      Local-first memory engine for AI-agent teams: private/team/project ACL, associative recall, and federated sync across nodes. One SQLite file, no LLM required.
      12
      9
      Apache 2.0
    • A
      license
      Not graded
      quality
      B
      maintenance
      Local memory for AI agents in one SQLite file on your own machine. Facts carry a validity window and a confidence score, so an outdated one is superseded and downweighted rather than deleted, and retrieval fuses BM25, vector similarity and a knowledge graph.
      4
      Business Source 1.1
    • A
      license
      Not graded
      quality
      D
      maintenance
      A local memory engine for AI agents. Stores conversation episodes, consolidates knowledge through a neuroscience-inspired lifecycle, and builds a personal knowledge graph — all in a local SQLite database.
      20
      MIT

    TDQS

    C2.7/5.0

    Scored across 35 tools

    Disambiguation3/5

    Many tools target related memory operations, and several boundaries are fuzzy: claim vs verdict both can save verdict evidence, note/reference/synthesise all create records, and context/read/search overlap in retrieval. Detailed descriptions mitigate much of the confusion, but an agent still has to reason carefully to choose the right tool.

    Naming Consistency3/5

    All names are snake_case, but conventions are mixed: some are single verbs or nouns (task, claim, note, read), some are verb_noun (task_update, link_cloud), and others are noun_verb or noun_noun (initiative_manage, cloud_recall, board_config). The set is readable but does not follow a predictable pattern.

    Tool Count2/5

    With 35 tools, the surface is heavy for a memory/knowledge server and includes many niche maintenance, sharing, and cloud-sync operations. While the domain is broad, the count exceeds a well-scoped set and likely burdens tool selection.

    Completeness4/5

    The surface covers an extensive memory lifecycle: creation, revision, replacement, relations, review, trails, lifecycle tiers, retention, audit history, search/read/context, initiatives, export, and cloud sharing. Minor gaps remain, such as no import counterpart to export and no obvious initiative creation action beyond management.

    Maintenance

    ActivityNo data
    ResponsivenessOutdated data