Use managed analytics servers
Ready-to-use endpoints cover Genie One, Genie Agent, AI Search, Databricks SQL and Unity Catalog functions.
Documentation ↗MCP server / data & analytics / source-linked
Databricks MCP is a governed tool layer for workspace analytics and retrieval. Its useful distinction is managed versus external: Databricks can host Genie, AI Search, SQL and Unity Catalog function servers, while MCP Services register external servers with grants, policies and audit logs.
Identify the implementation and the job it supports.
Databricks MCP is a governed tool layer for workspace analytics and retrieval. Its useful distinction is managed versus external: Databricks can host Genie, AI Search, SQL and Unity Catalog function servers, while MCP Services register external servers with grants, policies and audit logs.
The documented interface, authentication and installation path.
In the workspace, open AI Gateway → MCPs, select a managed server or register an MCP Service, then connect your agent using the workspace URL and required OAuth scope. See the client guide for agent-specific authentication.
Setup reference ↗Concrete capabilities with maintainer sources.
Ready-to-use endpoints cover Genie One, Genie Agent, AI Search, Databricks SQL and Unity Catalog functions.
Documentation ↗MCP Services register external servers as Unity Catalog securables with grants, policies, audit logs and usage tracking.
Documentation ↗Databricks documents discovery, authentication and tool calls from custom agent code before deployment on Databricks Apps.
Documentation ↗What was checked and what was not tested.
Public maintainer documentation and repositories. This is not a hands-on product review.
Setup examples are documented examples. Suggested trials and comparison advice are editorial guidance.
Sources support the adjacent factual statements. A source review does not establish uptime, performance, security or current account eligibility. Read the editorial policy.
A bounded evaluation you can reproduce in your own environment.
Suggested evaluation, not an observed test result.
What to inspect: A workspace-governed retrieval workflow. No Databricks workspace or tool call was tested.
Workflow reference ↗Read these constraints before granting access.
Managed MCP servers are explicitly marked Public Preview; availability and behavior can change.
Boundary reference ↗Access requires a Databricks workspace, Unity Catalog permissions and the matching OAuth scope; these are not generic public endpoints.
Boundary reference ↗Make the expected output explicit before you connect.
A workspace-governed retrieval workflow. No Databricks workspace or tool call was tested.
Keep the task inputs, tool calls, output and any errors together when you evaluate. The trial above is a proposal, not a recorded result.
Specific reasons to choose another route, with the tradeoff shown.
| Alternative | Choose it when | Tradeoff |
|---|---|---|
| Snowflake MCP | Editorial choice: governed data lives in Snowflake Cortex and RBAC. | Snowflake has its own tool limits and OAuth roles. Documentation ↗ |
| MongoDB MCP | Editorial choice: an operational document database needs agent access. | MongoDB focuses on data operations rather than lakehouse governance. Documentation ↗ |
Answers specific to this implementation.
It hosts managed servers, and it can also register external servers through MCP Services or host custom MCPs as Databricks apps.
Documentation ↗
It enforces permissions and manages credentials so an agent reaches only the tools and data granted to it.
Documentation ↗
Maintainer documentation used in this record.