MyMCPToolsSubmit Server

Guides8 min read

Best MCP Servers for Databricks Developers in 2026

The top MCP servers for Databricks workflows. From Delta Lake queries to ML model management — supercharge your Databricks data engineering with Model Context Protocol.

By MyMCPTools Team·May 23, 2026

Databricks sits at the intersection of data engineering, data science, and ML engineering. It's a platform where Python notebooks run Spark jobs, SQL analysts query Delta Lake tables, and ML engineers track experiments in MLflow — all in the same environment. The right MCP servers give your AI direct access to all three layers of that stack.

Here are the MCP servers that matter most for Databricks development in 2026.

1. Databricks MCP Server — Direct Platform Access

The Databricks MCP server is the foundation for any Databricks-focused workflow. It gives your AI direct access to your Databricks workspace — clusters, notebooks, jobs, and Unity Catalog — without you having to describe your environment from scratch every time.

Key use cases for Databricks developers:

Query cluster configurations to understand compute resources available
Inspect job definitions and schedule configurations for automation
Navigate the Unity Catalog to understand table ownership and lineage
Read notebook content for code review and refactoring assistance

Best for: All Databricks developers — the non-negotiable foundation of a Databricks MCP stack.

2. Databricks SQL MCP Server — Schema-Aware Query Generation

Writing Spark SQL and Delta Lake queries against the wrong schema is one of the most common errors in Databricks workflows. The Databricks SQL MCP server gives your AI live schema access — table names, column types, partition columns, and Delta table properties.

Key use cases for Databricks developers:

Generate accurate PySpark DataFrame operations with correct column names
Write Delta Lake MERGE statements against actual table schemas
Understand Z-ORDER columns and partition layouts for query optimization
Inspect table history for time travel query generation

Best for: Data engineers writing ETL pipelines and SQL analysts querying Delta Lake.

3. Apache Spark MCP Server — Cluster-Aware Computation

Spark configuration mistakes — wrong executor memory, incorrect shuffle partitions, poorly tuned broadcast joins — are expensive in Databricks. The Apache Spark MCP server gives your AI visibility into your Spark application's execution plan and configuration so it can help you optimize rather than just generate boilerplate.

Key use cases for Databricks developers:

Analyze query execution plans to identify shuffle bottlenecks
Tune Spark configurations for your specific cluster size and workload
Debug partition skew issues by inspecting task-level metrics
Generate optimized DataFrame transformations based on actual data size

Best for: Data engineers optimizing large-scale Spark jobs and pipelines.

4. Filesystem MCP Server — Local Notebooks and Scripts

Not all Databricks development happens in the browser. Many teams develop PySpark libraries, Delta Live Tables pipelines, and Databricks Asset Bundles locally before deploying. The Filesystem MCP server gives your AI access to your local project files alongside the cloud environment.

Key use cases for Databricks developers:

Read local Python library code that gets packaged and uploaded to Databricks
Inspect Databricks Asset Bundle YAML configurations
Review Delta Live Tables pipeline definitions in your local repo
Access shared utility modules across multiple notebooks and jobs

Best for: Databricks developers using local development with Databricks CLI and Asset Bundles.

5. GitHub MCP Server — Version Control for Data Pipelines

Modern Databricks teams version-control their notebooks and pipeline definitions in Git. The GitHub MCP server lets your AI review PRs for pipeline changes, search across your data engineering codebase, and create issues — all within your AI conversation.

Key use cases for Databricks developers:

Review PR diffs for Delta Live Tables pipeline changes before deploying
Search for all places a specific DataFrame transformation pattern is used
Create issues with schema details and query plans attached
Understand pipeline lineage by tracing code history across notebooks

Best for: Databricks teams using Git-backed workspace or Databricks Repos.

6. Brave Search MCP Server — Documentation and API Research

Databricks releases new features frequently — Unity Catalog updates, Delta Lake 4.x features, MLflow improvements. The Brave Search MCP server lets your AI look up current Databricks documentation and runtime release notes without breaking your development flow.

Key use cases for Databricks developers:

Look up Delta Lake API changes between runtime versions
Find Unity Catalog privilege grant syntax for your specific catalog type
Research MLflow experiment tracking APIs for your Databricks Runtime version
Check Photon engine compatibility for specific SQL operations

