{/* Generated by scripts/generate-integration-catalog.mjs. Do not edit by hand. */}
At a glance
- Availability: Experimental (how to enable).
- Authentication: API key.
- Connection: The key from
DATABRICKS_TOKENis sent as theBearerprefixedAuthorizationheader. - Provider documentation: Authentication reference.
Credentials
Set these per environment. See Connect an integration.
Setup
- Get a workspace: If you don't have one, sign up for the Databricks Free Edition at https://www.databricks.com/learn/free-edition, or use an existing workspace on AWS, Azure, or GCP.
- Find your workspace host: Copy the hostname from your workspace URL, e.g. dbc-a1b2345c-d6e7.cloud.databricks.com (AWS/GCP) or adb-1234567890123456.7.azuredatabricks.net (Azure). Set it as DATABRICKS_HOST (no https://).
- Generate a personal access token: In the workspace, click your username > Settings > Developer, click Manage next to Access tokens, then Generate new token. Name it, set a lifetime, and copy the token immediately.
- Store the credentials: Add DATABRICKS_TOKEN=<your token> and DATABRICKS_HOST=<your workspace host> to your .env file.
- Verify access: Run the List SQL Warehouses tool. A 401/403 means the token is invalid or expired, or token-based auth is disabled by your workspace admin.
Provider notes
- Personal access tokens are workspace-scoped: the token only works against the workspace host where it was created
- Executing SQL requires a running (or auto-starting) SQL warehouse; the first query may take a minute while the warehouse starts
- Databricks recommends OAuth over PATs for production use; PATs are the simplest option for getting started
- Tokens can expire; if calls suddenly return 403, regenerate the token
Tools
Verify the connection
Call a read tool such as databricks__list_clusters with arguments for your account. Confirm that the result comes from the intended account or workspace before enabling write tools.