Skip to main content
Glama

Related Servers

Alternatives to nMEMORY

No user-submitted related servers found.

    Related Servers

    • F
      license
      Not graded
      quality
      A
      maintenance
      Local-first memory for AI agents with evidence-backed recall, deterministic trust verdicts, self-inspection, and a tamper-evident audit history.
      3
      -
    • F
      license
      B
      quality
      A
      maintenance
      Memory for LLM agents: a local graph where the agent keeps decisions, tasks, hypotheses and reasoning between sessions, and gets a summary of what is open and overdue on every return to a project. Works with Claude Code, Codex, Cursor and opencode. Single Rust binary, no embedding model or LLM calls. Source-available (BSL 1.1), commercial use permitted.
      71
      38
      -
    • A
      license
      A
      quality
      A
      maintenance
      Embedded, local-first agent memory: facts extracted into a per-namespace SQLite file (vec0 + FTS5) with hybrid retrieval and point-in-time (time-travel) queries. ADD-only history over stdio — no server process, no cloud dependency.
      7
      42
      Apache 2.0
    • A
      license
      A
      quality
      B
      maintenance
      Local-first, source-traceable memory for AI agents — no LLM at ingest, $0 per message, zero data egress. Gives Claude Code, Cursor, and any MCP client one shared persistent memory with semantic recall, belief revision, selective forgetting, and a provenance guard that blocks acting on stale or unconfirmed memories.
      23
      21 PyPI
      14
      MIT
    • F
      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
      -

    TDQS

    A4.2/5.0

    Scored across 22 tools

    Disambiguation4/5

    Tools have distinct purposes, but memory_ingest and memory_classify both can persist classification sidecars, causing minor ambiguity. Overall, descriptions are thorough and roles are clear.

    Naming Consistency4/5

    All tools use 'memory_' prefix with snake_case. While not strictly verb_noun (e.g., outcome, vector, visual are nouns/adjectives), the pattern is consistent and predictable.

    Tool Count5/5

    22 tools cover a comprehensive memory management lifecycle including CRUD, import/export, session management, relations, and advisory features. Each tool earns its place without bloat.

    Completeness4/5

    Covers most operations but lacks a direct content-update tool; modification requires forget+re-ingest. Metadata updates exist via classify, pin, etc. Minor gap for full CRUD parity.

    Maintenance

    ActivityStale
    ResponsivenessNo issues