Skip to main content
Glama

Related Servers

Alternatives to localmem-mcp

No user-submitted related servers found.

    Related Servers

    • A
      license
      Not graded
      quality
      B
      maintenance
      Enables AI agents to save, recall, and forget persistent memories stored entirely on the local machine in SQLite, using hybrid semantic and keyword search with on-device embeddings, plus spaces and profile context injection.
      MIT
    • 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.
      293 npm
      MIT
    • A
      license
      Not graded
      quality
      B
      maintenance
      Gives AI agents a private, on-device persistent memory using semantic search over stored facts, preferences, and decisions. It enables agents to remember information, recall it by meaning even without keyword overlap, delete memories, and list them by tag.
      3 npm
      4
      MIT
    • 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.
      -
    • A
      license
      Not graded
      quality
      B
      maintenance
      Gives AI agents a local-first, persistent memory backed by a single SQLite file, letting them save decisions, preferences, and facts, then recall them by meaning or keyword across sessions and projects. Exposes tools for loading pinned context, searching, adding, updating, listing, and deleting memories, so agents stop forgetting between sessions.
      15 npm
      1
      Apache 2.0

    TDQS

    A4.3/5.0

    Scored across 8 tools

    Disambiguation4/5

    Each tool targets a distinct operation (store, search, recall by id, list, update, delete, bulk delete, stats), and descriptions clearly separate search from recall and list. The only mild overlap is recall_memory's 'most recent memories' versus list_memories in chronological order, but the descriptions give enough guidance to choose correctly.

    Naming Consistency4/5

    Most tools follow a consistent verb_noun pattern (store_memory, search_memory, update_memory, forget_memory), and all names are lowercase snake_case. memory_stats breaks the pattern by using a noun_noun form rather than a verb like get_stats, and singular/plural alternates between memory and memories.

    Tool Count5/5

    Eight tools is well-scoped for a memory store: create, read (three retrieval modes), update, delete (single and bulk), and stats. Each tool earns its place without redundancy or bloat.

    Completeness5/5

    The surface covers the full memory lifecycle: store, retrieve by meaning/id/browse, update, delete, bulk prune, and inspect storage. There are no obvious dead ends; even bulk deletion is safely gated by requiring a filter.

    Maintenance

    ActivityStale
    ResponsivenessWithin a week