Skip to main content
Glama

Related Servers

Alternatives to loom-memory

No user-submitted related servers found.

    Related Servers

    • A
      license
      Not graded
      quality
      B
      maintenance
      Provides persistent semantic memory for Claude Code and Claude Desktop with fully offline local embeddings and HNSW indexing, enabling memory storage, semantic search, listing, and deletion across sessions.
      MIT
    • A
      license
      Not graded
      quality
      B
      maintenance
      Provides persistent long-term memory and local RAG document search for Claude Desktop, fully offline. Enables memory save/search and document retrieval via MCP.
      MIT
    • A
      license
      A
      quality
      B
      maintenance
      Persistent memory for Claude Code. Automatically indexes every conversation and provides production-grade hybrid search (BM25 + vectors + reranker) via MCP tools. 100% local, zero config, zero API keys, zero invoice.
      16
      33
      7
      MIT
    • A
      license
      Not graded
      quality
      C
      maintenance
      Provides local-first, cross-session memory for Claude Code, enabling semantic search across past sessions to retrieve procedures, decisions, or answers without exposing secrets.
      Apache 2.0

    TDQS

    A3.8/5.0

    Scored across 9 tools

    Disambiguation5/5

    Each tool targets a distinct operation: get (single doc read), search (hybrid retrieval), list_docs (recent listing), projects (aggregate counts), update (replace text), delete (remove), and three add variants differentiated by source (raw text, URL, local file). The add_* trio could superficially overlap but their input types are clearly separated, so an agent won't misselect.

    Naming Consistency3/5

    The set mixes bare verbs (get, delete, search, update) with verb_noun forms (list_docs, add_text, add_url, add_file) and a bare noun (projects). It's readable and snake_case throughout, but there's no single predictable convention, with 'projects' being the most notable outlier.

    Tool Count5/5

    Nine tools is well-scoped for a personal memory store covering read, search, list, aggregate, create-by-source, update, and delete. Each tool earns its place with no redundant members.

    Completeness5/5

    Full lifecycle is covered: creation (add_text/add_url/add_file), reading (get), retrieval (search), browsing (list_docs, projects), update (update), and removal (delete). No obvious dead ends for a memory system of this scope.