Skip to main content
Glama

Related Servers

Alternatives to polypack-mcp

No user-submitted related servers found.

    Related Servers

    • F
      license
      B
      quality
      D
      maintenance
      Enables persistent memory for AI systems by providing tools for episodic, semantic, and procedural data storage through a vector-and-graph-enhanced database. It allows models to maintain long-term continuity using similarity search, thematic clustering, and identity tracking.
      24
      1
      -
    • A
      license
      B
      quality
      D
      maintenance
      Provides AI with persistent memory management including short-term memory (FIFO queue), long-term memory (graph-based storage with associations), and thought process management with multiple cognitive modes for continuous learning and reasoning.
      24
      17 npm
      3
      MIT
    • F
      license
      A
      quality
      D
      maintenance
      Provides persistent memory, identity, and context for Claude sessions through a memory graph, enabling recall, storage, and relationship management of entities and decisions.
      8
      -
    • A
      license
      A
      quality
      C
      maintenance
      Provides persistent memory capabilities for AI assistants, enabling storage, recall, and analysis of information across conversations with intelligent memory management.
      25
      28 npm
      MIT
    • A
      license
      A
      quality
      A
      maintenance
      Provides long-term memory and a temporal knowledge graph for AI agents, enabling persistent memory and reasoning across sessions.
      33
      1
      MIT
    • A
      license
      A
      quality
      D
      maintenance
      Provides persistent memory storage with advanced features like tagging, content search, and expiration settings. It enables users to create directed links between stored memories to build structured relationships and knowledge graphs.
      12
      8 npm
      ISC

    TDQS

    A3.6/5.0

    Scored across 18 tools

    Disambiguation5/5

    Each tool has a clearly distinct role: store, link, retrieve, suppress, supersede, consolidate, batch, and graph diagnostics are all explicitly separated. Even near-overlapping pairs like memory_store/memory_store_with_link and memory_link/graph_query are carefully disambiguated in their descriptions.

    Naming Consistency4/5

    The memory_* prefix provides a strong, predictable namespace, and most tools follow a clear verb-like pattern: store, update, delete, recall, link, unlink. Minor deviations like memory_context, memory_thread, and memory_feedback are noun-oriented, and graph_query breaks the memory_ prefix pattern, so it is not perfectly uniform.

    Tool Count3/5

    At 18 tools, the server is above the ideal 3-15 range and feels somewhat heavy. However, the batch variants, store-with-link convenience, and full memory lifecycle tools are mostly justified by the breadth of the domain.

    Completeness5/5

    The tool surface covers memory CRUD, batch operations, graph edge management, retrieval modes, lifecycle transitions, feedback, and context assembly. There are no obvious dead ends or missing operations for a project-memory and relationship-graph server.

    Maintenance

    ActivityMaintained
    ResponsivenessNo issues