Neo4j AuraDB uses GateRook’s Neo4j connector. With neo4j+s:// and the instance's credentials.
The screenshots show GateRook 2.0.0: the Neo4j AuraDB form, the endpoint selector, and this connector’s actual tool preview. The form and preview have not been saved. Select a screenshot to open it at full size.
1. Create a connection and enter the settings
In GateRook, open Connections, select Add connection, search for Neo4j AuraDB, choose its card and select Continue to configure. GateRook downloads the official Neo4j connector module when you choose it. Wait for the download and verification to finish before configuring the connection.
Copy the AuraDB connection URI and database credentials from the instance connection details or the credentials file saved when the instance was created.
Use a running AuraDB instance and a database user with the required graph read privileges. Aura console credentials are separate from the graph database login.
Enter a Name, for example neo4j-auradb-demo. Your AI app uses this name to choose the connection.
Enter the instance's neo4j+s:// address in Connection URI. Keep the TLS scheme and the exact Aura hostname.
Select User and password under Sign in with, then fill User and Password with the database credentials.
Set Database to the graph database you intend to query, normally neo4j unless your instance specifies otherwise. Keep CA certificate (PEM) empty for Aura's publicly trusted certificate, and set bounded Rows per query in Advanced if needed.
Choose Development, Staging or Production to match the service. Review the connector’s limit and access settings before continuing.
2. Test the connection and add it to an endpoint
Select Continue to test. GateRook checks the settings from your computer. Review the result and resolve any connection, certificate or permission error before continuing.
If the instance was paused, make sure it is available before retrying. Authentication failures call for checking the graph credentials; connection failures call for checking the URI and network access to the Neo4j protocol endpoint.
After the test passes, select Continue to add to an endpoint. Choose the endpoint your AI app uses, review its tool modes, then select Save connection. GateRook offers default as the starter endpoint.
3. Use the connection from your AI IDE
After saving Neo4j AuraDB on the endpoint and passing its connection test, ask your AI app to use neo4j-auradb-demo, or the name you chose. If its tools are missing, confirm the endpoint assignment and refresh the MCP connection or start a new chat.
The preview below shows this connector’s default tools before saving. The table explains what each tool can do; connection settings, credentials and endpoint policies can restrict access further.
Start with a small read request. Replace example resource names with existing resources your connection may access. Open Activity after the call to inspect its connection, tool, arguments, policy decision and result metadata.
Ask your AI, for example
- “Inspect the node labels and relationship types in this graph.”
- “Show at most 10 example nodes for one selected label, excluding sensitive properties.”
- “Find a short path between two specified nodes without changing the graph.”
| Tool | What it does | Starts as |
|---|---|---|
neo4j_schema | Labels, relationship types, property keys, indexes and constraints of the connection's database; optionally which labels connect through which types. | Read only |
neo4j_query | One Cypher read with $parameters, run in a READ transaction after Neo4j's EXPLAIN calls it read only. Nodes, relationships, paths, temporal and spatial values come back as JSON. | Read only |
neo4j_execute | One Cypher write with $parameters. You approve the exact statement with Neo4j's plan of it; it runs once, in one transaction, and reports what it changed. | Approval |
You can change each tool’s mode on the endpoint. Every call your AI makes appears in Activity.