Skip to main content
Glama

Related Servers

Alternatives to RecallVault

No user-submitted related servers found.

    Related Servers

    • A
      license
      A
      quality
      C
      maintenance
      Enables coding agents to save facts, decisions and conventions into a single SQLite file and search them again in later sessions. Recall is ranked by BM25 relevance boosted by recency and scoped per project, with zero native dependencies.
      4
      MIT
    • A
      license
      Not graded
      quality
      A
      maintenance
      Provides AI assistants a local, hybrid semantic+keyword memory vault to save research findings, notes, and project context, and recall them across sessions with session boot/save tools.
      4 npm
      2
      MIT
    • A
      license
      Not graded
      quality
      A
      maintenance
      Local memory for AI agents in one SQLite file on your own machine. Facts carry a validity window and a confidence score, so an outdated one is superseded and downweighted rather than deleted, and retrieval fuses BM25, vector similarity and a knowledge graph.
      2
      Business Source 1.1
    • A
      license
      A
      quality
      A
      maintenance
      Local memory for AI agents over plain Markdown files: hybrid vector + BM25 recall (RRF), one isolated memory per agent directory, fully offline with no LLM in the loop. Tools: cogvault_recall and cogvault_record.
      2
      46 PyPI
      1
      MIT
    • A
      license
      Not graded
      quality
      B
      maintenance
      Enables AI agents to store and recall durable facts, decisions, and lessons over MCP using hybrid semantic and keyword search, typed memories, graph relations, sessions, and time-travel queries. Runs locally with no server process or API key, persisting everything to files that both agents and a CLI can share.
      13 npm
      MIT
    • A
      license
      A
      quality
      B
      maintenance
      Enables AI agents to persist facts with tags, sources, and importance in a local SQLite database, retrieve them through hybrid BM25 plus embedding search weighted by retention decay, link or supersede related entries, and review everything in a read-only visual dashboard showing the memory graph and timeline.
      6
      MIT

    TDQS

    B3.4/5.0

    Scored across 10 tools

    Disambiguation4/5

    Most tools have clearly distinct purposes, but update_memory explicitly sets archived and priority fields, overlapping archive_memory and set_memory_priority. remember versus update_memory also requires care, though the descriptions distinguish create/append from replacement.

    Naming Consistency3/5

    The set mixes verb_noun names like list_memories, archive_memory, and delete_memory with bare verbs like remember and recall, plus noun-first names like health_check, memory_setup, and memory_import. It remains readable, but there is no single predictable convention.

    Tool Count5/5

    Ten tools are well-scoped for a memory vault: CRUD/search, archive, priority, setup/import, and health check. Each tool has a plausible place in the lifecycle, with no obvious bloat.

    Completeness4/5

    The surface covers create/append, search/retrieve, list, update, delete, archive, priority, setup/import, and health. There is no dedicated get-by-id or bulk operation, but recall and list_memories cover retrieval and inspection well enough for core workflows.

    Maintenance

    ActivityMaintained
    ResponsivenessNo issues