engram
Related Servers
Alternatives to engram
No user-submitted related servers found.
Related Servers
- AlicenseNot gradedqualityDmaintenanceLocal-first AI memory layer with hybrid retrieval and brain-inspired namespaces. Enables agents to save, search, and manage memories directly via MCP tools.5 npmMIT
- AlicenseNot gradedqualityBmaintenanceProvides 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 npmMIT
- AlicenseNot gradedqualityAmaintenanceProvides 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
- FlicenseNot gradedqualityAmaintenanceProvides 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.-
- AlicenseAqualityDmaintenanceProvides 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.54 npmMIT
- AlicenseAqualityBmaintenanceProvides persistent, searchable memory for AI agents across any MCP-compatible client, storing project context, user preferences, and session learnings locally in SQLite with tools to save, retrieve, search, and manage them.126 npmMIT
TDQS
Scored across 26 tools
Most tools target distinct resources or actions, but engram_add_memory, engram_supersede, and engram_correct overlap heavily—add_memory even references possible updates, and correct vs supersede both describe replacing an outdated memory with a new one. Context-loading tools (wake_up, load_room, replay) are distinguishable but close in scope.
All tools share the engram_ prefix and snake_case, with a coherent kg_ sub-namespace for graph operations. Names mix single verbs (search, status, audit) with verb_noun forms (create_room, list_wings) but stay readable and predictable overall.
At 26 tools the surface is on the heavy side for a memory system, though the domain (memory CRUD, KG, diary, compression, lifecycle/pinning) genuinely spans several sub-areas. It sits just past the 25-tool mark where density starts to weigh on selection.
Coverage is broad: room/wing creation, drawer add/get/delete, supersede/correct/dispute/history lifecycle, full KG add/query/invalidate/timeline, diary read/write, and compression. Gaps are minor—no delete for wings/rooms and no explicit drawer update, but corrections largely cover mutation.