Skip to main content
Glama
FranBarInstance

memento-context

by FranBarInstance
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python

Related Servers

Alternatives to memento-context

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

    • MCP Memory Server

      StevenWangler
      A
      license
      B
      quality
      D
      maintenance
      A Model Context Protocol server that provides knowledge graph-based persistent memory for LLMs, allowing them to store, retrieve, and reason about information across multiple conversations and sessions.
      9
      114,646 npm
      2
      MIT

    • AGI MCP Server

      QuixiAI
      F
      license
      B
      quality
      D
      maintenance
      A Model Context Protocol server that provides persistent memory capabilities for AI systems, enabling true continuity of consciousness across conversations through episodic, semantic, procedural, and strategic memory types.
      24
      6
      -

    • MCP Memory Tracker

      akaiserg
      F
      license
      B
      quality
      D
      maintenance
      A Model Context Protocol (MCP) server that provides persistent memory capabilities using OpenAI's vector stores, allowing AI assistants to save and search through memories across conversations.
      2
      -
    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

    A3.7/5.0

    Scored across 8 tools

    Disambiguation4/5

    Tools are largely distinct: init/get/save/delete/move cover clear lifecycle operations, and attachment/conversation save are separately named. Some overlap exists between save_memento and save_conversation (both persist mementos, differing mainly by whether attachments are included), but descriptions help disambiguate. The confusing 'mandatory init first' pattern creates redundancy concern but not ambiguity.

    Naming Consistency4/5

    Most tools follow a consistent verb_memento pattern: init_memento, get_mementos, save_memento, delete_memento, move_memento, get_memento_attachments, save_memento_attachments, save_conversation. Minor deviation with save_conversation breaking the pattern, and pluralization of get_mementos vs singular memento naming is slightly inconsistent.

    Tool Count5/5

    8 tools is well within the ideal 3-15 range for a memory/context management server. Each tool serves a clear purpose in the lifecycle: initialization, retrieval, saving, attachment handling, deletion, and movement. No unnecessary tools present.

    Completeness4/5

    The tool surface covers the full memento lifecycle: init, read (with scope filtering), create, attach files, delete, move, and conversation capture. Minor gaps exist—there's no update/edit operation for an existing memento's content (only delete then save), and no search/filter tool beyond basic scope filtering.

    Maintenance

    ActivityInactive
    ResponsivenessNo issues

    Resources