Skip to main content
Glama

Related Servers

Alternatives to MemVault

No user-submitted related servers found.

    Related Servers

    • A
      license
      Not graded
      quality
      B
      maintenance
      A self-hosted memory server that gives AI agents a shared, persistent second brain, enabling verbatim storage, hybrid semantic/keyword retrieval, and a synthesized wiki layer through MCP tools.
      2
      MIT
    • F
      license
      Not graded
      quality
      A
      maintenance
      A local-first MCP memory server that lets AI coding agents store, search, and recall project-specific and cross-project knowledge, so architecture decisions, preferences, error patterns, and coding guidelines persist across sessions. It also exposes optional task-queue tools for handing off autonomous work that draws on the same stored context.
      -
    • A
      license
      Not graded
      quality
      D
      maintenance
      MCP server that enables persistent, hybrid, local memory for LLM agents, with vector + BM25 search, knowledge graph, and policy-driven retention, providing token-budgeted context injection for AI assistants.
      MIT
    • A
      license
      Not graded
      quality
      B
      maintenance
      Provides AI agents and teams with self-hosted adaptive memory, combining hybrid search and a self-improving neural memory graph to enable precise recall and serendipitous discovery across MCP-compatible clients.
      13
      Apache 2.0
    • A
      license
      Not graded
      quality
      B
      maintenance
      Provides a self-hosted shared memory service that lets AI agents capture and recall durable facts, decisions, and context across multiple tools and MCP-capable clients.
      3
      MIT
    • A
      license
      Not graded
      quality
      B
      maintenance
      A vendor-independent memory layer MCP server that enables multiple LLMs and AI agents to share and persist personal memories, knowledge, and context across sessions, with support for full-text search and tagging.
      ISC

    TDQS

    A3.9/5.0

    Scored across 21 tools

    Disambiguation3/5

    Most tools have a distinct role, and the descriptions explicitly clarify near-neighbors such as save_memory vs extract_memories, delete_memory vs forget_memory, and record_outcome vs infer_outcome. However, multiple pairs overlap by design, including propose_memory_edit vs review_memory edit, the two compliance/effectiveness reports, and the three maintenance tools, so an agent must read carefully to select correctly.

    Naming Consistency4/5

    The set mostly follows a verb_noun pattern: save_memory, search_memory, delete_memory, get_compliance_report, import_skills, and run_decay. The main deviation is session_start, which reverses the order and mildly breaks the otherwise consistent convention.

    Tool Count3/5

    At 21 tools, the surface is heavy for a memory server, though the domain is broad and includes lifecycle, extraction, review, evidence, compliance, outcomes, skills, and maintenance. Several adjacent reporting and maintenance tools could likely be consolidated without losing core capability.

    Completeness4/5

    The set covers the main memory lifecycle: save/search/delete/forget, review and edit proposals, evidence, session injection, outcomes, compliance, and maintenance. Minor gaps remain, notably restore being CLI-only and some list/report operations lacking pagination or fuller management surfaces.

    Maintenance

    ActivityActive
    ResponsivenessNo recent community issues