Neo4j MCP Server
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| NEO4J_URI | Yes | Neo4j connection URI | bolt://localhost:7687 |
| NEO4J_USER | Yes | Neo4j username | neo4j |
| NEO4J_DATABASE | No | Database name | neo4j |
| NEO4J_MCP_HOST | No | HTTP host (for streamable-http/sse) | 0.0.0.0 |
| NEO4J_MCP_PORT | No | HTTP port (for streamable-http/sse) | 8080 |
| NEO4J_PASSWORD | Yes | Neo4j password | |
| NEO4J_MCP_TRANSPORT | No | Transport: stdio, sse, streamable-http | stdio |
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 | {
"listChanged": false
} |
| prompts | {
"listChanged": false
} |
| resources | {
"subscribe": false,
"listChanged": false
} |
| experimental | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| neo4j_searchA | Search for nodes in Neo4j. Provide ONE of:
Args: label: Node label to filter by (e.g. "Comprovante", "Pessoa"). properties: Optional dict of exact property matches {key: value}. query: Free-text search across all string properties (LIKE %query%). limit: Maximum results to return (default 25, max 100). |
| neo4j_search_relationshipsA | Search for relationships (edges) in Neo4j. Finds patterns (from_node)-[rel]->(to_node) matching the given filters. Args: from_label: Label of the source node. from_properties: Property filters on the source node. rel_type: Relationship type to match (e.g. "PAGOU", "PERTENCE"). to_label: Label of the target node. to_properties: Property filters on the target node. limit: Maximum results (default 25, max 100). |
| neo4j_insertB | Create a node in Neo4j. Args: label: Node label (e.g. "Comprovante", "Pessoa", "Categoria"). properties: Node properties as key-value pairs. |
| neo4j_insert_relationshipA | Create a relationship between two existing nodes (matched by label + properties). Args: from_label: Label of the source node. from_properties: Properties to match the source node (must be unique). rel_type: Relationship type (e.g. "PAGOU", "PERTENCE"). to_label: Label of the target node. to_properties: Properties to match the target node (must be unique). rel_properties: Optional properties on the relationship itself. |
| neo4j_updateA | Update properties on nodes matching label + match_properties. Args: label: Node label to match. match_properties: Properties to identify the node(s). update_properties: Properties to set/update on matched nodes. |
| neo4j_deleteA | Delete nodes matching label + match_properties. Args: label: Node label to match. match_properties: Properties to identify the node(s). detach: If True, delete node even if it has relationships (DETACH DELETE). |
| neo4j_schemaA | Introspect the Neo4j database schema. Returns labels, relationship types, indexes, and constraints. |
| neo4j_queryA | Execute a raw Cypher query against Neo4j. WARNING: This tool allows arbitrary Cypher execution. Use with caution. Prefer the structured tools (neo4j_search, neo4j_insert, etc.) when possible. Args: query: Cypher query string. parameters: Optional query parameters. write: Set True for write queries (CREATE, MERGE, DELETE, SET, etc.). |
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 8 tools
Each tool has a distinct purpose: create, read, update, delete operations for nodes and relationships, schema introspection, and raw query execution. No two tools overlap in functionality.
All tools follow the consistent `neo4j_<verb>` pattern in snake_case, with verbs like delete, insert, search, update, etc. The pattern is predictable and easy to understand.
8 tools cover the essential operations for a Neo4j database (CRUD, query, schema, search, relationship management) without being excessive or insufficient.
The toolset provides comprehensive coverage: node CRUD, relationship creation, update, search (by label/properties or free-text), relationship search, schema introspection, and raw Cypher for anything missing.