Databricks Unity Catalog (BYOK) — connector documentation
- MCP endpoint:
https://byok-databricks-unity-catalog.connectorbay.com/mcp - REST API:
POST https://byok-databricks-unity-catalog.connectorbay.com/v1/tools/{tool_name}, described by the OpenAPI 3.1 spec athttps://byok-databricks-unity-catalog.connectorbay.com/openapi.json - Transport: Streamable HTTP, stateless, MCP specification 2025-06-18 or later
- Authentication: your own Databricks Unity Catalog personal access token, sent in the
X-Upstream-Keyheader of every request (never stored, logged or cached) - Health:
https://byok-databricks-unity-catalog.connectorbay.com/health· Tool schemas:https://byok-databricks-unity-catalog.connectorbay.com/tools.json - Publisher: Unify Dynamics LLC · connectorbay.com/byok-databricks-unity-catalog · agent@connectorbay.com
What Databricks Unity Catalog (BYOK) is for
Databricks Unity Catalog (BYOK) lets an AI assistant read your own Databricks Unity Catalog data through the Databricks Unity Catalog API with a key you supply (personal access token). Read-only: 9 tools (get_metastore_summary, get_table, list_table_summaries, list_volumes, list_functions, list_registered_models, list_model_versions, list_external_locations, list_connections). The BYOK key travels with each request, is used for that one call only and is never stored, logged or cached; it is only ever sent to *.cloud.databricks.com. Unofficial connector by Unify Dynamics LLC: not affiliated with, endorsed by or sponsored by Databricks Unity Catalog. Databricks Unity Catalog and its logos are trademarks of their owners and are used only to say which service the connector works with.
Ask your assistant things like:
- "Which Unity Catalog metastore is my Databricks workspace attached to?"
- "What columns does the Unity Catalog table main.default.orders have?"
- "Which tables in the main catalog have 'order' in the name?"
- "Which volumes exist in main.default?"
- "Which functions are defined in main.default?"
- "Which registered ML models are in Unity Catalog?"
What it does
get_metastore_summary: Show the Unity Catalog metastore of the workspace: name, cloud, region, owner, creation time and Delta Sharing scope.get_table: Get one Unity Catalog table or view by its three-level name: type, format, owner, comment, storage location and the column list (name, type, comment, nullability, position).list_table_summaries: List the full names and types of tables in a catalog, optionally narrowed by SQL LIKE patterns for schema and table names. Token paginated.list_volumes: List the volumes of a Unity Catalog schema with type, owner, comment, storage location and timestamps.list_functions: List the user-defined functions of a Unity Catalog schema with data type, language, determinism, owner, comment and timestamps. Function bodies are not requested.list_registered_models: List Unity Catalog registered models, optionally within one schema (give both catalog and schema), with owner, comment and timestamps.list_model_versions: List the versions of one Unity Catalog registered model with status, source run, comment and timestamps.list_external_locations: List Unity Catalog external locations (cloud storage paths governed by Unity Catalog) with URL, credential name, owner, read-only flag and timestamps.list_connections: List Lakehouse Federation connections (links to external databases) with type, URL, owner, read-only flag and comment. Connection options and secrets are not returned.
BYOK key
You bring your own Databricks Unity Catalog personal access token (https://docs.databricks.com/aws/en/dev-tools/auth/pat). Your assistant sends it in the X-Upstream-Key header with each request. ConnectorBay uses it for that one call only: it is never stored, logged or cached, never shown in an answer, and it is only sent to *.cloud.databricks.com over https, with no redirects followed. Create a key with the fewest permissions the tools need (read-only if the provider offers it), and revoke it at the provider whenever you like.
Data sources
- https://docs.databricks.com/api/workspace/introduction (the API this connector calls, with a BYOK key)
Live from the Databricks Unity Catalog API (*.cloud.databricks.com) with a BYOK key; documentation: https://docs.databricks.com/api/workspace/introduction. Endpoints checked against that documentation on 2026-10-16.
What it is not
Unofficial connector by Unify Dynamics LLC: not affiliated with, endorsed by or sponsored by Databricks Unity Catalog. Databricks Unity Catalog and its logos are trademarks of their owners and are used only to say which service the connector works with. It is read-only: it never creates, changes, sends or deletes anything in your Databricks Unity Catalog account.
Built for: Worldwide. Languages: English.