mcp-neo4j

MCP Neo4j Server provides a bridge between a Neo4j graph database and Claude Desktop, enabling natural language interactions to perform graph operations. It exposes tools for executing Cypher queries, creating nodes, and establishing relationships, all through simple commands or natural language prompts. By configuring the environment variables, you can point the server to your Neo4j instance and optionally target a specific database in Neo4j Enterprise Edition. This makes it easy to perform reads, creates, updates, and deletes directly from Claude without writing Cypher manually.

Within Claude Desktop, you’ll access the available tools like execute_query, create_node, and create_relationship. Use execute_query to run arbitrary Cypher statements (with parameter support to prevent injection). Use create_node to add a new node with labels and properties, and use create_relationship to connect existing nodes with a relationship type and properties. The server is designed to handle typical graph operations and returns structured results you can inspect or feed into subsequent steps in your workflow.

Prerequisites:

• Node.js and npm installed on your machine
• Access to a Neo4j instance (local or remote) with appropriate credentials

Installation steps:

1. Install via Smithery (recommended for Claude Desktop users):

npx -y @smithery/cli install @alanse/mcp-neo4j-server --client claude

2. For development or local testing:

git clone https://github.com/da-okazaki/mcp-neo4j-server.git
cd mcp-neo4j-server
npm install

3. Build the project (if applicable):

npm run build

4. Run directly with npx (as shown in Quick Start):

npx @alanse/mcp-neo4j-server

Prerequisites summary:

• Node.js and npm, access to the internet for package installation
• A running Neo4j instance and credentials to connect

Environment variables:

• NEO4J_URI (default bolt://localhost:7687)
• NEO4J_USERNAME (default neo4j)
• NEO4J_PASSWORD (required for authentication)
• NEO4J_DATABASE (default neo4j; can target a specific database in Neo4j Enterprise) Common issues:
• Ensure the Neo4j service is reachable from the host running the MCP server
• Double-check password and user permissions; passwordless access is not supported
• When targeting an Enterprise database, set NEO4J_DATABASE to the desired database name
• If you encounter connection errors, verify TLS/SSL settings and URI format for your Neo4j deployment Debug tips:
• Enable verbose logs in your environment to inspect Cypher query execution and responses