Skip to main content
Glama
lakehouse-42

memory-mcp

by lakehouse-42
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Hybrid

Related Servers

Alternatives to memory-mcp

No user-submitted related servers found.

    Related Servers

    • Qoopia by qoopia

      Qoopiaofficial

      qoopia
      A
      license
      Not graded
      quality
      A
      maintenance
      Provides persistent memory for AI agents via MCP, enabling agents to store and access notes, files, and session context across sessions and clients while under user control.
      4
      MIT

    • mcp-memory

      oneKn8
      A
      license
      A
      quality
      D
      maintenance
      Provides persistent memory with semantic search for MCP-based AI agents, enabling them to store and recall information across sessions using vector embeddings.
      4
      1
      MIT

    • Remembra

      Hilbras
      A
      license
      A
      quality
      A
      maintenance
      Provides external memory for AI assistants, storing facts, decisions, roles, and history outside the context window and retrieving relevant memories via MCP tools.
      13
      825 npm
      2
      MIT

    • engram

      TushaeBXN
      A
      license
      Not graded
      quality
      B
      maintenance
      Provides persistent, local-first AI memory across sessions via MCP tools for storing, searching, and retrieving context from past interactions.
      1
      MIT

    • HippoDid MCP Server

      SameThoughts
      A
      license
      Not graded
      quality
      C
      maintenance
      Provides persistent, cloud-based memory for AI agents, letting them remember preferences, skills, and decisions across sessions via an MCP-compatible interface.
      Apache 2.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

    A3.9/5.0

    Scored across 5 tools

    Disambiguation5/5

    Each tool targets a distinct action: remember stores, recall searches, forget deletes, list_memories lists, and memory_status reports system status. There is no ambiguity or overlap between them.

    Naming Consistency4/5

    Names are mostly verb-based and readable, but there is a slight inconsistency: remember, recall, and forget are bare verbs, while list_memories is verb_noun and memory_status is noun_noun. A more uniform pattern like get_memory_status would improve consistency.

    Tool Count5/5

    With 5 tools, the server is well-scoped for a memory system. Each tool covers a necessary function without redundancy, making the set neither too thin nor overly heavy.

    Completeness4/5

    The tools cover the core CRUD operations (create, read, delete) plus status. The only minor gap is the lack of an explicit update tool, but users can forget and re-remember to modify entries, so the shortfall is easily worked around.

    Maintenance

    ActivityInactive
    ResponsivenessNo issues

    Resources