MCP Neo4j Server
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| NEO4J_URI | No | Neo4j database URI | bolt://localhost:7687 |
| NEO4J_PASSWORD | Yes | Neo4j password | |
| NEO4J_USERNAME | No | Neo4j username | neo4j |
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| execute_queryC | Execute a Cypher query on Neo4j database |
| create_nodeB | Create a new node in Neo4j |
| create_relationshipB | Create a relationship between two nodes |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 3 tools
Each tool targets a distinct operation: creating nodes, creating relationships, and executing arbitrary queries. There is no overlap.
All tools follow a consistent verb_noun pattern in snake_case: create_node, create_relationship, execute_query.
With 3 tools, the server is slightly small but still reasonable for a focused database interface. The tools cover essential create and query operations.
The server lacks direct update and delete operations on nodes/relationships. While execute_query can handle these via Cypher, it creates a dependency on raw queries, which is a notable gap.