mcp-neo4j -sse

This MCP server provides a Neo4j-backed Model Context Protocol interface over Server-Sent Events (SSE) or STDIO transport. It exposes three core tools for interacting with a Neo4j graph: read-neo4j-cypher to execute read queries and return results, write-neo4j-cypher to perform updates and return a summary of changes, and get-neo4j-schema to inspect the graph schema including node types, attributes, and relationships. A built-in demonstration prompt mcp-demo guides users through common database operations and can generate sample schemas and data. To use SSE (the default transport), run the server and connect the client to the provided SSE endpoint; for STDIO, run in stdio mode and interact via standard input/output streams. Start by selecting the target database and then issue Cypher queries through the read or write tools to explore or modify your graph. The schema tool helps you discover the graph’s structure, which is especially useful when designing queries or data models against the remote Neo4j instance.

Prerequisites:

• Python 3.12+ installed on your system
• Neo4j database running and accessible (bolt connection endpoint reachable)
• Internet access to install Python dependencies (pip)

Installation steps:

1. Clone the repository: git clone https://github.com/dsimile/mcp-neo4j-server-sse.git cd mcp-neo4j-server-sse

2. Install Python dependencies: python -m venv venv source venv/bin/activate # on Windows use venv\Scripts\activate pip install -r requirements.txt

3. Run the server (SSE mode by default): uv run src/mcp-neo4j-cypher/neo4j_server_remote.py
   --url bolt://localhost:7687
   --username neo4j
   --password neo4j123
   --database neo4j

4. Optional: run in STDIO mode for local development/testing: uv run src/mcp-neo4j-cypher/neo4j_server_remote.py
   --url bolt://localhost:7687
   --username neo4j
   --password neo4j123
   --database neo4j
   --mode stdio

5. If you’re using the released package, update cline_mcp_settings.json with the appropriate server entry.

Tips and notes:

• Ensure Neo4j is running and accessible at the provided Bolt URL (default bolt://localhost:7687) with the credentials you supply.
• SSE is the default transport; switch to STDIO by using the --mode stdio option or the corresponding configuration if you need local, interactive stream IO.
• The example configuration uses a public host/port; adapt to your deployment (firewalls, TLS, and authentication as needed).
• The get-neo4j-schema tool returns a list of node labels with their attributes and relationships, which is helpful for dynamic query building and UI generation.
• For production, consider securing credentials and restricting access to the MCP endpoints.