Skip to main content
Glama
denislamard

loom-memory

by denislamard
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

Related Servers

Alternatives to loom-memory

No user-submitted related servers found.

    Related Servers

    • mcp-memory-hnsw

      abho7
      A
      license
      Not graded
      quality
      A
      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

    • MemoryAI Local

      cenkierpiotr
      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

    • VeraMem

      Thebinary110
      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.
      159 PyPI
      Apache 2.0

    • mem0-mcp-selfhosted

      Wael1349
      F
      license
      Not graded
      quality
      A
      maintenance
      Enables Claude Code to add, search, update, delete, and organize persistent memories across sessions using self-hosted Qdrant, Neo4j, and Ollama, with optional Anthropic or local LLM support. It also exposes tools for knowledge-graph entity relationship search and retrieval.
      -
    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.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.

    Maintenance

    ActivityMaintained
    ResponsivenessNo issues

    Resources