Databricks Genie MCP Migration: What to Change Before November 30

Databricks is retiring the beta Genie MCP endpoint on November 30, 2026. Existing integrations need the Unity Gateway URL, the new OAuth scope and the right execution permission before that deadline. The November 11 Genie launch makes this a migration task, not just another connector to try.

The three changes an existing client needs

The Genie One MCP documentation says requests to the beta endpoint will fail after its end-of-life date. Tool names and arguments remain unchanged, so focus first on connection configuration rather than rewriting your agent.

Configuration	Beta	Generally available endpoint
URL path	/api/2.0/mcp/genie	/ai-gateway/mcp-services/system.ai.genie_one_mcp?o=<workspace-id>
OAuth scope	genie	ai-gateway
MCP execution access	Review existing access	Callers need EXECUTE on system.ai.genie_one_mcp

Use your actual workspace hostname before the new path. Keep an inventory of clients and scheduled jobs that still use the old endpoint, then verify each one under its real caller identity. A successful administrator test does not establish that ordinary users can connect.

Check permissions before changing the application

Databricks' MCP governance guide also requires workspace assignment and the parent USE CATALOG and USE SCHEMA privileges. Tools may need permissions on underlying resources. End users do not need USE CONNECTION; granting it broadly would allow direct connection use outside the MCP's tool selection and policies.

For a failed migration, separate three questions: can the client reach the workspace, can the caller execute this MCP, and can that caller access the requested data? Treating all three as an authentication problem encourages unnecessary permission expansion.

Network restrictions matter too. Databricks recommends context-based ingress for hosted partner clients such as ChatGPT and Claude, rather than manually maintaining their IP ranges. Have the administrator review the intended client path instead of disabling inbound restrictions to make a test pass.

New plugins change where the question starts

The November 11 plugin announcement brings Genie into ChatGPT, Claude, Microsoft Copilot Cowork and Grok Bot. An external agent can delegate a business question to Genie or request missing context while retaining responsibility for the broader task.

That division is useful. If an assistant is preparing a customer briefing, Genie can supply the governed consumption metric while the assistant handles the document. Installing a plugin should not become an excuse to recreate finance's definitions in another prompt library.

A migration test worth running

Use a small set of questions with answers your team already knows. Include one approved metric, one ambiguous business term, and one request for data the test user must not see. Compare the result, cited definition and permission outcome before making the new connection the default for scheduled work.

Then test a follow-up question in the same conversation. The goal is to catch a connection that authenticates successfully but loses the context needed to interpret the next request. This is a suggested acceptance test, not a report of testing performed here.

Keep the rollout narrow until those checks pass. A working connection is not the same as a correctly scoped connection, and a deadline is a poor reason to combine an endpoint migration with a broad access change.

I’m Paras. I work at the intersection of AI, engineering and distribution.

I help technical teams turn integration changes and complex AI workflows into clear documentation and stories developers can use.

Book a 30-minute call.