Skip to main content
Glama
HBarefoot

Engram

by HBarefoot
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Local

Related Servers

Alternatives to Engram

Related Servers

  • ClawMem MCP Server

    BFLabsAI
    A
    license
    Not graded
    quality
    B
    maintenance
    Enables AI agents to maintain persistent, local memory with retrieval-augmented search, knowledge graphs, and context surfacing, without any cloud dependencies.
    180
    MIT
  • PLUR by plur-ai

    PLURofficial

    plur-ai
    A
    license
    B
    quality
    A
    maintenance
    Open, local-first engram memory for AI agents: read, correct, and delete what your agent remembers. Works across Claude Code, Hermes, OpenClaw, and Cursor over MCP.
    39
    1,858,293
    267
    Apache 2.0

  • GENOME MCP Server

    NORTHTEKDevs
    A
    license
    A
    quality
    A
    maintenance
    A local, offline memory server for AI agents that stores and retrieves memories without LLM calls, enabling persistent cross-session memory with bi-temporal querying and auditable records.
    2
    4
    5
    Apache 2.0

  • Engram MCP

    vedtechsolutions
    A
    license
    Not graded
    quality
    D
    maintenance
    Engram MCP provides persistent, cross-session memory for AI agents by automatically encoding errors, decisions, and discoveries during development sessions. It enables local, intelligent recall and automated context management to help AI learn from experience and avoid recurring mistakes.
    123
    Business Source 1.1

  • SharedBrain

    awictor
    A
    license
    Not graded
    quality
    B
    maintenance
    Local-first, multi-user shared memory for AI agents with semantic search, offline support, and team synchronization.
    MIT
Deploy Server
RayrunBuild, deploy, and operate MCP servers without becoming an infrastructure team.ray.runAd

TDQS

A4.8/5.0

Scored across 6 tools

Disambiguation5/5

Each tool has a unique, well-defined purpose: context formatting, feedback, deletion, recall, storage, and status. No overlap exists; descriptions explicitly contrast pairs like engram_context vs engram_recall.

Naming Consistency5/5

All tool names follow a consistent 'engram_verb' pattern using snake_case (e.g., engram_remember, engram_forget). The verbs clearly indicate the action, and there are no deviations or mixed conventions.

Tool Count5/5

Six tools cover the essential operations for a memory system (create, read in two forms, feedback, delete, status) without unnecessary bloat. The count feels natural and well-scoped for the server's purpose.

Completeness4/5

The tool surface covers create (remember), read (recall, context), update confidence via feedback, delete (forget), and status. The only noteworthy gap is the lack of a direct tool to edit a memory's content, though merging in 'remember' partially addresses it.

Maintenance

ActivityStale
ResponsivenessResponsive

Resources