Neo4j is a graph database management system developed by Neo4j, Inc. It is a native graph database that stores data in nodes connected by relationships, providing an efficient way to query connected data.
Why this server?
Can be combined with Neo4j MCP server as mentioned in the tutorial for building a knowledge graph assistant
Why this server?
ATLAS has been completely rewritten to use Neo4j as its graph database, providing native relationship management, ACID-compliant transactions, and optimized queries for data integrity.
Why this server?
Uses Neo4j as the storage backend for the knowledge graph, providing unified graph storage and vector search capabilities.
Why this server?
Provides integration between Neo4j graph database and Claude Desktop, enabling graph database operations through natural language interactions. It allows executing Cypher queries, creating nodes and relationships, and performing complex graph operations via natural language commands.
Why this server?
Integrates with Neo4j database to store and query BloodHound data about Active Directory and Azure Active Directory environments, enabling natural language queries for security analysis without writing Cypher queries directly.
Why this server?
Uses Neo4j as the database backend for storing and querying the knowledge graph, supporting entity relationships and temporal data management
Why this server?
Mentioned in a tutorial about combining Tavily MCP with Neo4j MCP server to build a knowledge graph assistant
Why this server?
Provides access to Neo4j data by exposing it as relational SQL models through the CData JDBC Driver.
Why this server?
Allows SQL-based querying of Neo4j graph databases.
Why this server?
Enables SQL-based querying of Neo4J graph database data
Why this server?
Enables querying Neo4j graph database data through SQL-like syntax.
Why this server?
Listed as a supported data source for integration with the MCP server, allowing access to Neo4J data.
Why this server?
Provides a SQL interface for querying Neo4j graph databases.
Why this server?
Provides SQL interface for Neo4J graph databases.
Why this server?
Listed as a supported data source for accessing Neo4j graph databases.
Why this server?
Provides SQL-based access to Neo4J graph databases and nodes.
Why this server?
Enables access to Neo4J graph database data through SQL queries.
Why this server?
Provides tools for querying graph data from Neo4J databases through SQL-like interfaces.
Why this server?
Allows querying Neo4j graph database data through relational SQL models.
Why this server?
Listed as a supported data source for integration through the CData JDBC driver.
Why this server?
Allows querying Neo4j graph database data through SQL interfaces, making graph relationship information accessible via natural language.
Why this server?
Listed as a supported data source in the compatibility table, enabling access to Neo4j data.
Why this server?
Allows natural language to Cypher query conversion, knowledge graph memory storage, and exploration of graph databases with queries like 'What is in this graph?'
Why this server?
Allows querying Neo4J graph databases using SQL-like syntax, providing read-only access to nodes, relationships, and graph properties.
Why this server?
Optional integration for knowledge graph features when self-hosting Mem0, allowing creation and management of graph relationships between memory entities
Why this server?
Enables SQL-based access to Neo4J graph database nodes and relationships.
Why this server?
Listed as a supported data source for integration, allowing access to Neo4j data through the MCP server.
Why this server?
Provides access to Neo4J graph database data through relational SQL models.
Why this server?
Listed as a supported data source for integration through the CData JDBC Driver
Why this server?
Enables SQL-based access to Neo4J graph databases, translating SQL queries to graph operations.
Why this server?
Integrates with Neo4j graph database to provide graph-based context expansion and relationship-focused document retrieval capabilities
Why this server?
Uses Neo4j as the backend storage engine for the knowledge graph, providing powerful graph querying capabilities, high performance, and scalability for complex knowledge graph applications.
Why this server?
Stores and processes knowledge graphs of chat conversations, enabling relationship navigation between messages, concepts, and topics.
Why this server?
Connects to Neo4j database containing BloodHound Active Directory data, enabling natural language queries to analyze attack paths, security vulnerabilities, and domain relationships.
Why this server?
Provides a knowledge graph management interface for storing and retrieving information in Neo4j graph databases, with tools for creating entities and relationships, searching and filtering data, updating entities, and introspecting database schema.
Why this server?
Enables execution of Cypher queries against a Neo4j graph database, allowing management of graph database operations through the Model Context Protocol.
Why this server?
Planned future integration for expanded database options and more advanced relationship modeling for emails
Why this server?
Provides integration with Neo4j for storing and managing knowledge graph memory, allowing operations like creating entities, creating relations, adding observations, deleting entities, deleting observations, deleting relations, reading the graph, searching nodes, and opening specific nodes.