Best for: All Databricks developers staying current with platform updates.

Recommended MCP Stack for Databricks Developers

Always active: Databricks, Databricks SQL, Brave Search
Pipeline optimization: Apache Spark, Filesystem
Team collaboration: GitHub

The Databricks platform is powerful precisely because it unifies data engineering, analytics, and ML — but that breadth makes context critical. When your AI has live Delta Lake schema access, cluster configuration visibility, and direct workspace connectivity, it shifts from writing generic PySpark patterns to generating queries and pipelines that match your actual data architecture.

Related guides:

Recommended Tools

Better Stack

Free Plan

Get alerted when your APIs, browser tests, payment pipelines, or MCP server dependencies go down. Used by 100K+ developers.

Start monitoring free →

1Password

14-day Free Trial

Store and inject API keys, payment credentials, tokens, and file access secrets into your MCP server configs. Trusted by 150K+ developers.

Try 1Password free →

🔧 MCP Servers Mentioned in This Article

Databricks MCP Server

managed MCP servers that Databricks runs inside your own workspace, which is why there is nothing to install for the common case — you point an MCP client at a workspace URL and authenticate on behalf of the user with an OAuth scope. The hosted endpoints are /api/2.0/mcp/genie and /api/2.0/mcp/genie/{genie_space_id} for natural-language analytics against a Genie space (scope genie, read-only), /api/2.0/mcp/ai-search/{catalog}/{schema}/{index_name} for retrieval over AI Search indexes (scope ai-search; the older /api/2.0/mcp/vector-search/ path still resolves after the rename), /api/2.0/mcp/sql for running AI-generated SQL including writes (scope sql), and /api/2.0/mcp/functions/{catalog}/{schema}/{function_name} for executing SQL tools stored as Unity Catalog functions (scope unity-catalog). All of them prefix the workspace hostname, and because permissions are enforced on-behalf-of the calling user, an agent can only reach the data and tools that user could reach — the reason most teams choose these over a self-hosted server. For self-hosting there is databrickslabs/mcp, an experimental repo whose Unity Catalog server runs locally over stdio via uv and infers its tool list at startup from the UC functions, vector search indexes and Genie spaces in the schema you point it at; it can also be deployed onto Databricks Apps with databricks bundle or databricks apps, where it is reached over Streamable HTTP at a URL that must end in /api/mcp/ including the trailing slash. Two caveats worth knowing before you build on it: Databricks has marked that Unity Catalog server deprecated in favour of the managed servers, and the developer-tools server in the same repo is still labelled under construction and not usable. The separate databricks-mcp package on PyPI is a client-side helper library from databricks/databricks-ai-bridge (OAuth provider and MCP client plumbing for notebooks, Model Serving and local runs), not a server.

Databricks SQL

Query and manage Databricks SQL warehouses and Unity Catalog. Run SQL queries, manage tables, inspect job runs, and analyze lakehouse data via AI.

Apache Spark

Unified analytics engine MCP for Apache Spark. Submit jobs, query DataFrames via Spark SQL, inspect execution plans, and analyze large-scale distributed data.

Filesystem MCP Server

sandboxed read, write, edit, move and search access to an explicit whitelist of local directories, and it is the reference implementation most other filesystem MCP servers are modelled on. Shipped by Anthropic in the official modelcontextprotocol/servers monorepo (89,000+ stars, actively maintained), it is a Node.js server published to npm as @modelcontextprotocol/server-filesystem. The part worth understanding before you install is the access-control model, because there are now two ways to grant directories and they do not compose. Method one is command-line arguments: `npx -y @modelcontextprotocol/server-filesystem /path/one /path/two`. Method two, and the one the maintainers recommend, is MCP Roots — a client that supports the roots protocol sends its roots at initialization, and those roots COMPLETELY REPLACE any directories passed on the command line, then get replaced again on every `notifications/roots/list_changed`. That means allowed directories can change at runtime without restarting the server, but it also means a roots-capable client silently overrides your CLI arguments. If the server starts with no arguments and the client either does not support roots or sends an empty list, initialization throws an error. The tool surface is broad: `read_text_file` (with mutually exclusive `head`/`tail` line windows), `read_media_file` returning base64 image/audio content blocks, `read_multiple_files` which keeps going when individual reads fail, `write_file`, `edit_file`, `create_directory`, `list_directory`, `list_directory_with_sizes`, `move_file`, `search_files`, `directory_tree`, `get_file_info` and `list_allowed_directories`. `edit_file` is the one to learn — it does line-based and multi-line pattern matching with indentation detection and preservation, returns a git-style diff with context, and supports `dryRun: true` so you can preview a change before applying it; the maintainers recommend always running a dry run first. Every operation is refused outside the allowed set, and `list_allowed_directories` is the fastest way to confirm what the server actually believes it can touch.

