Skip to main content
Glama

Related Servers

Alternatives to amem

No user-submitted related servers found.

    Related Servers

    • A
      license
      Not graded
      quality
      D
      maintenance
      Gives AI coding agents persistent memory by storing observations, decisions, and learnings in a local SQLite database with vector search, full-text search, and a rules engine.
      4
      MIT
    • F
      license
      Not graded
      quality
      A
      maintenance
      Provides a local-first persistent memory layer that lets AI coding agents store, recall, and semantically search project-specific and cross-project knowledge across sessions, so context, decisions, and guidelines survive between conversations. Runs entirely on the user's machine with SQLite and no API keys, and optionally supports autonomous task-queue execution built on the same memory.
      -
    • F
      license
      Not graded
      quality
      A
      maintenance
      Provides a local-first, cross-session memory layer that lets AI coding agents store and semantically search per-project decisions, preferences, error patterns, and research alongside global guidelines. Also supports an optional task queue for autonomous execution, all backed by on-disk SQLite with no API keys or external calls.
      -
    • F
      license
      Not graded
      quality
      A
      maintenance
      Enables AI coding agents to store, search, and recall persistent project-specific and cross-project context — decisions, preferences, error patterns, and guidelines — from a local-first SQLite memory store with semantic search, so knowledge survives across sessions. An optional companion task server lets agents queue and autonomously execute work using that same memory.
      -
    • F
      license
      Not graded
      quality
      A
      maintenance
      Gives AI coding agents a local-first persistent memory they can read and write directly during sessions, storing decisions, preferences, error patterns, and guidelines in per-project and global SQLite stores. Enables semantic and keyword retrieval of relevant context across sessions so agents start work already knowing a codebase's conventions and history.
      -

    TDQS

    A3.9/5.0

    Scored across 16 tools

    Disambiguation4/5

    Tools are mostly distinct, but amem_context, amem_graph, amem_status, and amem_stats all touch the 'what does amem know' space, and amem_task_complete is explicitly documented as amem_task_update with status=done. Descriptions do the heavy lifting to draw boundaries (e.g. amem_recipe as a routing decision aid), so an attentive agent can pick correctly, but the overlaps require reading.

    Naming Consistency4/5

    Every tool is prefixed with a consistent amem_ namespace, grouped sensibly (skill_*, task_*). The pattern mixes bare-noun names (amem_repos, amem_stats, amem_graph, amem_status) with verb_noun names (amem_task_add, amem_skill_save, amem_remember), so it deviates slightly from a single convention but remains readable and predictable within subclusters.

    Tool Count4/5

    16 tools is at the upper edge, but the server spans four coherent subdomains (memory, skills, tasks, stats) so each tool carries weight. There is some redundancy (amem_stats vs amem_usage_report, amem_task_complete vs amem_task_update), but nothing gratuitous.

    Completeness4/5

    Core lifecycle is well covered: memory (remember/context/graph/supersede), skills (save/list/view), tasks (add/list/update/complete), plus reporting. Minor gaps exist—no delete/rename for skills, no delete for tasks, and no explicit fact-delete beyond supersession—but these are partly mitigated by the completion/supersede semantics.

    Maintenance

    ActivityMaintained
    ResponsivenessLimited data