Name: Unity Catalog MCP Server
Author: ognis1205

LABSCO SUMMARY

Your governed functions, callable as tools.

The four management calls are not the point. The point is that whatever your team has already registered in Unity Catalog shows up as callable tools, so the governed list and the model's tool list stay the same list.

What it is

A Unity Catalog MCP server. It exposes the Unity Catalog Functions registered under a catalog and schema as MCP tools directly, alongside four predefined calls for listing, reading, creating and deleting those functions.

What you get

All Unity Catalog Functions in the configured catalog and schema, usable as tools
The functions in that catalog and schema, listed
One function's details read by name
A function created from a Python script and registered
A function deleted

Requirements

A Unity Catalog server plus the catalog and schema to work in — those three are required; an access token and a verbosity level are optional. Values can come from CLI options or a .env file, and it runs through uv. The project marks function creation experimental and expects that API to change.

Setup effort

Build from source — git clone https://github.com/ognis1205/mcp-server-unitycatalog.git

See installation options

USE CASES

01

Letting a model use functions your team already governs

Registered Unity Catalog Functions appear as tools without wrapping each one by hand.

02

Seeing what a schema offers

List the functions under the catalog and schema before wiring anything up.

uc_list_functions

03

Checking what a function actually takes

Read one function's details by name.

uc_get_function

04

Adding a function from the conversation

Register a Python script as a function — an API the project marks experimental.

uc_create_function

05

Cleaning up

Delete a function that is no longer used.

uc_delete_function

4 tools

Listed in project docs. Your client may show a different list.

uc_list_functions

uc_get_function

uc_create_function

uc_delete_function

BEFORE YOU INSTALL

What to know first

Tools you get

4 tools named in the project's documentation. Every Unity Catalog Function registered in your chosen catalog and schema also appears as its own tool, so the total grows with your catalog. Switching catalog or schema requires a restart; uc_create_function is experimental.

Where it runs

All 4 documented setups run the server on your machine.

INSTALLATION

Connect your client

You clone and build this one yourself.

Server setup

TERMINAL

git clone https://github.com/ognis1205/mcp-server-unitycatalog.git
cd mcp-server-unitycatalog
docker build -t mcp/unitycatalog .

MCP Clients

Claude Desktop — uv, Cline — uv

JSON

{
  "mcpServers": {
    "unitycatalog": {
      "command": "uv",
      "args": [
        "--directory",
        "/<YOUR_LOCAL_GIT_REPOSITORY>/mcp-server-unitycatalog",
        "run",
        "mcp-server-unitycatalog",
        "--uc_server",
        "<YOUR_UNITY_CATALOG_URL>",
        "--uc_catalog",
        "<YOUR_CATALOG_NAME>",
        "--uc_schema",
        "<YOUR_SCHEMA_NAME>"
      ]
    }
  }
}

Claude Desktop — Docker, Cline — Docker