Skip to main content
Glama

Related Servers

Alternatives to Mnemento

No user-submitted related servers found.

    Related Servers

    • A
      license
      Not graded
      quality
      B
      maintenance
      Enables AI agents and LLMs to persist facts, preferences, and observations in a local SQLite store and to build and traverse subject-predicate-object knowledge graphs across sessions. It provides fuzzy keyword search and graph queries so assistants retain context and recall prior project history without repeating prompts.
      1
      MIT
    • A
      license
      A
      quality
      C
      maintenance
      Enables Claude Code and other MCP-capable agents to turn conversations into structured long-term memories, deciding whether each extracted fact is new, an update, or already known while preserving superseded history. It also lets agents recall the right facts through hybrid keyword and entity-graph search, list what is stored, and permanently forget entries.
      5
      MIT
    • A
      license
      Not graded
      quality
      B
      maintenance
      Enables MCP clients such as Claude Desktop, Cursor and Claude Code to add, search, answer from, and audit an agent's long-term memory stored in a single local SQLite file. Memories are backed by verifiable quotes, ranked by task outcomes, access-controlled, and usable fully offline.
      Apache 2.0
    • A
      license
      A
      quality
      B
      maintenance
      Gives every AI agent you use one shared, versioned memory in a local SQLite file, so a fact saved from one app is found by all the others. Runs fully offline with no API key, records which agent wrote each change, and keeps every prior version so nothing is silently overwritten.
      7
      964 npm
      8
      MIT
    • A
      license
      Not graded
      quality
      A
      maintenance
      Enables AI agents to maintain auditable, local-first long-term memory in a single SQLite file, preserving source evidence and retiring dependent memories when sources are corrected so Claude Code, Cursor, and Codex start from current recorded evidence.
      703 npm
      156
      MIT

    TDQS

    A3.7/5.0

    Scored across 14 tools

    Disambiguation5/5

    Each tool has a clearly distinct role: recording facts vs. series, querying vs. reading query logs, preview/apply/revert for ingest, and proposal vs. application for schemas. Overlaps are explicitly resolved in descriptions, so an agent can reliably select the intended tool.

    Naming Consistency4/5

    Almost all names use predictable snake_case with verb_noun or verb_noun_noun patterns (record_series, ingest_apply, apply_schema_proposal). A few single-word tools like query, record, and history deviate slightly but remain clear and consistent in style.

    Tool Count5/5

    14 tools are well within the sweet spot for a domain that spans recording, querying, ingestion, history, and schema management. Each tool earns its place with a specific operation, and there is no redundant surface area.

    Completeness4/5

    The surface covers record lifecycle through explicit kinds (created, updated, corrected, retracted), series batches with revert, ingest lifecycle, querying, history, and schema proposals. Minor gaps exist, such as no dedicated list-entities operation, but query and get_entity provide workarounds.

    Maintenance

    ActivityMaintained
    ResponsivenessOutdated data