Skip to main content
Glama

Related Servers

Alternatives to tua

No user-submitted related servers found.

    Related Servers

    • A
      license
      A
      quality
      B
      maintenance
      Enables LLMs to maintain persistent memory by reading and writing Markdown notes and sibling image assets in a user-selected local or sync folder, with no cloud service, account, or server to run.
      6
      453 npm
      MIT
    • A
      license
      Not graded
      quality
      A
      maintenance
      Enables AI agents to capture, structure, remember, and retrieve source-backed memory as local Markdown files, with reviewable writes and no cloud dependency.
      218
      MIT
    • A
      license
      B
      quality
      B
      maintenance
      Enables AI agents to securely read, search, and write to a local Markdown knowledge base with hybrid RAG retrieval, privacy zones, hash-locked writes, audit logging, and rollback-safe archiving.
      13
      MIT
    • A
      license
      Not graded
      quality
      B
      maintenance
      A personal, offline-first memory for AI assistants that enables them to read, search, and write to a shared folder of Markdown files, so they all remember you without needing a cloud.
      1
      MIT
    • A
      license
      Not graded
      quality
      B
      maintenance
      Gives AI apps a shared, plain-folder memory on your own machine, so whatever you tell one model the others can read, and you can inspect, review and undo every change they make. Memory stays portable across vendors, models and account changes instead of living on a provider's servers.
      192 PyPI
      29
      Apache 2.0
    • A
      license
      Not graded
      quality
      D
      maintenance
      Provides persistent long-term memory for AI assistants with tag-based retrieval, wiki-style linking, and source references, storing memories as markdown files with SQLite index.
      2
      MIT

    TDQS

    A4/5.0

    Scored across 11 tools

    Disambiguation4/5

    Each tool has a distinct role: save creates atoms, search/get/list retrieve them, compose assembles deliverables, link/unlink manage cross-project visibility, card/open handle UI and external files. The only mild overlap is between search/get (text retrieval) and card (visual display) or card-with-query, but descriptions explicitly steer the agent ('use tua_search/tua_get when you need the text').

    Naming Consistency5/5

    Every tool uses a consistent tua_ prefix followed by a single lowercase verb in snake_case (save, setup, import, search, get, list, compose, link, unlink, card, open), with a clean link/unlink pairing. No convention mixing anywhere in the set.

    Tool Count4/5

    11 tools sits comfortably in the well-scoped 3-15 range and covers distinct lifecycle stages. A couple of tools are auxiliary (tua_setup is one-time, tua_open is only used by the card), which slightly dilutes the core surface but doesn't make it bloated.

    Completeness4/5

    The surface covers create, import, search, retrieve, list, compose, relate, view, and open—strong lifecycle coverage. Minor gaps remain: no explicit delete tool and no dedicated tag/update management (updates seem to rely on re-saving with the same key), which agents must work around.

    Maintenance

    ActivityMaintained
    ResponsivenessNo recent community issues