Skip to main content
Glama

Related Servers

Alternatives to EvoMem-MCP

No user-submitted related servers found.

    Related Servers

    • A
      license
      B
      quality
      A
      maintenance
      Provides AI agents with a persistent long-term memory over a single SQLite file, letting them write, screen, consolidate, and recall notes across sessions without any generative LLM in the loop. Recall judges relevance, follows links between notes, and signals when memory is insufficient, so agents get one to three useful facts per question instead of a generic top-k list.
      11
      39 PyPI
      2
      MIT
    • A
      license
      Not graded
      quality
      A
      maintenance
      Local memory for AI agents in one SQLite file on your own machine. Facts carry a validity window and a confidence score, so an outdated one is superseded and downweighted rather than deleted, and retrieval fuses BM25, vector similarity and a knowledge graph.
      2
      Business Source 1.1
    • A
      license
      Not graded
      quality
      C
      maintenance
      Provides a decision memory layer for codebases, enabling AI agents to search, retrieve, and record business decisions with metadata filters and full-text search.
      1
      MIT
    • A
      license
      Not graded
      quality
      B
      maintenance
      Enables AI agents to store and recall durable facts, decisions, and lessons over MCP using hybrid semantic and keyword search, typed memories, graph relations, sessions, and time-travel queries. Runs locally with no server process or API key, persisting everything to files that both agents and a CLI can share.
      14 npm
      MIT
    • A
      license
      Not graded
      quality
      B
      maintenance
      Enables an AI agent to recall past approvals, edits and rejections that are similar to the task at hand before drafting, and to record each new decision along with the human's reason. Memory lives in a local Postgres (PGlite + pgvector) store, so corrections carry across sessions without hosting anything.
      1
      MIT
    • A
      license
      A
      quality
      A
      maintenance
      Agent memory for facts that change. When a user corrects something, Recall replaces the old fact, tells the agent what it replaced, and keeps the old value in a history. Ask what was believed on any date, see every change to a fact, or diff two dates. Runs locally on polign_db, Postgres with pgvector, MongoDB, or Qdrant. Apache 2.0.
      14
      5
      4
      Apache 2.0

    TDQS

    B3.4/5.0

    Scored across 5 tools

    Disambiguation5/5

    Each tool has a clearly distinct purpose: remember writes, recall searches by free-text, get_node fetches by id, forget removes, and stats reports storage. The recall/get_node boundary is well explained (query-based with history chain vs single-id lookup), leaving no realistic misselection.

    Naming Consistency4/5

    All names are lowercase snake_case and the core operations use bare verbs (remember, recall, forget), but get_node mixes verb_noun and stats is a bare noun. The style is slightly mixed yet entirely predictable and readable.

    Tool Count5/5

    Five tools is well-scoped for a memory server: one per core operation (write, search, read, delete, inspect). Nothing appears redundant or missing at this size.

    Completeness4/5

    The surface covers the full memory lifecycle—create, query, read, soft-delete/purge, and stats—with updates modeled through supersedes chains rather than a separate update tool. Minor gaps remain, such as no listing/enumeration or relation-traversal operation, but agents can work around these via recall and get_node.

    Maintenance

    ActivityMaintained
    ResponsivenessNo issues