Skip to main content
Glama
henrychong-ai

Neo4j Knowledge Graph MCP Server

by henrychong-ai
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Hybrid

Related Servers

Alternatives to Neo4j Knowledge Graph MCP Server

No user-submitted related servers found.

    Related Servers

    • Hebbrix MCP Server by Hebbrix

      Hebbrix MCP Serverofficial

      Hebbrix
      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

    • dejaview-mcp

      JakeC77
      A
      license
      Not graded
      quality
      C
      maintenance
      Provides persistent knowledge graph memory for AI agents, enabling them to store, recall, and query facts about people, projects, and relationships across sessions.
      MIT
    • Memsolus MCP Server by memsolus

      Memsolus MCP Serverofficial

      memsolus
      A
      license
      A
      quality
      D
      maintenance
      Provides persistent long-term memory for AI agents through semantic search and automated knowledge graph extraction. It enables agents to store, recall, and reason over facts, preferences, and relationships across multiple conversations and sessions.
      14
      12 npm
      MIT

    • Graphiti MCP Server

      chen9z
      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.
      -

    • novara-context

      ellingtonsp
      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
      -
    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.4/5.0

    Scored across 21 tools

    Disambiguation5/5

    Each tool targets a distinct operation on entities, observations, or relations. Batch variants are clearly differentiated, and query tools like search_nodes and semantic_search serve different purposes without ambiguity.

    Naming Consistency5/5

    All tool names follow a consistent verb_noun pattern (e.g., create_entities, delete_observations, get_relation_history). The '_batch' suffix is uniformly applied for optimized versions, and naming conventions are predictable throughout.

    Tool Count5/5

    With 21 tools covering CRUD, batch operations, time-travel queries, semantic search, and embeddings, the count is well-scoped for a knowledge graph server. Each tool serves a clear purpose without excess.

    Completeness4/5

    The tool surface covers core entity, relation, and observation lifecycle management. However, there is no explicit update_observations tool, and batch update for relations is limited to a single update_relation. These are minor gaps in an otherwise comprehensive set.

    Maintenance

    ActivityMaintained
    ResponsivenessUnresponsive

    Resources