Knowledge Graph Memory Server
Related Servers
Alternatives to Knowledge Graph Memory Server
No user-submitted related servers found.
Related Servers
- AlicenseAqualityDmaintenanceAn improved implementation of persistent memory using a local knowledge graph with a customizable --memory-path. This lets Claude remember information about the user across chats.10315 npm890MIT
- AlicenseBqualityAmaintenanceA basic implementation of persistent memory using a local knowledge graph. This lets Claude remember information about the user across chats.9163,576 npm90,629-
- AlicenseNot gradedqualityCmaintenanceA 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
- FlicenseAqualityDmaintenanceEnables Claude to maintain persistent memory across conversations using a local knowledge graph with fuzzy search capabilities, allowing it to remember and recall information about users, relationships, and context.9-
- FlicenseNot gradedqualityDmaintenanceEnables Claude to remember information about users across conversations by storing and retrieving data as entities, relations, and observations in a persistent local knowledge graph.163,576 npm-
- AlicenseNot gradedqualityDmaintenanceEnables Claude to remember information about users across chats using a persistent local knowledge graph that stores entities, relationships, and observations.163,576 npm-
TDQS
Scored across 9 tools
Most tools have distinct purposes, but 'open_nodes' and 'search_nodes' could cause some confusion as both involve accessing nodes, though 'open_nodes' seems to retrieve specific nodes by name while 'search_nodes' queries based on criteria. The CRUD operations for entities, relations, and observations are clearly separated, reducing major overlap.
All tool names follow a consistent verb_noun pattern with snake_case, such as 'add_observations', 'create_entities', and 'delete_relations'. This predictability makes it easy for agents to understand and use the tool set without confusion from mixed conventions.
With 9 tools, the server is well-scoped for managing a knowledge graph, covering core operations like creation, deletion, reading, and searching. This count is appropriate as it provides comprehensive functionality without being overwhelming or too sparse for the domain.
The tool set offers strong coverage with CRUD operations for entities, relations, and observations, plus reading and searching capabilities. A minor gap is the lack of update tools for entities or relations, which might require workarounds like delete-and-recreate, but core workflows are well-supported.