Skip to main content
Glama

Related Servers

Alternatives to MCP Memory Server

No user-submitted related servers found.

    Related Servers

    • A
      license
      B
      quality
      D
      maintenance
      MCP server that provides cross-session persistent memory for AI coding assistants using local vector database and semantic search, enabling automatic recall of project context, issues, and tasks.
      9
      25 PyPI
      91
      Apache 2.0
    • A
      license
      Not graded
      quality
      C
      maintenance
      Provides local vector-based semantic memory storage for AI assistants to persist context and decisions across sessions using local embeddings and LanceDB. It enables private semantic search and session handoff capabilities to maintain long-term project context.
      81 npm
      5
      MIT
    • A
      license
      Not graded
      quality
      C
      maintenance
      Provides a local, persistent long-term memory service for MCP-compatible AI agents, enabling them to store, search, and recall information across sessions.
      1
      GPL 3.0
    • A
      license
      A
      quality
      C
      maintenance
      A local, fully-offline MCP memory server that enables persistent storage and retrieval of information using SQLite with both keyword and semantic vector search capabilities.
      10
      19 npm
      13
      MIT
    • A
      license
      Not graded
      quality
      D
      maintenance
      A fully local, self-hosted memory server for MCP clients (Claude Code, Cursor, etc.) that provides persistent memory storage with semantic search, using local embeddings and a local Qdrant vector store.
      MIT
    • A
      license
      A
      quality
      B
      maintenance
      A local-first persistent memory server for AI coding agents, enabling project context to be shared across different MCP clients. It stores curated memories, task states, decisions, and handoffs as plain files under ~/.agent-memory.
      16
      3 npm
      MIT

    TDQS

    B3.4/5.0

    Scored across 6 tools

    Disambiguation5/5

    Each tool has a clearly distinct purpose: add, delete by source, list sources, reset, search, and stats. No overlapping functionality between them.

    Naming Consistency5/5

    All tools follow a consistent verb_noun pattern with 'memory_' prefix, e.g., memory_add, memory_delete_source. No mixing of conventions.

    Tool Count5/5

    6 tools is well-scoped for a memory management server covering core CRUD-like operations plus search and stats. Not too few nor too many.

    Completeness4/5

    Covers add, delete by source, list sources, search, and stats. Lacks individual memory item update or delete, but for vector stores these are less critical. Minor gap.

    Maintenance

    ActivityInactive
    ResponsivenessNo issues