Skip to main content
Glama

Related Servers

Alternatives to loom

No user-submitted related servers found.

    Related Servers

    • A
      license
      Not graded
      quality
      D
      maintenance
      Provides persistent, cloud-based memory for AI agents, letting them remember preferences, skills, and decisions across sessions via an MCP-compatible interface.
      Apache 2.0
    • A
      license
      Not graded
      quality
      B
      maintenance
      Enables AI agents to maintain a persistent identity and structured memory—including reasoning patterns, episodic history, and knowledge—while exposing procedures for managing that memory over MCP.
      Apache 2.0
    • A
      license
      Not graded
      quality
      B
      maintenance
      Provides persistent memory for AI agents via MCP, enabling agents to store and access notes, files, and session context across sessions and clients while under user control.
      4
      MIT
    • A
      license
      Not graded
      quality
      B
      maintenance
      Enables self-hosted, persistent AI identity and long-term memory across clients, models, and agent surfaces, with multi-resident isolation, shared world knowledge, governed memory writes, correction and forgetting, keyword or optional semantic recall, and MCP or HTTP access.
      79
      MIT
    • A
      license
      Not graded
      quality
      C
      maintenance
      Enables AI agents to maintain persistent memory across sessions by capturing conversations, extracting durable knowledge, and injecting relevant context, supporting various MCP-compatible platforms.
      12
      MIT
    • A
      license
      Not graded
      quality
      B
      maintenance
      Provides AI agents with persistent, human-like memory infrastructure via MCP, enabling them to store, search, summarize, and forget episodic, semantic, procedural, and working memories across sessions.
      280 npm
      MIT

    TDQS

    A3.7/5.0

    Scored across 43 tools

    Disambiguation3/5

    Many tools have carefully written boundaries, but the memory/knowledge lifecycle surfaces overlap heavily: memory_archive vs memory_merge vs forget vs memory_prune; knowledge_archive vs knowledge_supersede vs knowledge_merge vs knowledge_purge; memory_restore vs memory_revision_restore. Descriptions help resolve most cases, but an agent must read closely to choose correctly.

    Naming Consistency3/5

    All names use snake_case, but conventions are mixed: domain-prefixed verbs (memory_list, knowledge_write, person_verify) coexist with bare names (identity, episodes, recall, remember, forget, update, dossier, bootstrap) and update_identity instead of identity_update. The pattern is readable but not predictable.

    Tool Count2/5

    43 tools is heavy for any single server and exceeds the 25+ threshold. While the server spans several domains (identity, memory, knowledge, person, harness), many lifecycle variants inflate the surface, making discovery and selection harder.

    Completeness5/5

    The surface covers full lifecycles for memory, knowledge, person cards, and identity, including create/read/update/delete, archive/restore, revision history, verification, proposals, audits, merging, moving, and supersession. No obvious domain operation is missing.

    Maintenance

    ActivityActive
    ResponsivenessNo recent community issues