Skip to main content
Glama
engram
by TushaeBXN

Related Servers

Alternatives to engram

No user-submitted related servers found.

    Related Servers

    • A
      license
      Not graded
      quality
      C
      maintenance
      Provides a local-first persistent memory layer for AI coding agents through MCP, enabling them to save, search, retrieve, update, and consolidate project context, technical decisions, debugging solutions, and developer preferences across sessions.
      MIT
    • A
      license
      Not graded
      quality
      D
      maintenance
      Local-first AI memory layer with hybrid retrieval and brain-inspired namespaces. Enables agents to save, search, and manage memories directly via MCP tools.
      6 npm
      MIT
    • A
      license
      Not graded
      quality
      B
      maintenance
      Provides a local-first persistent memory layer for coding assistants, enabling cross-project user preferences, per-project durable and working memory, session archives, and reflective recommendations through MCP tools.
      43 npm
      MIT
    • A
      license
      Not graded
      quality
      A
      maintenance
      Provides persistent memory for AI coding agents via MCP, enabling agents to store and semantically recall facts, events, and lessons across sessions, all running locally without cloud dependencies.
      Apache 2.0
    • F
      license
      Not graded
      quality
      A
      maintenance
      Provides local-first, cross-session persistent memory that lets AI coding agents store, semantically search, and recall project-specific and cross-project knowledge via MCP tools and resources, with an optional task queue for autonomous execution.
      -
    • A
      license
      A
      quality
      D
      maintenance
      Provides persistent memory for AI assistants via MCP, enabling them to store and recall facts, preferences, and tasks across conversations using either local file storage or a cloud backend with semantic search.
      5
      6 npm
      MIT

    TDQS

    C2.8/5.0

    Scored across 31 tools

    Disambiguation3/5

    Several clusters overlap: engram_check vs engram_audit, engram_recall vs engram_search, engram_supersede vs engram_correct vs engram_link(supersedes), engram_source vs engram_link(based_on), and engram_history vs engram_why. Descriptions help distinguish them, but an agent must read carefully to avoid misselection among memory-lifecycle and maintenance tools.

    Naming Consistency4/5

    All tools use the engram_ prefix and snake_case, with a clear kg_ subgroup. Most names are verb_noun or noun_resource, but bare verbs/nouns like status, recall, why, history, audit, and pin are minor deviations rather than inconsistent conventions.

    Tool Count2/5

    At 31 tools, the surface is heavy for a memory server and exceeds the typical well-scoped range. Several operations could be consolidated (check/audit, supersede/correct/link, recall/search), making the set feel over-expanded rather than tightly scoped.

    Completeness4/5

    Coverage is broad: add/search/correct/supersede/dispute/link/source/why/history, temporal KG operations, wing/room/drawer structure, context loading, diary, compression, and audits. Minor gaps like deleting wings/rooms or directly editing drawer metadata remain, but there are no core workflow dead ends.

    Maintenance

    ActivityMaintained
    ResponsivenessNo recent community issues