Download Neo4j JDBC Driver

Download the Neo4j JDBC driver, copy the JDBC URL into DbSchema, and start designing schemas with ER diagrams — free Community Edition.

About the Neo4j JDBC driver

A JDBC driver is a Java .jar library that lets applications connect to Neo4j. DbSchema uses JDBC to reverse engineer schemas, run SQL, and generate documentation. Driver files are usually published by the database vendor or an open-source project.

JDBC URL format

Host, port, database name, and SSL options are passed in a URL starting with jdbc:. Each Neo4j driver uses its own syntax — see the connection details below.

The Neo4j JDBC driver

Neo4j is the world's leading graph database, storing data as nodes and relationships that model highly connected domains naturally without costly joins. It powers applications in fraud detection, knowledge graphs, recommendation engines, and network analysis where relationships between entities are first-class data. Neo4j supports the Cypher query language and also exposes a JDBC-compatible interface for SQL tooling integration.

The Neo4j JDBC URL

• Required File(s): neo4j-jdbc-driver-xxx.jar
• Java Driver Class: org.neo4j.jdbc.Driver
• JDBC URL: jdbc:neo4j://{HOST}:{PORT}
• Website: Neo4j

The Neo4j JDBC driver communicates over the Bolt protocol on port 7687. For Neo4j AuraDB (cloud), use the Bolt+Routing URL: jdbc:neo4j+s://xxxxx.databases.neo4j.io. Authentication uses the standard Neo4j username and password credentials.

Connecting to a Remote Neo4j Server

Drivers use the Bolt connector, not the browser's HTTP port, and Bolt has one property beyond the listen address that quietly breaks remote connections.

1. Use the Bolt port, 7687. Port 7474 serves Neo4j Browser over HTTP and is not what a driver connects to.
2. Let the connector listen beyond localhost. In neo4j.conf set server.default_listen_address=0.0.0.0, which applies to every connector, or server.bolt.listen_address=:7687 for Bolt alone. On Neo4j 4 the same settings carry a dbms. prefix instead of server. — check which names your version uses before editing.
3. Check the advertised address when a port is remapped. Neo4j tells the driver where to reconnect using server.bolt.advertised_address. Behind Docker port mapping, NAT or a tunnel, the address the server advertises is not the one you dialled, and the driver follows the advertised one — which is why a connection can open and then immediately fail.
4. Pick single-server or routing. The Standard (Bolt) entry in the Connection Mode combo talks to one server. Cluster (Bolt Routing) asks the cluster for its members and spreads work across them — correct for a cluster, and dependent on every member advertising an address you can reach.
5. Open port 7687 in the server's firewall. The database listens on port 7687 unless it was installed with a different one. A host firewall on the server blocks incoming connections on that port until a rule allows them. The firewall guide has the commands for Windows, ufw, firewalld and iptables.
6. Connect from DbSchema. In the Connection Dialog choose Remote computer or custom port, fill in the server host and the port, then press Test Connection to check that the server answers before you connect.

On Aura there is nothing to configure: the console gives a neo4j+s:// URI with TLS already on, plus the generated password.

DbSchema and Neo4j

DbSchema connects to Neo4j via the Neo4j JDBC driver wrapping the Bolt protocol, enabling visualization of node label schemas and relationship types, and Cypher query execution through the SQL editor interface for graph database management teams.