Neo4j MCP server for integrating Neo4j graph database with Claude Desktop through natural language interactions
Most database access work still happens through a UI a human drives. MCP MCP server moves it into the conversation instead. Neo4j MCP server for integrating Neo4j graph database with Claude Desktop through natural language interactions.
The server publishes 4 tools. What each one is for:
execute_query — Execute Cypher queries on the Neo4j databasecreate_node — Create a new node in the graph databasecreate_relationship — Create a relationship between two existing nodesTools — The Tools tool exposed by this serverInstallation goes through your MCP client rather than a global install: point it at @alanse/mcp-neo4j on npm and it is fetched when the client starts. The copy-paste blocks for Claude Desktop, Claude Code and Cursor are further down this page.
Configuration is passed through the environment: NEO4J_URI, NEO4J_USERNAME, NEO4J_PASSWORD, NEO4J_DATABASE. Treat anything key-shaped as a real credential — scope it to the minimum the server needs, and rotate it if it ever lands in a shared config.
Among the database access options, the useful question is rarely "what can it do" but "what does it cost you to run" — permissions, credentials, and how much of your context its toolset consumes. MCP's toolset — execute_query, create_node, create_relationship and 1 more — is a fair guide to whether it matches your workflow. It is maintained by alanse-daichi; worth a glance at recent repository activity before you build anything load-bearing on it.
This entry was verified against MCP's own documentation before publication; SyncDev keeps the directory reviewed rather than auto-generated.
| Tool | What it does |
|---|---|
| execute_query | Execute Cypher queries on the Neo4j database |
| create_node | Create a new node in the graph database |
| create_relationship | Create a relationship between two existing nodes |
| Tools | The Tools tool exposed by this server. |
{
"mcpServers": {
"neo4j-1": {
"command": "npx",
"args": ["-y", "@alanse/mcp-neo4j"],
"env": {
"NEO4J_URI": "your-value",
"NEO4J_USERNAME": "your-value",
"NEO4J_PASSWORD": "your-value",
"NEO4J_DATABASE": "your-value"
}
}
}
}Add to claude_desktop_config.json, then restart Claude Desktop.
| Variable | Description | Required |
|---|---|---|
| NEO4J_URI | Configuration value read at startup. | Optional |
| NEO4J_USERNAME | Configuration value read at startup. | Optional |
| NEO4J_PASSWORD | Configuration value read at startup. | Optional |
| NEO4J_DATABASE | Configuration value read at startup. | Optional |
Read-only SQL access to Postgres — let your assistant inspect schemas and answer questions from real data.
Manage your whole Supabase project in conversation — database, auth, storage, Edge Functions and branches.
Query, modify and analyse local SQLite databases in conversation — the fastest way to chat with a data file.
Metabase ships its own MCP endpoint — search your BI content, build and run queries, and save questions and dashboards without leaving the chat.
Official MongoDB server covering data, schemas and Atlas management — from find queries to spinning up clusters.
Serverless Postgres with database branching — point your assistant at Neon and let it work on disposable copies.