Skip to main content
Glama
fariborzvrm

Memento

by fariborzvrm
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

Related Servers

Alternatives to Memento

No user-submitted related servers found.

    Related Servers

    • Stoa

      BrettNye
      A
      license
      Not graded
      quality
      C
      maintenance
      Persistent shared memory for AI coding agents that turns a folder of markdown files into searchable memory across sessions, repos, and machines.
      12 npm
      Functional Source , Version 1.1, MIT Future

    • context-vault

      fellanH
      F
      license
      Not graded
      quality
      B
      maintenance
      Persistent memory for AI agents enabling saving, searching, and managing knowledge across sessions with local markdown files.
      1
      -

    • agtmem-mcp

      ihletru
      A
      license
      A
      quality
      B
      maintenance
      Enables coding agents to store, search, and retrieve long-term memory as plain Markdown files with a disposable SQLite index, including note management, decision/bug tracking, and codebase symbol lookup via MCP.
      8
      MIT

    • agent-memory

      jcyamacho
      F
      license
      Not graded
      quality
      F
      maintenance
      Persistent memory for MCP-powered coding agents, allowing LLMs to remember preferences, project context, and decisions across sessions via Markdown files.
      11 npm
      -

    • memory

      go-ports
      A
      license
      Not graded
      quality
      A
      maintenance
      Provides coding agents with persistent local memory by exposing tools to save, search, and retrieve decisions, bugs, and context as Markdown with hybrid keyword and semantic search.
      4
      MIT
    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

    Disambiguation4/5

    The tools are mostly distinct: read_all and search differ in scope (full dump vs targeted lookup), and write/update/log each have clear intents. The only minor ambiguity is write with type 'log' overlapping the dedicated log tool, but descriptions sufficiently clarify the difference.

    Naming Consistency4/5

    All tool names are imperative verbs (search, write, update, log, read_all), which makes them predictable. The slight deviation is 'read_all' with an underscore suffix versus the single-word names of the other tools, but the pattern is still coherent.

    Tool Count5/5

    Five tools is well-scoped for a memory-management server. Each tool covers a distinct core operation—full read, search, create, update, and session logging—without bloat or trivial fragmentation.

    Completeness4/5

    The toolset covers reading, searching, writing, updating, and logging, which handles the main memory lifecycle. There is no explicit delete, but update can set status to inactive, so the gap is minor and workaroundable.

    Maintenance

    ActivityMaintained
    ResponsivenessNo issues

    Resources