Skip to main content
Glama

Related Servers

Alternatives to memento-mcp

No user-submitted related servers found.

    Related Servers

    • F
      license
      Not graded
      quality
      D
      maintenance
      Enables AI assistants to build and query temporally-aware knowledge graphs from conversations and data, maintaining persistent memory of entities, relationships, and facts across interactions.
      -
    • F
      license
      Not graded
      quality
      D
      maintenance
      Enables AI agents to build and query a persistent knowledge graph with entities, relationships, and observations. Features a core index system that ensures critical information is always accessible across all memory operations.
      1
      -
    • A
      license
      Not graded
      quality
      D
      maintenance
      Persistent memory and knowledge graph server that fuses keyword, vector, and graph search into a single query, enabling AI assistants to recall typed entities and relationships across sessions.
      MIT
    • F
      license
      Not graded
      quality
      F
      maintenance
      Provides AI agents with persistent memory and knowledge management through a comprehensive knowledge graph platform. Enables storing, searching, and managing entities, relationships, and observations with advanced features like trending analysis and smart ranking.
      3
      -
    • 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
      52 PyPI
      2
      MIT

    TDQS

    B3.4/5.0

    Scored across 17 tools

    Disambiguation5/5

    Each tool has a clearly distinct purpose: CRUD operations for entities, relations, and observations are separated, and specialized tools for history, embeddings, and time-specific queries do not overlap. No ambiguity between tool functions.

    Naming Consistency5/5

    All tool names follow a consistent verb_noun pattern (e.g., create_entities, delete_observations, get_entity_history). The naming is uniform and predictable, aiding agent selection.

    Tool Count4/5

    With 17 tools, the count is slightly above the ideal 3-15 range but still well-scoped for a knowledge graph system. Each tool addresses a specific need, though a few could potentially be consolidated.

    Completeness3/5

    The tool surface covers most CRUD operations but lacks an update_entity tool and a dedicated get_entity (though open_nodes and read_graph partially fill this). Missing update for observations. These gaps may cause some workflow interruptions.

    Maintenance

    ActivityInactive
    ResponsivenessUnresponsive