Skip to main content
Glama
smaheshwari-ux

Databricks MCP Proxy

by smaheshwari-ux
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Remote

Server Configuration

Describes the environment variables required to run the server.

NameRequiredDescriptionDefault
DATABRICKS_HOSTYesYour Databricks host URL (e.g., https://dbc-XXXXX.cloud.databricks.com)
DATABRICKS_APP_URLYesYour Databricks MCP app URL (e.g., https://your-mcp-app.databricksapps.com)

Instructions

Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.

This server publishes no instructions, or was last inspected before Glama recorded them.

Capabilities

Server capabilities have not been inspected yet.

Tools

Functions exposed to the LLM to take actions

NameDescription
authenticateA
Authenticate with Databricks using OAuth U2M flow.
Opens a browser for authorization.
Uses DATABRICKS_HOST and DATABRICKS_APP_URL from app.yaml or environment.
list_databricks_toolsA

List all available tools on the remote Databricks MCP server. Must authenticate first.

call_databricks_toolA
Call a tool on the remote Databricks MCP server.

Args:
    tool_name: Name of the tool to call (use list_databricks_tools to see available tools)
    arguments: Arguments to pass to the tool

Prompts

Interactive templates invoked by user choice

NameDescription

No prompts

Resources

Contextual data attached and managed by the client

NameDescription

No resources

Deploy Server
One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

TDQS

A3.8/5.0

Scored across 3 tools

Disambiguation5/5

Each tool has a clearly distinct purpose: authenticate handles OAuth authorization, list_databricks_tools enumerates available remote tools, and call_databricks_tools executes those remote tools. There is no overlap or ambiguity between these three functions.

Naming Consistency4/5

The naming follows a consistent snake_case pattern throughout (authenticate, call_databricks_tool, list_databricks_tools). However, there is a minor inconsistency: two tools use plural 'tools' while one uses singular 'tool', which slightly reduces perfect consistency.

Tool Count3/5

With only 3 tools, this feels thin for a Databricks proxy server. While the tools cover authentication, discovery, and execution basics, the count is borderline minimal for a comprehensive proxy interface to a complex platform like Databricks.

Completeness4/5

The toolset provides a complete proxy workflow: authenticate to establish connection, list tools to discover capabilities, and call tools to execute operations. The only minor gap is that it relies entirely on the remote Databricks server for actual functionality, but as a proxy this is appropriate.

Maintenance

ActivityInactive
ResponsivenessNo issues

Resources