Skip to main content
Glama
jgauffin

Relax Memory MCP

by jgauffin
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

Related Servers

Alternatives to Relax Memory MCP

No user-submitted related servers found.

    Related Servers

    • Mem0 MCP Server

      ryaker
      A
      license
      Not graded
      quality
      C
      maintenance
      A Model Context Protocol server that integrates AI assistants with Mem0.ai's persistent memory system, allowing models to store, retrieve, search, and manage different types of memories.
      16
      MIT

    • agenticmemory

      jyswee
      A
      license
      Not graded
      quality
      B
      maintenance
      Persistent memory MCP server for AI agents that stores, recalls, and searches conversation history, key-value context, and long-term entries across sessions with semantic search and FIFO queues.
      48 npm
      1
      -

    • 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

    • Eternity MCP

      danttis
      A
      license
      Not graded
      quality
      D
      maintenance
      A privacy-focused local memory server that provides long-term semantic storage and retrieval for AI agents using SQLite and ChromaDB. It enables LLMs to persist and query text, chat histories, and PDF documents across sessions through the Model Context Protocol.
      MIT

    • memento-context

      FranBarInstance
      A
      license
      A
      quality
      D
      maintenance
      A Model Context Protocol server that gives AI assistants persistent, scoped memory by saving and retrieving short notes (mementos) across sessions and projects, enabling dynamic learning and context injection without heavy dependencies.
      8
      2
      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 4 tools

    Disambiguation5/5

    Each tool has a clearly distinct purpose: add/update, retrieve, delete, and list. No overlap or ambiguity exists.

    Naming Consistency5/5

    All tool names follow a consistent verb_noun snake_case pattern (add_memory, get_memory, delete_memory, list_memories). The pluralization of 'list_memories' is a minor stylistic variance but does not break the pattern.

    Tool Count5/5

    With only 4 tools, the set is well-scoped and perfectly sized for a simple memory storage service. Each tool serves a necessary CRUD function.

    Completeness5/5

    The tool surface covers the complete lifecycle of memories: create/update, read, delete, and list. No obvious gaps exist for the stated domain.

    Maintenance

    ActivityInactive
    ResponsivenessNo issues

    Resources