Skip to main content
Glama
Sign In
xdragonjia

leafmem

by xdragonjia
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

Related Servers

Alternatives to leafmem

No user-submitted related servers found.

    Related Servers

    • brainmem-mcp

      Jimmycarroll2021
      A
      license
      Not graded
      quality
      C
      maintenance
      MCP server for brainmem, providing memory search, write, outcome, explain, and status tools to give LLM agents auditable long-term memory. It prioritizes failures, gates writes on surprise, and supports validity intervals for beliefs.
      Apache 2.0
    • adl-context-collector by ammons-datalabs

      adl-context-collectorofficial

      ammons-datalabs
      A
      license
      Not graded
      quality
      C
      maintenance
      MCP server providing persistent memory for LLMs via semantic search over captures, structured facts with temporal tracking, and document ingestion. Enables any MCP-compatible client to maintain a searchable knowledge base across sessions.
      ISC

    • mnemo

      krat214
      A
      license
      Not graded
      quality
      D
      maintenance
      Persistent memory MCP server for AI agents, featuring a visual interface to browse, search, edit, and delete memory. It provides tools for capturing episodes, recalling, consolidating, crystallizing traits, and forgetting, with local SQLite storage and optional authenticated web UI.
      MIT

    • llm-memory-tool

      menoxz
      A
      license
      Not graded
      quality
      D
      maintenance
      MCP server that enables persistent, hybrid, local memory for LLM agents, with vector + BM25 search, knowledge graph, and policy-driven retention, providing token-budgeted context injection for AI assistants.
      MIT
    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.1/5.0

    Scored across 4 tools

    Disambiguation3/5

    The four tools have distinct high-level purposes (recall, write, organize, govern), but their descriptions bundle many sub-operations with overlapping concepts. Notably, 'distill active context/experience' in memory_write overlaps with 'distill principles' and 'maintain active experience' in memory_organize, which could confuse an agent about which tool to use for those tasks.

    Naming Consistency5/5

    All tool names follow a consistent memory_verb pattern in snake_case, with clear, distinct verbs (recall, write, organize, govern). This predictability makes the set easy to navigate.

    Tool Count4/5

    Four tools is a reasonable count for a memory management server, grouping operations into lifecycle phases. However, each tool is very broad and handles many sub-operations, which could argue for slightly more granularity.

    Completeness5/5

    The tool surface covers the full memory lifecycle: reading/searching (recall), creating/updating (write), curation/maintenance (organize), and governance (update/delete/attribute). No obvious gaps for the stated domain.

    Maintenance

    ActivityActive
    ResponsivenessNo issues

    Resources