Databricks MCP Server: Tools, Setup, and Governing Agent Access

It is a family of managed Model Context Protocol endpoints exposed from a Databricks workspace, each with its own URL: Unity Catalog functions, the system AI Python interpreter, Genie spaces, SQL, and vector search. The URLs live under Agents > MCP Servers, each registered separately.

It depends on the endpoint. A Unity Catalog functions endpoint exposes the functions in one schema; Genie gives read-only natural-language querying of one space; SQL executes SQL; vector search does similarity search over one index; system AI runs Python. Once authorized, the full list appears on the Tools tab, where each can be enabled, disabled, re-described, or annotated.

Yes, with scoping. The two Databricks-specific risks are compute spend and write access, both concentrated in SQL and Python. Register endpoints separately, use OAuth2 Authorization Code so Unity Catalog enforces per-user grants, gate execution behind approval with Once validity, and trace every call.

Yes. TrueFoundry runs in your VPC, on-prem, air-gapped, or hybrid, so prompts and responses never leave your domain even as you route across many providers.

Yes. It includes an MCP Gateway, an Agent Gateway, and an MCP & Agents Registry with tool-level access control. Agents on LangGraph, CrewAI, AutoGen, or a custom framework can all be governed centrally.

Ja. Das Gateway ist OpenTelemetry-kompatibel und lässt sich in Grafana, Datadog, Prometheus oder Ihren bevorzugten Stack integrieren. Es verfolgt jede Anfrage vom Prompt bis zur Ausführung von Tools und Modellen, sodass Sie eine einheitliche Protokollierung erhalten, ohne Ihre bestehenden Systeme entfernen zu müssen.