GitHub MCP Server

authenticated access to the whole GitHub platform — repositories, files, branches, issues, pull requests, Actions runs, security alerts, discussions and notifications — from Claude, Cursor, VS Code, Copilot CLI and any other MCP host. There is no npm package for this server, and that trips up most people who try to install it: `@github/mcp-server` is not published to the npm registry, so any `npx` line you find for it will fail. GitHub ships it three other ways. The easiest is the hosted remote server at https://api.githubcopilot.com/mcp/, which needs no install at all — point an HTTP-transport MCP client at that URL and log in with OAuth (VS Code 1.101+, Claude Desktop, Claude Code, Cursor and Windsurf all support this). The second is the official Docker image ghcr.io/github/github-mcp-server, which is what the copy-paste command on this page runs; on github.com it now performs a browser-based OAuth login on first use and keeps the token in memory only, which is why the published Docker configs map a fixed loopback callback port (-p 127.0.0.1:8085:8085 with GITHUB_OAUTH_CALLBACK_PORT=8085) so the container can receive the callback. Prefer a token? Set GITHUB_PERSONAL_ACCESS_TOKEN instead — it takes precedence over OAuth, and the minimum useful scopes are repo, read:org and read:packages. The third is the native Go binary from the repository's releases, which needs no fixed port for the OAuth flow. GitHub Enterprise Server has no hosted option: use the local server with --gh-host or GITHUB_HOST set to your instance (include the https:// scheme — it defaults to http://, which GHES rejects). Toolsets can be narrowed with GITHUB_TOOLSETS, and an insiders channel is available at /mcp/insiders or via the X-MCP-Insiders header.

Auth required📘✓

Brave Search MCP Server

The Brave Search MCP Server is the official server from Brave that gives AI assistants privacy-first web search through the independent Brave Search API — no tracking, no profiling, and results drawn from Brave's own web index rather than Google or Bing. It exposes five distinct tools that map directly to the Brave Search API endpoints: brave_web_search for general queries with pagination, freshness filters, and safe-search controls; brave_local_search for businesses, restaurants, and points of interest with automatic location filtering; brave_news_search for recent articles and current events; brave_image_search for image discovery; and brave_video_search for finding videos across the web. Authentication uses a single BRAVE_API_KEY (free tier available at brave.com/search/api) or a mounted BRAVE_API_KEY_FILE for Docker-secret setups. Install in Claude Desktop, Cursor, Windsurf, or VS Code with one npx command and choose stdio or streamable-HTTP transport. Because Brave operates its own crawler and index, the Brave Search MCP server is a strong choice for developers who want an alternative to Google-dependent search tools, need reproducible non-personalized results, or care about data privacy in agent workflows — Claude can pull fresh web context, verify facts, and research topics without leaking queries to ad-tech pipelines.

📚 More from the Blog

Best MCP Servers for Developers in 2026: The Complete Guide

Discover the top MCP servers that every developer should know about. From filesystem access to database queries, these Model Context Protocol servers supercharge your AI coding workflow.

8 min read Guides

Best MCP Servers for Data Engineering: Database, ETL & Analytics

Top MCP servers for data engineers and analysts. Connect your AI to PostgreSQL, BigQuery, Snowflake, and more for AI-powered data workflows.

7 min read Tutorials

Getting Started with MCP: A Beginner's Guide to Model Context Protocol

New to MCP? Learn what Model Context Protocol is, how it works, and how to set up your first MCP server in under 5 minutes. Complete beginner's guide.