Databricks Object Browser With Catalog Schema Table Hierarchy Navigation

via “database schema visualization and navigation with hierarchical explorer”

Universal database client for VS Code.

Unique: Implements a VS Code sidebar tree view provider that caches database schema metadata locally and renders it as a collapsible hierarchy, enabling fast navigation without repeated database queries. Uses VS Code's native tree view API for consistent UI and keyboard navigation.

vs others: More integrated into the development workflow than external schema visualization tools because it lives in the sidebar alongside other VS Code panels, eliminating context switching.

via “databricks workspace path navigation and file browsing”

IDE support for Databricks

via “databricks object browser with catalog-schema-table hierarchy navigation”

Databricks SQL driver for SQLTools

Unique: Understands Databricks' three-level namespace (catalog.schema.table) and renders it as a native tree hierarchy, rather than flattening to two-level schema.table like generic SQL drivers

vs others: Provides native Unity Catalog support with catalog-level navigation, whereas generic SQL drivers typically only support schema-level browsing

via “database schema navigation and metadata introspection”

Free universal database tool and SQL client

Unique: Uses database-specific MetaModel implementations (PostgreSQL, Oracle, MySQL extensions) that optimize metadata queries for each database's system catalogs rather than relying solely on generic JDBC DatabaseMetaData, reducing query overhead by 50-70% for large schemas

vs others: Provides faster schema navigation than generic JDBC tools by implementing database-specific metadata query optimizations and lazy-loading, and supports more metadata details (constraints, indexes, comments) than lightweight clients

via “distributed database schema discovery and metadata introspection”

** - A Go implementation of a Model Context Protocol (MCP) server for Trino, enabling LLM models to query distributed SQL databases through standardized tools.

Unique: Implements hierarchical metadata discovery (catalog → schema → table → column) as separate MCP tools, allowing LLMs to progressively explore schema without loading entire warehouse structure. Uses Trino's native information_schema queries rather than custom metadata stores, ensuring consistency with actual database state.

vs others: More efficient than REST API wrappers around Trino's UI because it queries system.information_schema directly and exposes results as structured MCP tools that LLMs can reason about, versus requiring LLMs to parse HTML or navigate REST endpoints.