> **Building with AI coding agents?** If you're using an AI coding agent, install the official Scalekit plugin. It gives your agent full awareness of the Scalekit API — reducing hallucinations and enabling faster, more accurate code generation.
>
> - **Claude Code**: `/plugin marketplace add scalekit-inc/claude-code-authstack` then `/plugin install <auth-type>@scalekit-auth-stack`
> - **GitHub Copilot CLI**: `copilot plugin marketplace add scalekit-inc/github-copilot-authstack` then `copilot plugin install <auth-type>@scalekit-auth-stack`
> - **Codex**: run the bash installer, restart, then open Plugin Directory and enable `<auth-type>`
> - **Skills CLI** (Windsurf, Cline, 40+ agents): `npx skills add scalekit-inc/skills --list` then `--skill <skill-name>`
>
> `<auth-type>` / `<skill-name>`: `agent-auth`, `full-stack-auth`, `mcp-auth`, `modular-sso`, `modular-scim` — [Full setup guide](https://docs.scalekit.com/dev-kit/build-with-ai/)

---

# Databricks Workspace

<div class="grid grid-cols-5 gap-4 items-center">
 <div class="col-span-4">
  Connect to Databricks Workspace APIs using a Service Principal with OAuth 2.0 client credentials to manage clusters, jobs, SQL, and more.
 </div>
 <div class="flex justify-center">
  <img src="https://cdn.scalekit.com/sk-connect/assets/provider-icons/databricks-1.svg" width="64" height="64" alt="Databricks logo" />
 </div>
</div>

Supports authentication: OAuth 2.0

## Set up the agent connector

<SetupDatabricksSection />

## Usage

<UsageDatabricksSection />

## Tool list

## `databricksworkspace_cluster_get`

Get details of a specific Databricks cluster by cluster ID.

| Name | Type | Required | Description |
| --- | --- | --- | --- |
| `cluster_id` | string | Yes | The unique identifier of the cluster |

## `databricksworkspace_cluster_start`

Start a terminated Databricks cluster by cluster ID.

| Name | Type | Required | Description |
| --- | --- | --- | --- |
| `cluster_id` | string | Yes | The unique identifier of the cluster to start |

## `databricksworkspace_cluster_terminate`

Terminate a Databricks cluster by cluster ID. The cluster transitions to a `TERMINATED` state — this is reversible. The cluster configuration is retained for 30 days (unless pinned) and can be restarted via the start API. To permanently remove a cluster and its configuration, use the Databricks `/permanent-delete` endpoint directly.

| Name | Type | Required | Description |
| --- | --- | --- | --- |
| `cluster_id` | string | Yes | The unique identifier of the cluster to terminate |

## `databricksworkspace_clusters_list`

List all clusters in the Databricks workspace.

This tool takes no input parameters.

## `databricksworkspace_job_get`

Get details of a specific Databricks job by job ID.

| Name | Type | Required | Description |
| --- | --- | --- | --- |
| `job_id` | integer | Yes | The unique identifier of the job |

## `databricksworkspace_job_run_now`

Trigger an immediate run of a Databricks job by job ID.

| Name | Type | Required | Description |
| --- | --- | --- | --- |
| `job_id` | integer | Yes | The unique identifier of the job to run |

## `databricksworkspace_job_runs_list`

List all job runs in the Databricks workspace, optionally filtered by job ID.

| Name | Type | Required | Description |
| --- | --- | --- | --- |
| `job_id` | integer | No | Filter runs by a specific job ID. If omitted, returns runs for all jobs |
| `limit` | integer | No | Number of runs to return. Defaults to 20, maximum is 1000 |
| `offset` | integer | No | Offset of the first run to return, used for pagination |

## `databricksworkspace_jobs_list`

List all jobs in the Databricks workspace.

| Name | Type | Required | Description |
| --- | --- | --- | --- |
| `limit` | integer | No | Number of jobs to return. Defaults to 20, maximum is 100 |
| `offset` | integer | No | Offset of the first job to return, used for pagination |

## `databricksworkspace_scim_me_get`

Retrieve information about the currently authenticated service principal in the Databricks workspace.

This tool takes no input parameters.

## `databricksworkspace_scim_users_list`

List all users in the Databricks workspace using the SCIM v2 API.

| Name | Type | Required | Description |
| --- | --- | --- | --- |
| `count` | integer | No | Maximum number of results to return per page |
| `filter` | string | No | SCIM filter expression to narrow results (e.g. `userName eq "user@example.com"`) |
| `startIndex` | integer | No | 1-based index of the first result to return, used for pagination |

## `databricksworkspace_secrets_scopes_list`

List all secret scopes available in the Databricks workspace.

This tool takes no input parameters.

## `databricksworkspace_sql_statement_execute`

Execute a SQL statement on a Databricks SQL warehouse and return the results.

| Name | Type | Required | Description |
| --- | --- | --- | --- |
| `statement` | string | Yes | The SQL statement to execute |
| `warehouse_id` | string | Yes | The ID of the SQL warehouse to execute the statement on |
| `catalog` | string | No | The Unity Catalog name to use for execution |
| `schema` | string | No | The schema to use for execution |

## `databricksworkspace_sql_warehouses_list`

List all SQL warehouses available in the Databricks workspace.

This tool takes no input parameters.

---

## More Scalekit documentation

| Resource | What it contains | When to use it |
|----------|-----------------|----------------|
| [/llms.txt](/llms.txt) | Structured index with routing hints per product area | Start here — find which documentation set covers your topic before loading full content |
| [/llms-full.txt](/llms-full.txt) | Complete documentation for all Scalekit products in one file | Use when you need exhaustive context across multiple products or when the topic spans several areas |
| [sitemap-0.xml](https://docs.scalekit.com/sitemap-0.xml) | Full URL list of every documentation page | Use to discover specific page URLs you can fetch for targeted, page-level answers |
