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.
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.
- 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
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.
One command — docker build -t mcp/unitycatalog .