Authenticates with Databricks via OAuth and provides access to remote MCP tools hosted on Databricks, enabling discovery and invocation of Databricks-hosted tools.
Click on "Deploy Server".
Wait a few minutes for the server to deploy. Once ready, it will show a "Started" state.
In the chat, type @ followed by the MCP server name and your instructions, e.g., "@Databricks MCP Proxy list available tools in my Databricks workspace"
That's it! The server will respond to your query, and you can continue using it as needed.
Here is a step-by-step guide with screenshots.
An MCP proxy server that authenticates with Databricks and exposes remote MCP tools.
uv syncRelated MCP server: Databricks MCP Server
Edit app.yaml with your Databricks settings:
env:
- name: DATABRICKS_HOST
value: "https://dbc-XXXXX.cloud.databricks.com"
- name: DATABRICKS_APP_URL
value: "https://your-mcp-app.databricksapps.com"uv run databricks-mcp-proxyAdd to ~/Library/Application Support/Claude/claude_desktop_config.json:
{
"mcpServers": {
"databricks": {
"command": "uv",
"args": [
"--directory", "/path/to/databricks-mcp-proxy",
"run",
"databricks-mcp-proxy"
]
}
}
}Tool | Description |
| Start OAuth flow (opens browser) |
| List available remote tools |
| Call a remote tool by name |
Claude starts the proxy via stdio
Call authenticate tool
Browser opens for Databricks OAuth
After auth, remote tools are discovered
Use call_databricks_tool to invoke any remote tool
Authenticate with Databricks using OAuth U2M flow.
Opens a browser for authorization.
Uses DATABRICKS_HOST and DATABRICKS_APP_URL from app.yaml or environment.
Inputs: no named parameters. Returns: result
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
Inputs: tool_name (required), arguments. Returns: result
List all available tools on the remote Databricks MCP server. Must authenticate first.
Inputs: no named parameters. Returns: result
Recent tool additions, removals, and schema changes observed during successful MCP inspections.
Loading tool schema changelog…
Scored across 3 tools
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.
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.
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.
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.
One OAuth connector for your team's remote MCP servers, with Tool Packs, guardrails and logs.
The Remote MCP server acts as a standardized bridge between LLM applications (like Claude, ChatGPT, and Cursor) and external services, enabling AI agents to access external tools and resources. Its primary capability is providing a centralized search tool to discover other MCP servers and their respective tools. Unlike local implementations, it runs remotely with OAuth authentication and permission controls for security.
Connect AI agents to Filepad workspaces through OAuth MCP.
Zero-setup MCP gateway securely connecting AI to your tools with authentication and workflows