MCP.so
ログイン

MCP Server for Databricks Interaction

@ZubeyirOflaz

基本情報

カテゴリ

その他

最終更新

ライセンス

LGPL-2.1 license

トランスポート

stdio

作者

ZubeyirOflaz

MCP Server for Databricks Interaction について

概要はまだありません

MCP Server for Databricks Interaction の設定

以下の設定を使って、このサーバーを MCP 対応クライアントに追加してください。

{
  "mcpServers": {
    "mcp_server_for_databricks": {
      "command": "uv",
      "args": [
        "venv",
        "#",
        "Create",
        "a",
        "virtual",
        "environment",
        "(e.g.,",
        ".venv)"
      ]
    }
  }
}

MCP Server for Databricks Interaction のツール

ツール一覧はまだありません

この掲載には表示できるツール一覧がまだありません。サーバーにツールがないという意味ではありません。対応機能はプロジェクトのドキュメントをご確認ください。

ツールは README から自動的に抽出されます。メンテナーは ## Tools という見出しの下に記載することで、このタブに反映できます。

概要

What is MCP Server for Databricks Interaction?

The MCP Server for Databricks Interaction acts as an interface to a Databricks workspace, exposing tools to query and retrieve metadata about schemas, tables, table samples, and job results via MCP commands. It is built with FastMCP and uses the Databricks SDK and CLI for backend communication, targeting users who need simplified metadata retrieval through an MCP interface.

How to use MCP Server for Databricks Interaction?

Install prerequisites (Python 3.x, uv, and the latest databricks-cli from the official site), clone the repo, create a virtual environment with uv venv, run uv sync, and execute python init.py to configure the workspace URL, authenticate via OAuth, select a SQL Warehouse, and set the sample size. Then add the server to an MCP client (e.g., Cursor) by specifying the uv command with arguments pointing to main.py in the project directory.

Key features of MCP Server for Databricks Interaction

  • Retrieves schemas and tables in a specified catalog
  • Returns detailed table metadata with column info and sample data
  • Provides schema metadata including comments and table details
  • Fetches results from the latest job run (or last failed run)
  • Uses Databricks CLI OAuth profile for authentication

Use cases of MCP Server for Databricks Interaction

  • Explore all schemas and tables within a catalog for data discovery
  • Inspect table structure, comments, and sample rows for schema understanding
  • Quickly retrieve the output of the most recent Databricks job run
  • Debug by filtering for the last failed run of a specific job

よくある質問

1

What are the prerequisites?

Python 3.x, uv (package installer), and the latest databricks-cli (version 0.18 from PyPI is too old; install directly from Databricks).

2

How is authentication handled?

The server uses a Databricks CLI profile named `mcp_server_for_databricks`. The `init.py` script initiates an OAuth login flow; the server obtains tokens via subprocess calls to `databricks auth login` and `databricks auth token`.

3

What MCP tools are provided?

Four tools: `get_schemas(catalog)`, `get_table_sample_tool(catalog, schema_name, table)`, `get_schema_metadata(catalog_name, schema_name)`, and `get_job_run_result(job_name, filter_for_failed_runs=False)`.

4

How is the connection configured?

The `init.py` script saves the workspace URL, selected SQL Warehouse ID/name, and sample size into a `config.yaml` file. The server reads this file on startup.

5

Can I use this server with Cursor IDE?

Yes. In Cursor Settings > Features > MCP, add a new server with command `/path/to/uv` and args including `--directory /PATH/TO/THIS/REPO run main.py`.

コメント

「その他」の他のコンテンツ