Neo4j MCP Server
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| NEO4J_URI | No | The URI of your Neo4j database | |
| NEO4J_USER | No | Your Neo4j username | |
| NEO4J_PASSWORD | No | Your Neo4j password | |
| NEO4J_CONNECTION | No | Single connection string in the format <uri>,<user>,<password> |
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
Server capabilities have not been inspected yet.
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| neo4j-queryC | Execute a Cypher query against the Neo4j database |
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 1 tool
With only one tool, there is no possibility of ambiguity or overlap between tools. The tool has a single, clear purpose: executing Cypher queries against a Neo4j database.
Since there is only one tool, naming consistency is inherently perfect. The tool name 'neo4j-query' follows a clear and descriptive pattern, though no pattern can be established or broken with a single tool.
A single tool is too few for a database server's apparent scope, which typically requires operations like creating, updating, deleting, and querying data. This minimal set limits functionality and forces all operations through a generic query interface, which is insufficient for structured interactions.
The tool surface is severely incomplete for a Neo4j database server. While 'neo4j-query' allows executing arbitrary Cypher queries, it lacks dedicated tools for common operations like creating nodes, updating relationships, or managing transactions, leaving significant gaps that agents must work around with raw queries.