Be the first to get access to new connectors. Get early access →
ConnectorBay Early access

Databricks Compute (BYOK) — connector documentation

  • MCP endpoint: https://byok-databricks-compute.connectorbay.com/mcp
  • REST API: POST https://byok-databricks-compute.connectorbay.com/v1/tools/{tool_name}, described by the OpenAPI 3.1 spec at https://byok-databricks-compute.connectorbay.com/openapi.json
  • Transport: Streamable HTTP, stateless, MCP specification 2025-06-18 or later
  • Authentication: your own Databricks Compute personal access token, sent in the X-Upstream-Key header of every request (never stored, logged or cached)
  • Health: https://byok-databricks-compute.connectorbay.com/health · Tool schemas: https://byok-databricks-compute.connectorbay.com/tools.json
  • Publisher: Unify Dynamics LLC · connectorbay.com/byok-databricks-compute · agent@connectorbay.com

What Databricks Compute (BYOK) is for

Databricks Compute (BYOK) lets an AI assistant read your own Databricks Compute data through the Databricks Compute API with a key you supply (personal access token). Read-only: 10 tools (get_cluster, list_instance_pools, get_instance_pool, list_node_types, list_spark_versions, list_availability_zones, list_policy_families, list_global_init_scripts, get_cluster_library_status, list_all_cluster_library_statuses). 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 Compute. Databricks Compute 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:

  • "Why is Databricks cluster 0101-120000-abcd1234 terminated?"
  • "Which Databricks instance pools do we have and how many instances are idle?"
  • "Show details of Databricks instance pool 0101-120000-pool123"
  • "Which node types can I use for Databricks clusters?"
  • "Which Databricks runtime versions are available?"
  • "Which availability zones can my Databricks clusters use?"

What it does

  • get_cluster: Get one cluster: state and message, Spark runtime, node types, worker count or autoscale, auto-termination, access mode, policy, creator and start time. Spark settings and environment variables are not returned.
  • list_instance_pools: List instance pools with node type, minimum idle and maximum capacity, idle auto-termination, state and usage counts.
  • get_instance_pool: Get one instance pool: node type, capacity limits, idle auto-termination, state, usage counts and preloaded runtimes.
  • list_node_types: List the node types (instance types) that clusters can use: cores, memory, GPUs, category and Photon support.
  • list_spark_versions: List the Databricks Runtime versions available for clusters, with the key to use and the display name.
  • list_availability_zones: List the availability zones clusters can be created in and the workspace default zone.
  • list_policy_families: List the Databricks-provided cluster policy families (templates for cluster policies) with name and description. The definition JSON is not returned.
  • list_global_init_scripts: List workspace-wide init scripts with name, enabled flag, run position, creator and timestamps. Script bodies are not returned.
  • get_cluster_library_status: List the libraries installed or being installed on one cluster with install status and messages.
  • list_all_cluster_library_statuses: List library install status for every cluster of the workspace.

BYOK key

You bring your own Databricks Compute 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

Live from the Databricks Compute 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 Compute. Databricks Compute 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 Compute account.

Built for: Worldwide. Languages: English.