Skip to main content
Glama
donggyun112

keymem

by donggyun112
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

Related Servers

Alternatives to keymem

No user-submitted related servers found.

    Related Servers

    • mnemos

      vishalbanwari26
      A
      license
      A
      quality
      B
      maintenance
      Persistent memory for LLM agents — episodic/semantic/procedural memory, auditable forgetting, and a benchmark proving it actually recalls things days later.
      5
      MIT

    • agent-knowledge

      yucx-go
      A
      license
      A
      quality
      C
      maintenance
      Long-term memory for AI agents. Compiles conversations into a structured knowledge base with Claim/Evidence model, source provenance, append-only timeline, and contradiction detection. Multi-path retrieval (Exact + BM25 + Graph + weighted RRF + reranker) — 96.6% R@5 on LongMemEval-S, zero vector dependencies.
      8
      3
      MIT

    • 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

    • MahoRAGa

      Aadi775
      A
      license
      B
      quality
      D
      maintenance
      Persistent, graph-powered memory for AI agents that provides long-term semantic recall using a local Kuzu graph database.
      55
      3
      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

    A4.1/5.0

    Scored across 10 tools

    Disambiguation5/5

    Each tool maps to a distinct operation: retrieval (browse_keys/read_key/read_memory/recall), writing (remember/remember_batch), updating (correct/confirm_memory), and deleting/decaying (forget/dismiss). The only close pair, remember vs remember_batch, is clearly separated by single vs multiple facts. Correct, forget, and dismiss are carefully differentiated with usage guidance.

    Naming Consistency4/5

    The toolkit uses imperative lowercase verbs throughout, with many verb_noun compounds like read_key, read_memory, browse_keys, and confirm_memory. However, several tools are standalone verbs without objects (recall, correct, dismiss, forget, remember), creating a slight inconsistency in naming shape.

    Tool Count5/5

    Ten tools is a well-scoped size for a memory server covering search, browsing, reading, writing, updating, and forgetting. Each tool has a clear role, and there is no redundant surface area. The batch variant of remember is justified by efficiency and does not feel like filler.

    Completeness4/5

    The core lifecycle is covered: recall/read for retrieval, remember/remember_batch for creation, correct/confirm_memory for updates, and forget for deletion, plus dismiss for link-level correction. Minor gaps exist around namespace enumeration and explicit alias/history management, but agents can complete normal workflows without dead ends.

    Maintenance

    ActivityActive
    ResponsivenessNo issues

    Resources