Skip to main content
Glama
LamantinAI

kaeru memory

by LamantinAI
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Rust
Hybrid

Related Servers

Alternatives to kaeru memory

No user-submitted related servers found.

    Related Servers

    • agent-memory-os

      yamantaka520
      A
      license
      A
      quality
      A
      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
      6
      Apache 2.0

    • kepta

      DamianTodorovic
      F
      license
      Not graded
      quality
      A
      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.
      2
      -

    • alaya

      SecurityRonin
      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.
      17
      MIT

    • nMEMORY

      menot-you
      A
      license
      A
      quality
      A
      maintenance
      Hermetic memory for AI agents — one Rust binary, one SQLite file, zero network. Recall returns evidence with provenance or abstains: no code path for making things up.
      22
      9
      AGPL 3.0
    Deploy Server
    Context All Your Agents Can ShareAgents share what they learn, hand off work, and hold it when you switch models. Start with 5 GB free.fulcradynamics.comAd

    TDQS

    B3.3/5.0

    Scored across 71 tools

    Disambiguation4/5

    There is heavy thematic overlap in the read family (at vs recall vs search vs tagged; drill vs neighbours vs between; path vs chain vs why) and in the write/lifecycle family (jot vs episode; settle vs synthesise; link vs link_cloud; reflect vs lint), but the descriptions go to unusual lengths to draw explicit boundaries ('drill follows only derived_from and part_of; neighbours follows all twelve'). An agent can tell them apart with care, though the sheer number of near-parallel verbs invites occasional misselection.

    Naming Consistency3/5

    Casing and separators are consistent (all lowercase snake_case), but predicate style is mixed: bare imperative verbs (link, settle, pin, search), verb_noun compounds (set_status, close_review, merge_initiative, cloud_recall), and bare nouns (board, slots, ideas, outcomes, history, config). No camelCase chaos, but no single predictable convention either.

    Tool Count2/5

    71 tools is far beyond any comfortable surface, and the rubric flags 25+ as heavy and 50+ as extreme. The domain (bi-temporal graph, tiers, layers, chains, roles, reviews, initiatives, multi-cloud sync) genuinely justifies more than a typical server, so it is not a pure mismatch, but the count is still excessive for reliable tool selection.

    Completeness5/5

    Coverage is remarkably exhaustive for a knowledge substrate: capture (jot/episode/cite/claim/task/evidence), layered read (at/recall/search/tagged/drill/neighbours/between/path/trace/why/history/surface), graph editing (link/unlink/reweight/chain/rechain), lifecycle (settle/unsettle/supersede/revise/synthesise/forget), task board, reviews/verdicts, roles, initiative management, cloud sync, and maintenance (reflect/lint/hygiene) plus export/import. Almost no dead ends in the domain flow.

    Maintenance

    ActivityActive
    ResponsivenessWithin a week

    Resources