MCP
Recent items mentioning MCP across the Databricks ecosystem — releases, news, videos, and community Q&A. Updated hourly.
The Genie One Model Context Protocol (MCP) server is now generally available, enabling external AI agents to access unified, governed business context across structured and unstructured data grounded in Genie Ontology 410. Databricks also expanded third-party tooling by introducing Meta’s ads MCP server to the Databricks Marketplace under Unity Catalog and Unity AI Gateway governance 58, alongside support for integrating custom MCP servers into enterprise agent workflows 9.
Generated daily from the 10 most recent items mentioning MCP. Click any [N] to jump to the source.
We wrote about this
- Genie One MCP server: setup and migrationHow to connect Claude Code, Claude, Cursor and ChatGPT to the GA Genie One MCP server, and what to change before the Beta endpoint sunsets on 31 October.14 min read
- Databricks put agent skills in Unity Catalog, and gave them two namesA skill is now a catalog object you grant like a table. What the Beta does, the download-versus-live decision it forces, and why the docs cannot decide what to call it.6 min read
What’s new in Databricks - September 2026?
Databricks shipped the following major GA launches in September 2026: 👉 Spark Declarative Pipelines (SDP): Lakeflow Spark Declarative Pipelines now feature structured maintenance windows for continuous runs, zero-reprocessing migrations (import_checkpoint), multi-source append flows, and explicit cascade deletion (cascade: true) for Unity Catalog tables. 👉Governance and ABAC Security: Metastore-level Attribute-Based Access Control policies and explicit DENY rules are now GA in Unity Catalog, automatically enforcing data protection and access rules across all present and future catalogs. 👉Connectors and Data Applications: Lakeflow Connectors reached GA for Anaplan, Anysphere, and Celigo, while Genie Ones MCP server was officially made generally available for AI assistant workflows. Full article 👉 https://community.databricks.com/t5/product-platform-updates/what-s-new-in-databricks-september-2026/ba-p/173896 submitted by /u/Youssef_Mrini [link] [comments]
What’s new in Genie One — September 2026 update ?
Databricks has introduced significant feature upgrades to Your favourite AI Co-worker: Genie One , expanding its web connectivity, third-party integrations, workspace accessibility and interactive steering controls. Integrations & Native Tooling Databricks-Provided MCP Connectors : Genie One and Genie Code natively support Model Context Protocol (MCP) connectors for tools like Google Drive, Gmail, Google Calendar, Microsoft 365, Atlassian, Slack, and GitHub. Public Web Search : Genie One can autonomously search the live web for up-to-date documentation, market trends, or release notes, providing clickable source citations. PowerPoint Support : Upload and analyze .pptx presentation files directly inside conversations. Multi-File Skills (Beta): Custom skills support nested file structures up to 3 folders deep and 50 text files/folders per skill. Real-Time Interaction & Memory Controls Backend Steering: Send real-time guidance or correction prompts to Genie One while it is generating an answer without waiting for execution to finish. Memory Confirmation Prompts (Beta) : When Genie One detects relevant facts or preferences, it prompts you to confirm, edit, or reject the suggestion before saving it to long-term memory. Pinned Chats: Pin important or active conversation threads to the top of the sidebar. Enterprise Access & Mobile Enhancements Account-Only User Access: Enterprise users registered in an Identity Provider (IdP) can access account-level Genie One without needing workspace assignments or consumer licenses. Mobile MCP Write Actions (Beta) : The Genie mobile app supports interactive write operations via connected MCP tools. Scheduled Task Push Notifications (Public Preview): Receive iOS push notifications for scheduled Genie tasks directly on mobile devices. Push notifications . The Takeaway: Transforms Genie One into an enterprise-wide AI assistant that connects natively to third-party tools, supports real-time steering, and expands access beyond individual workspace boundaries Full article 👉 https://personal.nextgenlakehouse.com/whats-new-in-genie-one-september-2026-update-347c0c08e8b7?postPublishedType=initial submitted by /u/Youssef_Mrini [link] [comments]
Databricks Genie Ontology Explained | Demo with Databricks Product Manager
Hey everyone! Elise Georis (PM at Databricks) partnered with me to do a 35-min deep-dive (chat + demo) on Genie Ontology. We covered a lot of ground and hope you enjoy learning more about it. Some of the topics covered: -Modeled ontology: governed metric views, Pages, and domains. -Learned ontology: snippets extracted from existing assets and how teams use them. -OntoRank: authorship, popularity, and source authority. -Text-to-SQL, Model Context Protocol (MCP) connectors, and search. -Source permissions, personal memory, citations, and tool governance. -Benchmark questions, domain experts, certified assets, and rollout evaluation. -Genie Ontology best practices -Much more! PS: I really appreciate your honest feedback. Knowing what really hits home for you in this video and/or what you feel the video could have done better helps me serve you better through my content! submitted by /u/JosueBogran [link] [comments]
ReleasesJev, OpenAI Dots, DevDay, and Genie One! | AI Newsround - September 2026
The video covers the rise of Jev and other system one decision-making models that output typed probabilities instead of free text for enterprise workflows. It also highlights OpenAI DevDay announcements including persistent agents called dots, the general availability of the Genie one Model Context Protocol, and several new model releases from Anthropic and OpenAI.
Announcement | Meta’s ads MCP server comes to Databricks
MLflow 3.17.0
MLflow 3.17.0 introduces fine-grained access control for runs and traces, links evaluation metrics directly to managed datasets, and adds support for Databricks Unity Catalog model service resources. Self-hosted SQL tracking servers require a coordinated schema migration via mlflow db upgrade with all writers stopped, as rolling deployments are not supported.
What changed on Lakenaut after your feedback, and the site is now an MCP server you can plug into Claude
First of all, I really want to thank you everyone commented my latest post and encourage me to keep update and mantain the website. For the ones who miss my post is this one (for reference): https://www.reddit.com/r/databricks/s/S06gTMmm2P A few of you wrote in over the last two weeks, and most of it is live now. The short version, then one bigger thing. From the feedback "Too many categories, the docs' hierarchy is clearer." The sidebar groups now follow the Databricks documentation's domains (Platform & governance, Data engineering · Lakeflow, Data warehousing & BI, AI & ML), while each area keeps the name the workspace menu gives it. The sidebar is contextual: the doors are always there, the tree opens only where you are. "Finishing a page and moving on is one gesture." It is: Mark as done and Done, next sit together at the foot of every concept. "I want to know what moved." Every concept, area, path and roadmap now opens with a "What changed, and when" box, and /changes/ is the whole log by day: which page, what was done, and whether a person did it by hand or accepted a correction the agent drafted after the documentation changed. Every end-of-support row has its own address now, and search lands on it instead of on the list. A fifth way through the material is taking shape: practices, decision pages filed on the well-architected pillars. When to pick a thing, for whom, what choosing wrong costs. The first one is in draft. The bigger thing: an MCP server, no key Put the MCP URL (page below) into Claude, ChatGPT, Cursor or Claude Code and the assistant reads the published site instead of guessing: 170+ concepts, 8 paths, 5 roadmaps, the news, the resources, and the platform tables (what is in preview, what was renamed, what is ending). Thirteen read-only tools, 60 calls a minute per address, every answer links back to the page it came from. How to connect it: https://lakenaut.dev/developers/ Two questions If you plug it into an assistant, what is the first thing you ask it? I want to know whether people reach for prep, for "what is in preview", or for something I have not thought of. Is there a kind of page you keep wishing existed? The practices came from one comment. The next kind could come from yours. Again, thank you and let's connect! submitted by /u/imthenitto [link] [comments]
Meta’s ads MCP server comes to Databricks: Put your customer intelligence to work in advertising campaigns
Meta’s ads MCP server is now available in the Databricks Marketplace, allowing marketers to use natural language in Genie to evaluate campaign performance alongside governed business data. Administrators can control access to the connection through Unity Catalog, with Unity Gateway governing tool calls and recording audit logs.
EventsDemo: Building a Governed AI Agent with Unity AI Gateway
This video demonstrates how to build, update, and govern a store operations AI agent using Databricks Agent Bricks and the Unity AI Gateway. The tutorial highlights integrating custom Model Context Protocol servers, recording execution traces with MLflow, and enforcing security policies and budget controls.
Problems with UC MCP connection
We built a supervisor agent where one of the tools is the native databricks MCP connection (which is in beta). Today, the agent doesn’t work. Removing the MCP tool fixes it, so it’s definitely that. The agent response just says “received an invalid and unexpected value from the API: undefined” Anyone else having problems suddenly with the MCP server? I’m able to hit the target MCP URL locally no problem. And even test the UC MCP in databricks successfully. So it’s something about the handshake between MCP and the supervisor agent submitted by /u/pboswell [link] [comments]
Genie One MCP is now GA
The Genie One MCP server is now GA. It exposes Genie One over MCP, allowing any agent to communicate with Genie One as a peer agent. The MCP exposes tools for asking questions to Genie One, getting query results, checking on incremental progress, and steering responses. These capabilities allow you to integrate Genie One into whatever agent you want without changing your workflow. And you get all of the semantics built-in instead of having to use raw SQL APIs with fragmented skills/stale markdown repos/additional semantic layers like we used to with ai devtools. Here are the docs: https://docs.databricks.com/aws/en/agents/mcp/genie-mcp I've seen some pretty cool use cases with integration into ChatGPT/Claude, but also headless agent workflows where you want to delegate the data questions to Genie One so it can use agents/ontology. Interested in folks' thoughts on the right/wrong use cases for this feature. submitted by /u/lakehouse_vacation [link] [comments]
The Genie One MCP is now Generally Available
The Genie One MCP server is now generally available, bringing trusted insights across structured and unstructured data into any AI agent workflow. Grounded in Genie Ontology, it provides agents with governed access to unified business context across tables, documents, and tools to reduce conflicting answers and support queries, visualizations, and citations.
What’s new in Databricks - August 2026
Databricks shipped many major Generally Available features in August 2026. Here is the breakdown of what just landed: 🚀 Unity AI Gateway Enterprise AI governance layer covering model access, Model Context Protocol (MCP) management, and cost observability. 🔒 Role-Based Access Control (RBAC) Switch to scoped, temporary role assumptions instead of dealing with permission bloat. 🔑 Secrets in Unity Catalog Unified security secrets are now governed, 3-level namespace securable objects. ⚙️ Serverless Compute Access Control Granular admin controls over who can trigger serverless workloads across your organization. ⚡ Lakebase Postgres APIs & LTAP Direct Writes Accelerated synced-table loads and improved transactional data integration. 🤖 Genie Agent Upgrades Official GA releases for both the Agent mode API and Full-page Genie Code view. submitted by /u/Youssef_Mrini [link] [comments]
Multiple Databricks Genie MCP connectors in one Claude workspace collapse into a single shared connector, anyone solved this?
We're connecting Claude (Cowork/Claude Desktop) to several separate Databricks workspaces, each with its own Genie space. Running into a platform-level snag and hoping someone's hit this before. Setup: each workspace exposes the standard Genie MCP endpoint ( https:// /api/2.0/mcp/genie ). We add each as its own connector in Claude so we can ask natural-language questions against the right workspace's data. Problem 1, generic connectors are indistinguishable: every Genie MCP server reports the same tool names and the same generic description, regardless of which workspace it's pointed at. Claude has no way to tell them apart from metadata alone, so it either has to probe each one (asking a neutral "what workspace is this?" question and checking the returned deep_link ) before it can route a question correctly, or it guesses wrong. Problem 2, trying to fix it with named connectors backfires: we tried building a Claude plugin that declares each of the seven as a distinct, fixed-name MCP server (e.g. genie-workspace-a , genie-workspace-b , ...), hoping deterministic names would remove the need for probing entirely. Turns out Claude's client recognizes Databricks Genie as a "verified" connector type in its directory, and collapses all seven fixed-name declarations into a single shared authorization instead of keeping them independent. Authorizing one silently becomes "the" Genie connection, and the others just reflect that same state rather than getting their own. Problem 3, working around the collapse trades one problem for another: we found that changing the declared URL slightly (adding a harmless query param) makes the client stop recognizing it as the verified type, which does force it down the plain custom-connector path and keeps it independent. But then it needs an actual registered OAuth client ID against that Databricks workspace, since it no longer gets whatever implicit OAuth handling the verified integration has. That means registering an app per workspace in Databricks/Azure just to get back to where the plain manual setup already was, more infrastructure, not less. So right now we're back to manually-added generic connectors plus a routing skill that probes and caches per conversation, which works, but costs a lookup the first time each workspace is used per session, and never scales cleanly as we add more workspaces. Has anyone gotten multiple Genie MCP connections into the same Claude account/org without them colliding into one shared authorization? Is there a way to deploy or configure the Genie MCP endpoint itself so each workspace reports distinguishable tool names or descriptions, rather than relying on the client to differentiate them? Btw, in Codex/chatgpt this is not an issue, because we can edit the description/name, and it automatically discovers the right plugin to use. It seems this is a very claude thing issue submitted by /u/Akroma188 [link] [comments]
NewsMonitor AI Model Usage & Spending on Databricks
Databricks AI Gateway enables admins to select which MCP server tools are exposed to agents and view their governance configuration. Usage tracking is automatically enabled to provide centralized visibility into model token consumption and spending metrics.
Building Governed Agents with Databricks
Databricks extends its Unity Catalog governance layer to AI agents, MCP servers, and tools to solve "agent sprawl" by providing centralized discovery, access controls, and audit logging. The system allows developers to quickly build agents while IT teams enforce fine-grained policies, manage credentials, and track end-to-end request and response lineage.
From Primitives to Production: How Anthropic Builds Agents
Anthropic defines agents as LLMs in loops with tool access, leaning on model intelligence over rigid workflows, and uses domain-specific skills, MCPs, and evals to build effective agents across sectors. A demo showed a site reliability agent autonomously identifying a database pool issue, fixing the code, and generating a postmortem.
NewsBuilding Agents on Databricks with Custom Apps and Omnigent
This video demonstrates how to build, update, and govern custom AI agents on Databricks using Agent Bricks, Databricks Apps, and Omnigent. The tutorial shows how to integrate Model Context Protocol servers, track execution with MLflow traces, schedule automated agent tasks, and manage security policies through Unity AI Gateway.
What is Tool Calling?
Tool calling transforms basic chatbots into action-oriented AI agents by executing a structured loop to interact with external tools, APIs, and systems. Databricks Agent Bricks provides a governed environment to build these agents grounded in enterprise data, featuring native support for the Model Context Protocol and Unity Catalog governance.
TutorialsBuilding Agents on Databricks with Custom Apps and Omnigent
The video demonstrates how to build, update, and govern a store operations AI agent on Databricks using Model Context Protocol servers and custom apps. It shows how to use Omnigent and CodeX to add new context and tools, redeploy the application, and manage governance and traces through the Unity AI gateway.
MLflow 3.15.0 introduces an MCP Registry for registering and sharing Model Context Protocol servers, enhances the Assistant with multi-provider LLM support and per-session token usage tracking, and enables proxy-less artifact transfers via presigned URLs to reduce server load and timeouts on large files. Additional improvements include sharable Runs table views, multi-modal image attachments for LLM judges to evaluate vision tasks, and numerous bug fixes across tracing, evaluation, gateway, and UI components.
NewsAI Dev Kit 2.0: Databricks AI Tools
AI DevKit 2.0 moves Databricks' agentic coding tools from standalone installation to the official Databricks Agent Skills repository, now installed via the Databricks CLI with improved features and consolidated skills. Users must uninstall the old AI DevKit version and reinstall from the new location, with the MCP server available as a separate optional component.
Why R&D Data Belongs in the Lakehouse - and Why Agents Need It There
Cellcentric built an industrial Data Hub on Databricks using Unity Catalog and Lakehouse Federation, establishing a governed context layer that unifies scattered R&D data for employees and AI agents via an MCP server. By treating documentation as a first-class quality metric, this architecture delivers AI-ready data products that accelerate complex R&D investigations from weeks to days.
Empower your healthcare agents with ready-to-use MCP on Databricks Marketplace
Databricks Marketplace now offers ready-to-use biomedical and clinical Model Context Protocol (MCP) servers from partners like Climb and Atropos Health, empowering healthcare agents. Easily build and deploy bespoke agents to production, leveraging a securely governed, centralized MCP Catalog that also supports your own custom MCP servers or data.
Whether MCP server support for Genie is available in our workspace/region for free version.
I built an open-source Text-to-SQL agent for Databricks Unity Catalog
I've been working on an open-source side project called [Mega Djinn](https://github.com/ocelma/mega-djinn) to solve the *"where is this data?"* problem, and I wanted to share it with you all. **1. What it does** You ask a natural language question (e.g., *"Which web pages kept readers engaged the longest last month?"*) and the agent handles the rest: 1. *Table Discovery*: Automatically finds the relevant tables and schemas inside Databricks Unity Catalog. 2. *Governance Enrichment*: (Optional) Pulls business definitions and approved SQL snippets from Alation to ground the prompt. 3. *Human-in-the-Loop*: Generates optimized SQL and displays it for your review before execution. 4. *Execution*: Runs the query on Databricks (via CLI or MCP server), returns the results, and generates an HTML report. 5. *Memory*: Saves successful queries back to the knowledge base so your team can reuse them. **2. Why I built it** Our data teams were drowning in repetitive ad-hoc requests from PMs and business stakeholders; people who have critical data questions but not enough SQL background. # The ultimate goal is to give non-technical users direct access to data insights without always depending on a data analyst. Mega Djinn is much simpler and lightweight than Vanna: it uses your existing data governance metadata (UC schemas + Alation definitions if available) to ground the context, making the generated SQL accurate to your specific business logic. **3. The Tech Stack** * Core: Python + Databricks SDK * LLM Integration: Built as a Claude Code skill. Also works via Cursor, Codex, and Gemini CLI. [https://github.com/ocelma/mega-djinn](https://github.com/ocelma/mega-djinn) I would love to get your feedback, feature requests, or thoughts on how you handle text-to-SQL governance!
Genie UI MCP Server Connection Issue
AI-ready data in practice: What dbt Semantic Layer and dbt's MCP server and agent skills do for your team
dbt's Semantic Layer, MCP server, and agent skills now provide AI with essential business context. This enables your team to move beyond just clean data to truly AI-ready data in practice.
Stop rogue AI: How Unity Catalog secures your agent actions
Unity Catalog now governs external Model Context Protocol (MCP) tools, allowing teams to restrict agent actions in real time using Unity AI Gateway. By applying SQL-based service policies and logging full payload data to Delta tables, you can prevent unauthorized tool executions and maintain a complete audit trail.
TutorialsMCP Servers + OBO Auth: The Formula for Context-Aware Agents
The video demonstrates how to build an AI agent in Databricks that provides personalized responses by integrating user-delegated actions through Model Context Protocol (MCP) servers. It walks through setting up Unity Catalog functions, external MCP tools like web search, and custom MCP servers to access internal APIs, all while maintaining user context for relevant information retrieval.
5 dbt MCP server patterns that work in production
Learn five dbt MCP server patterns that work in production, including one that doesn't behave as expected. These patterns are drawn from real-world production use cases.
NewsDatabricks AI Dev Toolkit: Empowering Workspace Users
The Databricks AI Dev Toolkit provides workspace users, even those unfamiliar with IDEs, access to AI tools via a Databricks app serving an MCP server. It supercharges the Genie code agent with MCP tools to automate resource creation.
NewsDatabricks Apps vs Model Serving: Authentication, Cost, and Performance Compared
Databricks Apps are now the recommended first choice for deploying agents due to their flexibility in handling full-stack applications with multiple components, offering faster iteration and local testing compared to Model Serving. Model Serving remains suitable for use cases prioritizing high QPS, governance features like AI Gateway, inference tables, and guardrails, or when scaling to zero is acceptable for cost optimization.
MLflow 3.11.1 introduces AI-powered issue detection in traces, AI Gateway budget alerts and spending controls, trace graph visualization, native Databricks gateway provider, and pickle-free model serialization. TypeScript SDK packages are now @mlflow-scoped and LiteLLM is no longer required for GenAI evaluation.
TutorialsDatabricks AI Dev Kit Demo - Install, DataGen, SDP, Dashboard
The video demonstrates installing the Databricks AI Dev Kit on a Mac, then uses it to generate synthetic data, create serverless Spark declarative pipelines for a medallion architecture, and build a Databricks dashboard based on the generated data. It highlights how the AI Dev Kit leverages skills and an MCP server to automate these development tasks.
ReleasesIntroducing Databricks AI Dev Kit - Skills, MCP server, Builder App
The Databricks AI Dev Kit provides agent skills, an MCP server, and a Builder App to enhance AI-driven development on Databricks. It allows users to integrate AI coding tools with Databricks best practices, extending LLM capabilities through specialized functions and offering a chat-based interface for building applications.
5 Tips to Get More Out of Your Claude Code with MLflow
MLflow now offers an MCP server, CLIs, and Skills to extend Claude Code, enabling you to trace tokens and monitor tool usage. These five tips will help you transform your Claude coding agent into a transparent and controllable workflow.
NewsTurbo-Charge your Agents with instant MCP in Databricks
The video demonstrates how to use Model Context Protocol (MCP) in Databricks to give AI agents "superpowers" by enabling them to interact with various tools and data sources. It shows how to easily set up MCP servers within Databricks to connect agents to Unity Catalog functions, vector search, external APIs, and even marketplace MCP services, all without extensive coding.
NewsClaude Code: 5 Essentials for Data Engineering
The video introduces five essential concepts for using Claude Code in data engineering: the cloud.mmd file for core project information, skills for packaging expertise, commands for predefined prompts, sub-agents for focused tasks, and Model Context Protocol (MCP) for standardized tool interaction. These components help manage context and memory for effective AI-enhanced development.
NewsDatabricks: What’s new in September 2025? #databricks
Databricks now supports geospatial data types (geography and geometry) with new functions for visualization and spatial operations, and introduces serverless GPU clusters for distributed GPU code execution. The platform also offers enhanced notebook features like side-by-side editing and a notebook-specific search, along with new options for managing serverless environments, SQL warehouses, and access requests in Unity Catalog.
NewsAI Agents in Action: Structuring Unstructured Data on Demand With Databricks and Unstructured
Unstructured's MCP server enables LLMs to directly transform unstructured data (PDFs, documents, images) into JSON using natural language commands instead of code. Their agentic approach retrieves data on-demand from sources like S3 and SharePoint, reducing costs compared to traditional full data ingestion into vector databases.
EventsData + AI Summit Keynote Day 1
Databricks introduced Lakebase, a serverless Postgres database with storage-compute separation and instant branching designed for AI agents, alongside Databricks Apps for deploying secure production data applications with built-in governance. The company unified support for both Delta Lake and Apache Iceberg formats through Unity Catalog while emphasizing AI-driven democratization through natural-language data access and intelligent coding agents.