Skip to main content
Glama
pinkpixel-dev

mem0 Memory System

by pinkpixel-dev
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Hybrid

Related Servers

Alternatives to mem0 Memory System

No user-submitted related servers found.

    Related Servers

    • GNB MemoryMCP

      GennoBou
      F
      license
      Not graded
      quality
      A
      maintenance
      A vendor-independent memory layer MCP server that enables multiple LLMs and AI agents to share and persist personal memories, knowledge, and context across sessions, with support for full-text search and tagging.
      -

    • GroundMemory

      huss-mo
      A
      license
      Not graded
      quality
      C
      maintenance
      An MCP-native, local-first memory server that gives AI agents persistent, structured memory across sessions and tools, enabling them to maintain identity and context without reconfiguration.
      3
      MIT

    • mindcore-memory-mcp

      woshilaohei
      A
      license
      A
      quality
      C
      maintenance
      A production-grade long-term memory MCP server that enables AI agents to persist and recall memories across sessions with importance weighting, confidence calibration, and efficient context window management.
      9
      20 PyPI
      1
      MIT

    • mem0-agent-memory

      arunkumars-mf
      A
      license
      A
      quality
      D
      maintenance
      An MCP server that provides persistent memory capabilities for AI agents using Mem0, enabling storage, search, and management of contextual information across conversations with support for multiple backends and LLM providers.
      18
      21 PyPI
      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

    B3.3/5.0

    Scored across 3 tools

    Disambiguation5/5

    Each tool has a clearly distinct purpose: add_memory stores new data, delete_memory removes by ID, and search_memory retrieves based on queries. There is no overlap or ambiguity between these three core operations.

    Naming Consistency5/5

    All tools follow a consistent verb_noun pattern (add_memory, delete_memory, search_memory) with snake_case throughout. The naming is predictable and uniform across the set.

    Tool Count3/5

    With only 3 tools, the set feels minimal for a memory system. While it covers basic CRUD operations (create, delete, read), it lacks update functionality and other potential features like listing or managing memory collections, making it borderline thin for the domain.

    Completeness4/5

    The tools provide essential CRUD coverage (add, delete, search) for a memory system, but there are minor gaps such as no update_memory tool to modify existing memories and no way to list all memories without a query. Agents can work around this by deleting and re-adding, but it's not ideal.

    Maintenance

    ActivityInactive
    ResponsivenessNo issues

    Resources