Skip to main content
Glama
v1b3x0r

living-memory-engine

by v1b3x0r
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Hybrid

Related Servers

Alternatives to living-memory-engine

No user-submitted related servers found.

    Related Servers

    • mnemory

      fpytloun
      A
      license
      Not graded
      quality
      A
      maintenance
      Self-hosted MCP server giving AI agents persistent memory for personalization and context across conversations.
      152 PyPI
      277
      Apache 2.0

    • saor-mcp

      ubajxn
      A
      license
      A
      quality
      C
      maintenance
      MCP server providing persistent memory for AI agents, enabling them to read, write, and query memories across sessions.
      9
      4 npm
      MIT
    • Structured-sh by structured-sh

      Structured-shofficial

      structured-sh
      A
      license
      Not graded
      quality
      D
      maintenance
      MCP server providing managed persistent memory for AI agents. Read and write structured state across sessions, tools, and restarts at 1000+ requests per second, with no infrastructure to self-host or operate.
      2
      Apache 2.0

    • kernl

      fastslack
      A
      license
      Not graded
      quality
      A
      maintenance
      A self-hosted MCP server that provides any LLM with a graph-backed memory layer of your life—tasks, email, finance, contacts, calendar—plus autonomous agent offices that act on your behalf.
      1
      Apache 2.0

    • agent-memex

      Gudmundur76
      F
      license
      Not graded
      quality
      B
      maintenance
      Free, persistent memory layer for AI agents, enabling storage and semantic search of memories via MCP or REST.
      -
    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.2/5.0

    Scored across 4 tools

    Disambiguation5/5

    Each tool has a clearly distinct purpose: add, search, summarize, and delete. There is no meaningful overlap between retrieval (search) and store-state inspection (state), and forget is explicitly destructive and separate.

    Naming Consistency4/5

    All tools share a consistent memory_ prefix and lowercase style. memory_state is a noun where the others use action verbs, which is a minor deviation but does not create confusion.

    Tool Count5/5

    Four tools is a well-scoped, focused set for a memory engine. Each tool covers a core need without unnecessary surface area or duplication.

    Completeness4/5

    The toolset covers the essential lifecycle: store, retrieve, inspect state, and delete. A precise single-item delete or explicit memory update would round it out, but the destructive substring delete plus memory_add makes common workflows workable.

    Maintenance

    ActivityMaintained
    ResponsivenessUnresponsive

    Resources