Skip to main content
Glama
T1nker-1220

Knowledge Graph Memory Server

by T1nker-1220
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Hybrid

Related Servers

Alternatives to Knowledge Graph Memory Server

No user-submitted related servers found.

    Related Servers

    • Knowledge Graph Memory Server

      guinacio
      A
      license
      Not graded
      quality
      C
      maintenance
      A persistent memory system using a local knowledge graph that enables Claude to remember information about users across chats, with advanced search, graph traversal, and filtering capabilities for entities, relations, and observations.
      MIT

    • Memento

      scrypster
      A
      license
      Not graded
      quality
      C
      maintenance
      Provides persistent memory for AI tools by building a local knowledge graph from conversations, enabling cross-session recall and context awareness without cloud dependencies.
      9
      MIT

    • recall

      andrewhomeyer
      A
      license
      A
      quality
      D
      maintenance
      Gives AI assistants a persistent memory across conversations, allowing them to remember user preferences, notes, and facts between chats.
      6
      8 npm
      MIT

    • AGI MCP Server

      randyandrade
      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
      -
    Deploy Server
    One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

    TDQS

    B3.3/5.0

    Scored across 13 tools

    Disambiguation4/5

    Most tools have distinct purposes, but some overlap exists: 'open_nodes' and 'search_nodes' both involve accessing nodes, which could cause confusion. However, descriptions clarify that 'open_nodes' targets specific names while 'search_nodes' uses queries, reducing ambiguity. Other tools like 'add_observations' vs. 'create_entities' are clearly differentiated.

    Naming Consistency5/5

    Tool names follow a consistent verb_noun pattern throughout, such as 'add_observations', 'create_entities', and 'delete_relations'. All tools use snake_case and clear verbs, making them predictable and easy to understand. There are no deviations in naming conventions.

    Tool Count5/5

    With 13 tools, the count is well-scoped for a knowledge graph memory server, covering operations like CRUD for entities, relations, observations, and lessons. Each tool appears to serve a specific function without redundancy, fitting the domain's complexity appropriately.

    Completeness4/5

    The tool set provides comprehensive coverage for knowledge graph management, including creation, reading, updating, and deletion of entities, relations, observations, and lessons. A minor gap is the lack of an 'update_entities' or 'update_relations' tool for modifying existing content, but agents can work around this by deleting and recreating. Core workflows are well-supported.

    Maintenance

    ActivityInactive
    ResponsivenessUnresponsive

    Resources