Skip to main content
Glama
MihaiBuilds

Memory Vault

by MihaiBuilds

Related Servers

Alternatives to Memory Vault

No user-submitted related servers found.

    Related Servers

    • A
      license
      Not graded
      quality
      D
      maintenance
      An MCP server that gives Claude persistent memory by storing conversation context, entities, and enabling semantic search across sessions.
      9 npm
      1
      MIT
    • A
      license
      Not graded
      quality
      A
      maintenance
      An MCP server that provides persistent memory capabilities for Claude, offering tiered memory architecture with semantic search, memory consolidation, and integration with the Claude desktop application.
      38 npm
      69
      MIT
    • A
      license
      Not graded
      quality
      A
      maintenance
      An MCP server that provides Claude agents with a comprehensive memory management system for storing and retrieving episodic, semantic, and procedural knowledge. It enables working memory persistence, knowledge graph integration, and interaction stream capture to enhance agent learning and context retrieval.
      22 npm
      MIT
    • F
      license
      Not graded
      quality
      D
      maintenance
      MCP server that provides persistent long-term memory for Claude Code, enabling storage, search, and retrieval of project knowledge across sessions.
      -
    • A
      license
      Not graded
      quality
      A
      maintenance
      MCP server providing persistent, searchable memory management for AI workflows, enabling Claude Code to store, retrieve, and organize context through CRUD operations and knowledge tools.
      MIT
    • A
      license
      Not graded
      quality
      C
      maintenance
      A persistent memory MCP server for Claude Code that enables long-term recall across sessions via hybrid search, code intelligence, and tools for reading/writing memory.
      32 npm
      1
      MIT

    TDQS

    A4.4/5.0

    Scored across 6 tools

    Disambiguation5/5

    Each tool has a clearly distinct purpose: recall for searching, remember for storing, forget for soft-deleting, purge_forgotten for permanent cleanup, move_memory for relocating, and memory_status for health checks. There is no meaningful overlap or ambiguity between any pair of tools.

    Naming Consistency4/5

    Most tool names follow a verb-first pattern (recall, remember, forget, purge_forgotten, move_memory), which is predictable and readable. memory_status breaks the pattern slightly by being noun-first, but the naming is still clear and consistent in style overall.

    Tool Count5/5

    Six tools is a well-scoped size for a memory vault server, covering querying, writing, deletion, recovery/cleanup, organization, and monitoring without redundancy. Each tool earns its place and there is no sense of bloat or thinness.

    Completeness4/5

    The core memory lifecycle is well covered: store, search, soft-delete, permanent purge, move between spaces, and inspect status. Minor gaps exist, such as updating or editing an existing memory's content and creating spaces directly through the server, but these are workable limitations rather than fatal dead ends.

    Maintenance

    ActivityActive
    ResponsivenessResponsive