neo4j

Neo4j

Name: Nexoxa Bridge
Author: Nexoxa

Property graph database via neo4j:// — Cypher lab and graph-native browsing.

GPHneo4j://neo4j:password@host:7687

The story

These pages use illustrative scenarios (sample names and timelines) to explain real Nexoxa Bridge features. Connection URLs, sidebar panels, and vault behavior match the product; story details are teaching examples, not customer case studies.

Product team GraphFirst models recommendations as a property graph in Neo4j while orders stay in Postgres. Data engineer Sam used to alt-tab between Bolt browser and pgAdmin to debug why a MATCH returned empty — two mental models, two vaults, two windows.

Sam saved neo4j://recommendations and postgresql://orders in Bridge. Cypher runs beside SQL; graph relationships render natively for Neo4j while Postgres gets the FK knowledge graph. One workbench, two engines, one encrypted credential store.

Graph data wants graph tools — Bridge does not pretend nodes are just another table.

Connection URL

Scheme: neo4j://

Parameters

Neo4j Boltstringvaultrequired

neo4j://neo4j:password@host:7687

Paste the URL in Nexoxa Bridge → New connection. Save a human-readable name — MCP references that name, not the raw URL with embedded passwords.

Step 1

Cypher lab

Sam writes MATCH (u:User)-[:VIEWED]->(p:Product) WHERE u.id = $id RETURN p LIMIT 20, binds parameters, and inspects tabular results. Syntax highlighting catches a typo before it hits staging.
Default Bolt port 7687; user neo4j unless the instance uses another principal.

Cypher execution with formatted results. Connection URL neo4j://user:password@host:7687. Credentials encrypted on save. Query history in the same lab chrome as SQL engines.

Step 2

Graph relationships

Sam explores relationship types discovered from introspection and recent queries — sees VIEWED and PURCHASED clusters around Product nodes. That shapes index advice for the next sprint.
Native graph view complements Postgres FK graphs for hybrid architectures.

Relationship and node browsing from Neo4j metadata. Export-friendly results for downstream tooling. Pairs with SQL knowledge graph features on relational sidecars.

Explore the full feature guide: Knowledge graph feature