Skip to main content
Glama

Related Servers

Alternatives to Memory MCP

No user-submitted related servers found.

    Related Servers

    • A
      license
      Not graded
      quality
      D
      maintenance
      Provides AI coding assistants with persistent project memory to retain architectural decisions, code patterns, and domain knowledge across sessions. It stores data locally in a SQLite database, allowing agents to remember, recall, and manage project-specific context using full-text search.
      4 npm
      Apache 2.0
    • -
      license
      Not graded
      quality
      Not graded
      maintenance
      Provides persistent local memory functionality for AI assistants, enabling them to store, retrieve, and search contextual information across conversations with SQLite-based full-text search. All data stays private on your machine while dramatically improving context retention and personalized assistance.
      3
      -
    • A
      license
      Not graded
      quality
      D
      maintenance
      Provides AI assistants with persistent memory across sessions using local SQLite and keyword search, allowing storage and retrieval of user preferences, project context, and decisions.
      27 npm
      9
      MIT
    • F
      license
      Not graded
      quality
      A
      maintenance
      Enables AI coding agents to read and write persistent memory directly during sessions, storing decisions, preferences, error patterns, research, and cross-project guidelines in local SQLite databases. Supports semantic search so relevant project and global context can be recalled by meaning, fully offline and without API keys.
      -
    • A
      license
      A
      quality
      B
      maintenance
      Provides AI coding assistants with persistent memory storage using a local SQLite database. Enables tools to remember project details, notes, and relationships across sessions to maintain context and reduce repetitive explanations.
      17
      4
      MIT

    TDQS

    A3.7/5.0

    Scored across 8 tools

    Disambiguation5/5

    Each tool has a clearly distinct purpose with no overlap: delete_memory removes a memory, get_session retrieves a session's conversation, list_memories lists memories, list_sessions lists sessions, refresh_sessions indexes new sessions, save_memory stores a memory, search_memory searches memories, and search_sessions searches sessions. The descriptions reinforce these distinct roles, making misselection unlikely.

    Naming Consistency5/5

    All tools follow a consistent verb_noun pattern using snake_case: delete_memory, get_session, list_memories, list_sessions, refresh_sessions, save_memory, search_memory, and search_sessions. This predictable naming scheme enhances readability and usability across the toolset.

    Tool Count5/5

    With 8 tools, the server is well-scoped for managing memories and sessions. Each tool serves a clear purpose, such as CRUD operations for memories (save, list, search, delete) and sessions (list, get, search, refresh), avoiding bloat while covering essential functionality for the domain.

    Completeness4/5

    The toolset provides strong coverage for memory and session management, including create (save_memory), read (list_memories, get_session), delete (delete_memory), and search (search_memory, search_sessions). A minor gap exists in updating memories or sessions, but agents can work around this by deleting and re-saving, and the refresh_sessions tool handles session updates indirectly.

    Maintenance

    ActivityInactive
    ResponsivenessOutdated data