mcp-neo4j-server-sse is an MCP server that uses Server-Sent Events (SSE) or STDIO as the transport protocol.
mcp-neo4j-server-sse is an MCP server that uses Server-Sent Events (SSE) or STDIO as the transport protocol. The neo4j mcp server wraps that behind the Model Context Protocol, so an assistant can use it through 7 defined tools rather than through you.
A Model Context Protocol (MCP) server implementation that provides database interaction and allows for graph exploration capabilities through Neo4j. This server enables the execution of Cypher graph queries, analysis of complex domain data, and supports the selection of remotely accessible databases. Inspired by neo4j-contrib/mcp-neo4j.
Setup follows the usual MCP pattern — install or clone the server, register it in your client's configuration file, restart the client. The configuration blocks on this page cover the common clients.
Everything the assistant can do here goes through one of these:
read-neo4j-cypher — Execute Cypher read queries to read data from the databaseInput — - query (string): The Cypher query to executeReturns — Query results as array of objectswrite-neo4j-cypher — Execute updating Cypher queriesget-neo4j-schema — Get a list of all nodes types in the graph database, their attributes with name, type and relationships to other node typesPrompts — The Prompts tool exposed by this serverTools — The Tools tool exposed by this serverAmong 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. Neo4j's toolset — read-neo4j-cypher, Input, Returns and 4 more — is a fair guide to whether it matches your workflow. It is maintained by dsimile; worth a glance at recent repository activity before you build anything load-bearing on it.
This entry was verified against Neo4j's own documentation before publication; SyncDev keeps the directory reviewed rather than auto-generated.
| Tool | What it does |
|---|---|
| read-neo4j-cypher | Execute Cypher read queries to read data from the database |
| Input | - query (string): The Cypher query to execute |
| Returns | Query results as array of objects |
| write-neo4j-cypher | Execute updating Cypher queries |
| get-neo4j-schema | Get a list of all nodes types in the graph database, their attributes with name, type and relationships to other node types |
| Prompts | The Prompts tool exposed by this server. |
| Tools | The Tools tool exposed by this server. |
- STDIO Mode
```json
{
"mcpServers": {
"neo4j-local": {
"disabled": false,
"timeout": 60,
"command": "uv",
"args": [
"run",
"/absolute/path/to/neo4j_server_remote.py",
"--url",
"bolt://localhost:7687",
"--username",
"neo4j",
"--password",
"neo4j123",
"--database",
"neo4j",
"--mode",
"stdio"
]
}
}
}Configuration as documented by the project. Restart the client after saving.
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.