Skip to main content
Glama
Sign In
Databricks Unity Catalog MCP Server

Databricks Unity Catalog MCP Server

by revodatanl
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Remote

Server Configuration

Describes the environment variables required to run the server.

NameRequiredDescriptionDefault
DATABRICKS_HOSTYesYour Databricks workspace URL.
DATABRICKS_TOKENYesYour Databricks 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

Features and capabilities supported by this server

Protocol revision2025-11-25

CapabilityDetails
tools
{
  "listChanged": false
}
prompts
{
  "listChanged": false
}
resources
{
  "subscribe": false,
  "listChanged": false
}
experimental
{}

Tools

Functions exposed to the LLM to take actions

NameDescription
get-catalogsB

Retrieve a list of all available catalogs in the Databricks workspace

get-schemas-in-catalogsB
        Retrieve a list of all available schemas in the given catalogs.

        Args:
            - catalog_names: List of catalog names to get schemas for
get-tables-in-catalogs-schemasC
        Retrieve a list of all tables in the given catalogs and schemas.

        Args:
            - catalog_schemas: List of catalog.schema strings to get tables for
get-tables-detailsA
        Retrieve detailed information for the given tables.

        Args:
            - full_table_names: List of full table names in the format catalog.schema.table to get details for
find-tables-by-nameA
        Find tables by name in Unity Catalog using fuzzy matching with in-memory caching.

        Args:
            - search_term: The search term to find tables by
            - limit: The maximum number of results to return
            - force_refresh: If True, bypass the cache and fetch fresh data from the API
get-jobsA

Retrieve a list of all jobs in the workspace

get-job-detailsC
        Get job details like settings and tasks by the job id.

        Args:
            - List of integer job IDs
get-job-runsC
        Get recent job runs by job id.

        Args:
            - job_ids: List of job ids for which to get the runs
            - amount: Amount of runs to get per job, sorted by most recent

Prompts

Interactive templates invoked by user choice

NameDescription

No prompts

Resources

Contextual data attached and managed by the client

NameDescription

No resources

Deploy Server
One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

TDQS

B3.3/5.0

Scored across 8 tools

Disambiguation4/5

The tools generally target distinct resources and actions, but the three table-oriented tools (list by schema, fuzzy name search, and details) could be confused at a glance despite clear descriptions. Job-related tools are clearly separated between listing, details, and runs.

Naming Consistency4/5

Most names follow a consistent kebab-case get-<resource> pattern, with only find-tables-by-name deviating in verb choice. The convention is still readable and predictable overall.

Tool Count5/5

Eight tools are well-scoped for a read-only Unity Catalog and jobs exploration server. Each tool covers a distinct browsing or detail-retrieval need without excessive surface area.

Completeness3/5

The surface supports catalog, schema, table, and job discovery plus details and runs, but it is entirely read-only and lacks operations such as creating/updating/deleting assets, triggering jobs, or accessing permissions/lineage. These gaps limit it to exploration workflows rather than full lifecycle management.

Maintenance

ActivityMaintained
ResponsivenessNo recent community issues

Resources