Skip to main content
Glama
light-agent-memory-mcp-server

light-agent-memory-mcp-server

by AliYar-Khan

Related Servers

Alternatives to light-agent-memory-mcp-server

No user-submitted related servers found.

    Related Servers

    • A
      license
      Not graded
      quality
      B
      maintenance
      Enables MCP-compatible AI coding tools to store and recall persistent memories across sessions and projects, with keyword and semantic search backed by a local SQLite database.
      709 npm
      75
      Apache 2.0
    • A
      license
      A
      quality
      C
      maintenance
      Provides persistent local memory for any MCP-compatible AI agent, enabling agents to store, search, recall, forget, export, and manage preferences, rules, and facts with zero dependencies, no cloud, and no API keys.
      8
      MIT
    • 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
      Persistent memory for AI coding agents. Enables agents to save and recall decisions, patterns, bugs, and context across sessions via an MCP server with local SQLite storage.
      24 npm
      2
      MIT
    • A
      license
      Not graded
      quality
      B
      maintenance
      Enables AI coding agents to persistently save, search, retrieve, update, link, and forget project-scoped memories through MCP tools, using local SQLite FTS5 keyword search without cloud access or telemetry.
      26 npm
      14
      MIT
    • A
      license
      C
      quality
      B
      maintenance
      Provides persistent, local-first AI memory across sessions via MCP tools for storing, searching, and retrieving context from past interactions.
      31
      698 PyPI
      1
      MIT

    TDQS

    A3.7/5.0

    Scored across 12 tools

    Disambiguation3/5

    The type-specific tools (project/pref/learning) are fairly distinct, but the generic memory_save, memory_search, and memory_list overlap with specialized equivalents like memory_project_save, memory_learning_search, and memory_project_list. The descriptions clarify the generic vs. specific distinction, but an agent still faces multiple paths to accomplish the same operation.

    Naming Consistency4/5

    Tool names consistently use a memory_ prefix and mostly follow a memory_<type>_<action> pattern. Minor inconsistencies exist: 'search' is used for learning where 'list' or 'get' might be expected, and the top-level memory_save/memory_search/memory_delete/memory_list deviate from the type-specific naming pattern.

    Tool Count4/5

    Twelve tools is reasonable for a memory system covering projects, preferences, and learnings. The count is slightly inflated by the generic memory_* tools that duplicate type-specific functionality, but overall the server remains well-scoped and navigable.

    Completeness4/5

    The server covers create, read, list, search, and delete across all memory types, either through type-specific or generic tools. Minor gaps exist—learning has no direct get-by-ID function, and deletion is only exposed through the generic memory_delete—but common workflows can be completed with existing tools.