Databricks MCP Server
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| DATABRICKS_HOST | Yes | Your Databricks instance URL (e.g., https://your-databricks-instance.azuredatabricks.net) | |
| DATABRICKS_TOKEN | Yes | Your Databricks personal access token |
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Server capabilities have not been inspected yet.
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| list_clustersB | List all Databricks clusters |
| create_clusterC | Create a new Databricks cluster |
| terminate_clusterC | Terminate a Databricks cluster |
| get_clusterC | Get information about a specific Databricks cluster |
| start_clusterB | Start a terminated Databricks cluster |
| list_jobsA | List Databricks jobs with pagination and filtering. |
| list_job_runsA | List recent job runs with detailed status and duration information. |
| run_jobD | Run a Databricks job |
| list_notebooksC | List notebooks in a workspace directory |
| export_notebookC | Export a notebook from the workspace |
| list_filesC | List files and directories in DBFS |
| execute_sqlB | Execute a SQL statement and wait for completion (blocking) |
| execute_sql_nonblockingB | Start SQL statement execution and return immediately with statement_id (non-blocking) |
| get_sql_statusC | Get the status and results of a SQL statement by statement_id |
| create_notebookC | Create a new notebook in the Databricks workspace |
| create_jobB | Create a new Databricks job to run a notebook (uses serverless by default) |
| upload_file_to_volumeA | |
| upload_file_to_dbfsA | |
| list_volume_filesA | |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 19 tools
Every tool has a clearly distinct purpose targeting specific Databricks resources and actions. There is no ambiguity: create_* tools create resources, list_* tools list resources, execute_sql vs execute_sql_nonblocking handle different execution modes, and upload_file_to_dbfs vs upload_file_to_volume target different storage systems. The descriptions reinforce these distinctions.
All tool names follow a consistent verb_noun pattern with snake_case throughout. Verbs like create, list, get, execute, run, start, terminate, export, and upload are used predictably with appropriate nouns (cluster, job, notebook, sql, files, etc.). There are no deviations in naming conventions.
With 19 tools, the count is slightly high but reasonable for a comprehensive Databricks interface covering clusters, jobs, notebooks, SQL execution, and file management. It includes core operations for each domain without being excessive, though some tools like list_job_runs and list_jobs could potentially be consolidated to reduce count.
The tool surface provides complete CRUD/lifecycle coverage for Databricks domains: clusters (create/get/list/start/terminate), jobs (create/list/run with detailed run tracking), notebooks (create/list/export), SQL execution (blocking/non-blocking with status check), and file management (list/upload for both DBFS and Unity Catalog volumes). There are no obvious gaps that would cause agent failures.