Skip to main content
Glama
JustTryAI

Databricks MCP Server

by JustTryAI

Related Servers

Alternatives to Databricks MCP Server

No user-submitted related servers found.

    Related Servers

    • A
      license
      B
      quality
      D
      maintenance
      A fixed Model Completion Protocol (MCP) server that enables LLMs like Claude Code to interact with Databricks functionality including clusters, jobs, notebooks, and SQL execution through natural language commands.
      19
      5
      MIT
    • F
      license
      Not graded
      quality
      C
      maintenance
      A governed MCP server exposing Databricks operations as tools for jobs orchestration, SQL execution, notebook creation, Unity Catalog governance, lineage, clusters, and DLT pipelines, with safety features like dry-run and audit logging.
      -
    • A
      license
      Not graded
      quality
      C
      maintenance
      This is a Model Context Protocol (MCP) server for executing SQL queries against Databricks using the Statement Execution API. It enables AI assistants to directly query Databricks data warehouses, analyze database schemas, and retrieve query results in a structured format
      43
      MIT
    • A
      license
      Not graded
      quality
      D
      maintenance
      A server that provides tools to interact with Databricks for cluster, job, notebook, DBFS, and SQL management through natural language interfaces like Claude-Desktop and Cursor.
      GPL 3.0

    TDQS

    B3.2/5.0

    Scored across 11 tools

    Disambiguation5/5

    Each tool has a distinct purpose with clear boundaries: cluster management (create, get, list, start, terminate), SQL execution, notebook operations (export, list), file listing, and job operations (list, run). No overlapping functionality exists, making tool selection straightforward for an agent.

    Naming Consistency5/5

    All tools follow a consistent verb_noun pattern (e.g., create_cluster, execute_sql, list_files) using snake_case throughout. This predictable naming convention enhances readability and usability for agents.

    Tool Count5/5

    With 11 tools, the server is well-scoped for Databricks operations, covering clusters, SQL, notebooks, files, and jobs. Each tool serves a clear purpose without redundancy, making the count appropriate for the domain.

    Completeness4/5

    The toolset provides strong coverage for core Databricks workflows, including cluster lifecycle, SQL execution, notebook/file management, and job operations. Minor gaps exist, such as missing notebook creation or job update tools, but agents can work around these with available operations.

    Maintenance

    ActivityInactive
    ResponsivenessNo issues