Neo4j MCP Server
This server does not currently have a deployable release on Glama. Follow the repository's setup instructions to install and configure it for your MCP client, including any required credentials and local dependencies.
Neo4j MCP Server
A Model Context Protocol server that exposes a Neo4j graph database as tools an AI agent can call. It serves the MCP protocol over HTTP, so it can be reached by any MCP client — including a Databricks Unity Catalog MCP connection.
Tools
Tool | Purpose |
| Run a read-only Cypher query ( |
| Run a write Cypher query ( |
| Return the graph schema — node labels, relationship types, properties, and connection patterns. Call this first so queries use the right labels/relationships instead of guessing. |
Related MCP server: Neo4j MCP Server
Requirements
Node.js 20+
A Neo4j database (e.g. Neo4j Aura)
Setup
npm install
cp .env.example .env # then fill in your Neo4j credentials + a secret token
npm run build
npm start # serves on http://localhost:3000Endpoints:
GET /health— liveness checkPOST /mcp— the MCP endpoint (requiresAuthorization: Bearer <MCP_SECRET_TOKEN>)
Optional: npm run seed loads sample data into Neo4j.
Environment
See .env.example. Copy it to .env and fill in:
Variable | Description |
| Bolt/Aura connection URI, e.g. |
| Neo4j username |
| Neo4j password |
| HTTP port (default |
| Bearer token clients must present on |
.envis git-ignored. Never commit real credentials.
Exposing it to Databricks (or any remote client)
The server listens on localhost. To let a remote MCP client reach it during development, expose the port with a tunnel:
ngrok http 3000Then register the public URL as a UC HTTP/MCP connection in Databricks, using
Authorization: Bearer <MCP_SECRET_TOKEN>. For production, host the server on a
reachable machine instead of a tunnel.
Project layout
neo4j-mcp-server/
├── src/
│ ├── index.ts # the MCP server (tools + HTTP transport)
│ └── seed.ts # optional sample-data seeder
├── package.json
├── tsconfig.json
├── .env.example
└── .gitignoreTool Schema Changelog
Recent tool additions, removals, and schema changes observed during successful MCP inspections.
Loading tool schema changelog…
This server cannot be deployed
Maintenance
Related MCP Connectors
Persistent memory, knowledge graph, task management and more for AI agents via MCP.
MCP facade over the Nebelus Construction API. ~48 tools give full agent build parity: create/update/probe agents, edit graphs, attach knowledge and vector stores, wire connectors, set governance policies and locked guardrails, enable grounding-trace, and read deployment wiring. Purpose-built for regulated industries: data residency is enforced per region (EU / GCC-KSA), with PII controls and an audit trail. Agents are created as drafts — no deploy tool is exposed over MCP by design; publishing happens in the Nebelus console.
PostgreSQL, MySQL, and SQL Server in one session. 26 read-only MCP tools for AI agents.
A private graph database you query in plain English or Cypher. Hosted, nothing to install.
Related MCP Servers
- AlicenseNot gradedqualityCmaintenanceThis lets you use Claude Desktop, or any MCP Client, to use natural language to accomplish things with Neo4j and your Aura account.989MIT
- AlicenseNot gradedqualityDmaintenanceEnables AI assistants to interact with Neo4j graph databases through natural language, supporting Cypher queries, schema management, data manipulation, and graph algorithms.MIT
- AlicenseNot gradedqualityCmaintenanceEnables LLMs to interact with Neo4j graph databases using natural language to execute Cypher queries and introspect database schemas. It supports both read and write operations for local, Docker, and cloud-based instances like Neo4j Aura.MIT
- AlicenseAqualityCmaintenanceMCP server for Neo4j that provides abstract graph operations for LLMs, enabling safe and consistent interaction with Neo4j databases through tools like search, insert, update, delete, and schema introspection.8MIT