Skip to main content
Glama
yodakeisuke

Knowledge Graph Memory Server

by yodakeisuke
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Hybrid

Related Servers

Alternatives to Knowledge Graph Memory Server

No user-submitted related servers found.

    Related Servers

    • my-memory-mcp

      moontmsai
      F
      license
      Not graded
      quality
      D
      maintenance
      A MCP server that provides persistent memory for AI assistants, storing personal information, relationships, and observations to enable personalized and contextual conversations.
      4
      -

    • memcurve

      nathaniel-gordon
      A
      license
      A
      quality
      B
      maintenance
      This MCP server enables AI assistants to maintain persistent, human-like memory by storing and recalling information that naturally fades unless reinforced through use, with long-term promotion for frequently accessed memories.
      17
      AGPL 3.0

    • Simple Memory MCP Server

      AojdevStudio
      F
      license
      A
      quality
      D
      maintenance
      A lightweight MCP server that provides persistent knowledge graph storage for AI assistants, enabling memory across sessions through entity-relationship storage with JSON file persistence.
      10
      1
      -

    • Graph-Mem MCP

      Sathvik-1007
      A
      license
      Not graded
      quality
      A
      maintenance
      A universal MCP server providing persistent, structured memory through a knowledge graph with graph storage, semantic vector search, and multi-hop traversal for AI agents and IDEs.
      1
      MIT

    • CogniRepo

      ashlesh-t
      A
      license
      B
      quality
      A
      maintenance
      MCP server providing persistent memory and context for AI tools, including semantic memory, knowledge graph, and session history to avoid starting from scratch in every conversation.
      35
      14
      MIT
    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

    A3.5/5.0

    Scored across 9 tools

    Disambiguation5/5

    Each tool has a clearly distinct purpose with no ambiguity: create/delete operations target specific components (entities, relations, observations), while read/search/open handle different access patterns. The descriptions reinforce these distinctions, making misselection unlikely.

    Naming Consistency5/5

    All tools follow a consistent verb_noun pattern with snake_case throughout (e.g., add_observations, delete_relations, search_nodes). The naming is predictable and readable, with no deviations in style or convention.

    Tool Count5/5

    With 9 tools, the server is well-scoped for a knowledge graph memory system. Each tool earns its place by covering essential CRUD operations and access methods, avoiding both bloat and insufficiency for the domain.

    Completeness4/5

    The toolset provides strong coverage for core knowledge graph operations, including creation, deletion, reading, and searching. A minor gap exists in update capabilities for entities or observations, which agents might need to work around by deleting and recreating, but overall workflows are well-supported.

    Maintenance

    ActivityInactive
    ResponsivenessNo issues

    Resources