Databricks MCP Server
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| DATABRICKS_HOST | Yes | Databricks workspace hostname (e.g., dbc-xxxxxxxx-xxxx.cloud.databricks.com) | |
| DATABRICKS_TOKEN | Yes | Databricks personal access token | |
| DATABRICKS_HTTP_PATH | Yes | HTTP path for the SQL warehouse (e.g., /sql/1.0/warehouses/xxxxxxxxxxxxxxxx) |
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
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {
"listChanged": false
} |
| prompts | {
"listChanged": false
} |
| resources | {
"subscribe": false,
"listChanged": false
} |
| experimental | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| run_queryA | Run a READ-ONLY SQL query against samples.nyctaxi.trips and return rows. Only a single SELECT/WITH is allowed; LIMIT 1000 is appended if missing. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
| revenue_by_month | Monthly revenue trend. |
| busiest_pickup_zones | Top pickup ZIP codes by demand. |
| trips_by_hour | Demand by hour of day. |
| fare_distance_summary | Overall fare and distance stats. |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
| nyctaxi_schema | Curated schema and business context for samples.nyctaxi.trips. |
TDQS
Scored across 1 tool
With only one tool, there is no risk of confusion between tools. The tool's purpose is clearly defined as running a read-only SQL query on a specific table.
With a single tool, naming consistency is not a concern. The tool name 'run_query' follows a common verb_noun pattern.
The server is named 'Databricks MCP Server', implying access to a wide range of Databricks functionality, but only one tool for a single query on a fixed table is provided. This is an extreme mismatch in scope.
The tool set is severely incomplete for a Databricks server. It lacks operations for managing databases, tables, clusters, or running arbitrary SQL beyond the fixed sample table.