Skip to main content
Glama
memory_plus

memory_plus

Related Servers

Alternatives to memory_plus

No user-submitted related servers found.

    Related Servers

    • A
      license
      Not graded
      quality
      A
      maintenance
      Enables AI coding agents to keep persistent, Zettelkasten-style memory by saving and recalling atomic markdown knowledge cards with bidirectional links across sessions. Supports searching, reading, writing, linking, organizing, and git-syncing those cards through a set of MCP tools, with no vector database required.
      15 npm
      ISC
    • A
      license
      A
      quality
      A
      maintenance
      Provides persistent, graph-based memory for AI agents via MCP, enabling semantic search, wikilink traversal, reminders, and injection protection.
      9
      35
      Apache 2.0
    • A
      license
      Not graded
      quality
      A
      maintenance
      Enables AI coding agents to persistently store, recall, and manage atomic markdown knowledge cards with bidirectional links across sessions. It provides MCP tools for searching, reading, writing, linking, archiving, organizing, and syncing memory via git without a vector database.
      15 npm
      ISC
    • A
      license
      Not graded
      quality
      B
      maintenance
      Enables AI assistants to store, retrieve, and manage persistent memories locally via an MCP server with hybrid vector and keyword search, plus tools for memory CRUD, search, backup, and import.
      MIT
    • 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

    TDQS

    A3.5/5.0

    Scored across 6 tools

    Disambiguation5/5

    Each tool has a clearly distinct operation on memory: audit (log query), forget (delete), list (list all), recall (keyword search), stats (statistics), store (create). No overlap in purpose.

    Naming Consistency5/5

    All tools follow the pattern 'svm_<verb>', using consistent snake_case and lowercase verbs. The naming is uniform and predictable.

    Tool Count5/5

    Six tools cover the essential memory operations (CRUD plus audit and stats) without being excessive or too sparse. The scope is well-balanced for a memory management server.

    Completeness4/5

    Core operations create (store), read (recall, list), and delete (forget) are present. Audit and stats provide additional oversight. An explicit update operation is missing, but store may serve as upsert, so gap is minor.

    Maintenance

    ActivityInactive
    ResponsivenessNo recent community issues