Skip to main content
Glama
lalithbuilds

Engram Alpha

by lalithbuilds
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Hybrid

Related Servers

Alternatives to Engram Alpha

No user-submitted related servers found.

    Related Servers

    • local-memory-mcp

      mason-yb-zhang
      F
      license
      Not graded
      quality
      C
      maintenance
      Provides AI agents with persistent, local cross-session shared memory by combining vector semantic retrieval with knowledge graph relationships, and supports short/long-term memory management and local backups.
      -

    • ClawMem MCP Server

      BFLabsAI
      A
      license
      Not graded
      quality
      D
      maintenance
      Enables AI agents to maintain persistent, local memory with retrieval-augmented search, knowledge graphs, and context surfacing, without any cloud dependencies.
      52 npm
      MIT

    • skillmem

      liza-studio
      A
      license
      A
      quality
      A
      maintenance
      Procedural memory for coding agents: not facts about the user, but how a task was solved — trigger, steps, outcome, lessons. Hooks recall it automatically; skills strengthen only on outside evidence and unused ones decay. Each memory carries its provenance and only the owner approves one as a rule. Local SQLite + FTS5, no API key, no cloud. One database for Claude Code, Codex and Cursor.
      2
      9
      677 PyPI
      5
      Apache 2.0

    • rekal

      janbjorge
      A
      license
      Not graded
      quality
      A
      maintenance
      Provides long-term memory for LLMs via local SQLite storage with hybrid search (BM25, vectors, recency decay), enabling AI coding agents to persist and recall memories across sessions without cloud or API keys.
      53
      MIT
    Deploy Server
    One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

    TDQS

    B3.4/5.0

    Scored across 15 tools

    Disambiguation4/5

    Most tools have distinct targets: memory nodes, graph relations, ingestion, maintenance, and stats. A few pairs like save_memory vs extract_and_save_memory or search_memory vs auto_context could overlap, but their descriptions clarify the intended workflow. No tools are truly redundant.

    Naming Consistency4/5

    Tool names are consistently lowercase snake_case and mostly follow a verb-first pattern. The main outlier is auto_context, which is a noun phrase, and graph-related names mix save_graph_relation, query_graph, and visualize_graph. Overall the pattern remains predictable and readable.

    Tool Count5/5

    15 tools is at the upper edge of ideal but well-scoped for a memory system that combines vector storage, knowledge graph operations, ingestion, reflection, and maintenance. Each tool serves a distinct purpose, and none feel purely decorative or redundant.

    Completeness4/5

    Memory CRUD is well covered with save, search, edit, delete, and list, and graph relations have save and query support. Missing direct graph relation editing/deletion and a get-memory-by-ID tool are minor gaps, but cascade deletion and search/list provide workarounds.

    Maintenance

    ActivityMaintained
    ResponsivenessNo issues

    Resources